From: Randy Dunlap <rdunlap@infradead.org>
To: "Michal Suchánek" <msuchanek@suse.de>,
linux-kernel@vger.kernel.org,
"Masahiro Yamada" <masahiroy@kernel.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-fbdev@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: Re: build failure in linux-next: offb missing fb helpers
Date: Fri, 18 Nov 2022 22:20:30 -0800 [thread overview]
Message-ID: <b8191c01-4d78-537b-9650-a783e14e5997@infradead.org> (raw)
In-Reply-To: <20221118150351.GV28810@kitsune.suse.cz>
Hi--
[adding Masahiro-san]
On 11/18/22 07:03, Michal Suchánek wrote:
> Hello,
>
> I am seeing these errors:
>
> [ 3825s] AR built-in.a
> [ 3827s] AR vmlinux.a
> [ 3835s] LD vmlinux.o
> [ 3835s] OBJCOPY modules.builtin.modinfo
> [ 3835s] GEN modules.builtin
> [ 3835s] GEN .vmlinux.objs
> [ 3848s] MODPOST Module.symvers
> [ 3848s] CC .vmlinux.export.o
> [ 3849s] UPD include/generated/utsversion.h
> [ 3849s] CC init/version-timestamp.o
> [ 3849s] LD .tmp_vmlinux.btf
> [ 3864s] ld: drivers/video/fbdev/offb.o:(.data.rel.ro+0x58): undefined
> reference to `cfb_fillrect'
> [ 3864s] ld: drivers/video/fbdev/offb.o:(.data.rel.ro+0x60): undefined
> reference to `cfb_copyarea'
> [ 3864s] ld: drivers/video/fbdev/offb.o:(.data.rel.ro+0x68): undefined
> reference to `cfb_imageblit'
>
> cfb_fillrect is provided by drivers/video/fbdev/core/cfbfillrect.c
>
> It is compiled when CONFIG_FB_CFB_FILLRECT
> drivers/video/fbdev/core/Makefile:obj-$(CONFIG_FB_CFB_FILLRECT) += cfbfillrect.o
>
> drivers/video/fbdev/Makefile:obj-$(CONFIG_FB_OF) += offb.o
> is compiled when CONFIG_FB_OF
>
> It selects CONFIG_FB_CFB_FILLRECT
> config FB_OF
> bool "Open Firmware frame buffer device support"
> depends on (FB = y) && PPC && (!PPC_PSERIES || PCI)
> select APERTURE_HELPERS
> select FB_CFB_FILLRECT
> select FB_CFB_COPYAREA
> select FB_CFB_IMAGEBLIT
> select FB_MACMODES
>
> The config has FB_OF built-in and FB_CFB_FILLRECT modular
> config/ppc64le/vanilla:CONFIG_FB_CFB_FILLRECT=m
> config/ppc64le/vanilla:CONFIG_FB_CFB_COPYAREA=m
> config/ppc64le/vanilla:CONFIG_FB_CFB_IMAGEBLIT=m
> config/ppc64le/vanilla:CONFIG_FB_OF=y
>
> It only depends on FB which mut be built-in for FB_OF
> config FB_CFB_FILLRECT
> tristate
> depends on FB
>
> Is select in kconfig broken?
>
> Attachnig the config in question.
The symbol info from xconfig says:
Symbol: FB_CFB_FILLRECT [=m]
Type : tristate
Defined at drivers/video/fbdev/Kconfig:69
Depends on: HAS_IOMEM [=y] && FB [=y]
Selected by [m]:
[deleted]
- FB_OF [=y] && HAS_IOMEM [=y] && FB [=y]=y && PPC [=y] && (!PPC_PSERIES [=y] || PCI [=y]) && !DRM_OFDRM [=m]
I don't see why the 'select' from (bool) FB_OF would leave FB_CFB_FILLRECT (and the others)
as =m instead of =y.
Hopefully Masahiro can shed some light on this.
--
~Randy
next parent reply other threads:[~2022-11-19 6:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221118150351.GV28810@kitsune.suse.cz>
2022-11-19 6:20 ` Randy Dunlap [this message]
2022-11-19 13:27 ` build failure in linux-next: offb missing fb helpers Masahiro Yamada
2022-11-19 15:37 ` Michal Suchánek
2022-11-19 18:15 ` Randy Dunlap
2022-11-20 17:47 ` Thomas Zimmermann
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=b8191c01-4d78-537b-9650-a783e14e5997@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=masahiroy@kernel.org \
--cc=msuchanek@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;
as well as URLs for NNTP newsgroup(s).