From: Daniel Vetter <daniel@ffwll.ch>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: 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 11:50:56 +0200 [thread overview]
Message-ID: <YP/XAFYDmJSyUkiM@phenom.ffwll.local> (raw)
In-Reply-To: <20210727093015.1225107-1-javierm@redhat.com>
On Tue, Jul 27, 2021 at 11:30:15AM +0200, Javier Martinez Canillas wrote:
> The Generic System Framebuffers support is built when the COMPILE_TEST
> option is enabled. But this wrongly assumes that all the architectures
> declare a struct screen_info.
>
> This is true for most architectures, but at least the following do not:
> arc, m68k, microblaze, openrisc, parisc and s390.
>
> By attempting to make this compile testeable on all architectures, it
> leads to linking errors as reported by the kernel test robot for parisc:
>
> All errors (new ones prefixed by >>):
>
> hppa-linux-ld: drivers/firmware/sysfb.o: in function `sysfb_init':
> (.init.text+0x24): undefined reference to `screen_info'
> >> hppa-linux-ld: (.init.text+0x28): undefined reference to `screen_info'
>
> To prevent these errors only allow sysfb to be built on systems that are
> going to need it, which are x86 BIOS and EFI.
>
> The EFI Kconfig symbol is used instead of (ARM || ARM64 || RISC) because
> some of these architectures only declare a struct screen_info if EFI is
> enabled. And also, because the SYSFB code is only used for EFI on these
> architectures. For !EFI the "simple-framebuffer" device is registered by
> OF when parsing the Device Tree Blob (if a DT node for this was defined).
>
> Fixes: d391c5827107 ("drivers/firmware: move x86 Generic System Framebuffers support")
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
Whacked onto drm-next so we're welcome again in linux-next.
-Daniel
> ---
>
> Changes in v2:
> - Add a Fixes tag to the changelog.
>
> drivers/firmware/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/firmware/Kconfig b/drivers/firmware/Kconfig
> index af6719cc576b..897f5f25c64e 100644
> --- a/drivers/firmware/Kconfig
> +++ b/drivers/firmware/Kconfig
> @@ -254,7 +254,7 @@ config QCOM_SCM_DOWNLOAD_MODE_DEFAULT
> config SYSFB
> bool
> default y
> - depends on X86 || ARM || ARM64 || RISCV || COMPILE_TEST
> + depends on X86 || EFI
>
> config SYSFB_SIMPLEFB
> bool "Mark VGA/VBE/EFI FB as generic system framebuffer"
> --
> 2.31.1
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2021-07-27 9:51 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 [this message]
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
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=YP/XAFYDmJSyUkiM@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--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=gregkh@linuxfoundation.org \
--cc=javierm@redhat.com \
--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®