public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [patch] video/dvb: fix MEDIA_TUNER && FW_LOADER build error
@ 2008-05-20 19:34 Ingo Molnar
  2008-05-25 19:30 ` Roman Zippel
  0 siblings, 1 reply; 2+ messages in thread
From: Ingo Molnar @ 2008-05-20 19:34 UTC (permalink / raw)
  To: Mauro Carvalho Chehab
  Cc: linux-kernel, Michael Krufky, Patrick Boettcher, Sam Ravnborg


-tip testing found the following build failure:

  LD      .tmp_vmlinux1
  drivers/built-in.o: In function `generic_set_freq':
  tuner-xc2028.c:(.text+0xbd896): undefined reference to `request_firmware'
  tuner-xc2028.c:(.text+0xbdd7a): undefined reference to `release_firmware'
  drivers/built-in.o: In function `xc_load_fw_and_init_tuner':
  xc5000.c:(.text+0xc68e6): undefined reference to `request_firmware'
  xc5000.c:(.text+0xc6abe): undefined reference to `release_firmware'

with this config:

  http://redhat.com/~mingo/misc/config-Tue_May_20_18_11_34_CEST_2008.bad

the reason is another kconfig tool bug that has to be worked around in
the driver's Kconfig file: if FW_LOADER is selected in a second
dependency, that is not properly propagated up the dependencies.

in this case, FW_LOADER is selected from MEDIA_TUNER_XC2028:

  config MEDIA_TUNER_XC2028
        tristate "XCeive xc2028/xc3028 tuners"
        depends on VIDEO_MEDIA && I2C
        depends on HOTPLUG
        select FW_LOADER

which got selected by MEDIA_TUNER:

  config MEDIA_TUNER
        tristate
        default VIDEO_MEDIA && I2C
        depends on VIDEO_MEDIA && I2C
        select FW_LOADER if !MEDIA_TUNER_CUSTOMIZE && HOTPLUG

but the kconfig tool did not pick up this second-order dependency and 
allowed CONFIG_FW_LOADER=m to be selected - in which case the build 
fails.

the workaround i found was to move the select of FW_LOADER one level up, 
so that the buggy kconfig tool can notice it and can act appropriately. 
This problem can probably be worked around in other ways as well, i went 
for the minimal fix.

Obviously, the kconfig tool should be fixed, it is not reasonable to 
expect driver authors to do manual dependency resolution (that kconfig 
itself already does) and uglify the Kconfig files. The kconfig tool did 
nothing to warn about this situation and did not prevent this faulty 
.config from being constructed.

Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
 drivers/media/common/tuners/Kconfig |    1 +
 1 file changed, 1 insertion(+)

Index: linux/drivers/media/common/tuners/Kconfig
===================================================================
--- linux.orig/drivers/media/common/tuners/Kconfig
+++ linux/drivers/media/common/tuners/Kconfig
@@ -21,6 +21,7 @@ config MEDIA_TUNER
 	tristate
 	default VIDEO_MEDIA && I2C
 	depends on VIDEO_MEDIA && I2C
+	select FW_LOADER if !MEDIA_TUNER_CUSTOMIZE && HOTPLUG
 	select MEDIA_TUNER_XC2028 if !MEDIA_TUNER_CUSTOMIZE && HOTPLUG
 	select MEDIA_TUNER_XC5000 if !MEDIA_TUNER_CUSTOMIZE && HOTPLUG
 	select MEDIA_TUNER_MT20XX if !MEDIA_TUNER_CUSTOMIZE

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2008-05-25 19:31 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-05-20 19:34 [patch] video/dvb: fix MEDIA_TUNER && FW_LOADER build error Ingo Molnar
2008-05-25 19:30 ` Roman Zippel

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