Linux Framebuffer Layer development
 help / color / mirror / Atom feed
* fbdev: fb_defio not buildable as module
@ 2015-02-09 11:38 harald
  0 siblings, 0 replies; only message in thread
From: harald @ 2015-02-09 11:38 UTC (permalink / raw)
  To: linux-fbdev

Hi *,

in drivers/video/fbdev/Kconfig we have

| menuconfig FB
|        tristate "Support for frame buffer devices"
|        select FB_CMDLINE
|        ---help---

and

| config FB_DEFERRED_IO
|        bool
|        depends on FB

but in drivers/video/fbdev/core/Makefile we have the line
| obj-$(CONFIG_FB_DEFERRED_IO)   += fb_defio.o

AFAICS the combination of this leads to fb_defio always
linked into the kernel image, even if the framebuffer core
is only built as a module. This doesn't make much sense and
I couldn't find any reason why this would be necessary.

The above code is there in one way or the other since the
initial version of fb_defio.c - I wonder what was the
intended behaviour or actually what is considered the right
way today?

TIA,
Harald

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2015-02-09 11:38 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-02-09 11:38 fbdev: fb_defio not buildable as module harald

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox