From: Javier Martinez Canillas <javierm@redhat.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel <dri-devel@lists.freedesktop.org>,
Peter Robinson <pbrobinson@gmail.com>,
Mark Brown <broonie@kernel.org>,
kernel test robot <lkp@intel.com>, Borislav Petkov <bp@suse.de>,
Colin Ian King <colin.king@canonical.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Dinh Nguyen <dinguyen@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
John Stultz <john.stultz@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Linus Walleij <linus.walleij@linaro.org>,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH v2] drivers/firmware: fix SYSFB depends to prevent build failures
Date: Tue, 27 Jul 2021 13:32:29 +0200 [thread overview]
Message-ID: <e3f0f7a0-2130-18be-48a4-af1918017eca@redhat.com> (raw)
In-Reply-To: <CAMuHMdVh4XgXeaLXXTmPxMuWM4C1mTDnhSmDmff6T37PwNxupg@mail.gmail.com>
On 7/27/21 1:17 PM, Geert Uytterhoeven wrote:
[snip]
>> Not enabling this, would mean that a platform device to match a driver
>> supporting the EFI GOP framebuffer (e.g: simple{drm,fb} or efifb) will
>> not be registered. Which will lead to not having an early framebuffer.
>
> Do all (embedded) EFI systems have a frame buffer?
>
That's a good question. I don't know if all EFI firmwares are expected
to provide a GOP or not. But even the u-boot EFI stub provides one, if
video output is supported by u-boot on that system.
> Perhaps SYSFB should be selected by SYSFB_SIMPLEFB, FB_VESA,
> and FB_EFI?
>
It's another option, yes. I just thought that the use of select was not
encouraged and using depends was less fragile / error prone.
>> The logic used to be in drivers/firmware/efi/efi-init.c, that's built
>> in if CONFIG_EFI is enabled. We just consolidated both X86 and EFI:
>>
>> https://cgit.freedesktop.org/drm/drm-misc/commit/?id=8633ef82f101
>
> Thanks, I'm aware of that commit, as I was just about to reply to it,
> when I saw the patch is this thread ;-)
>
Ok :)
Best regards,
--
Javier Martinez Canillas
Linux Engineering
Red Hat
next prev parent reply other threads:[~2021-07-27 11:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 9:30 Javier Martinez Canillas
2021-07-27 9:50 ` Daniel Vetter
2021-07-27 10:03 ` Geert Uytterhoeven
2021-07-27 10:22 ` Javier Martinez Canillas
2021-07-27 11:17 ` Geert Uytterhoeven
2021-07-27 11:32 ` Javier Martinez Canillas [this message]
2021-07-27 11:39 ` Geert Uytterhoeven
2021-07-27 11:54 ` Javier Martinez Canillas
2021-07-27 11:49 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e3f0f7a0-2130-18be-48a4-af1918017eca@redhat.com \
--to=javierm@redhat.com \
--cc=bp@suse.de \
--cc=broonie@kernel.org \
--cc=colin.king@canonical.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dinguyen@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=john.stultz@linaro.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nsaenz@kernel.org \
--cc=pbrobinson@gmail.com \
--cc=sudeep.holla@arm.com \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®