If you configure V4L2 as a module, the config system will still let you
configure DVB_CORE built-in. This yields:
drivers/built-in.o: In function `v4l2_i2c_drv_attach_legacy':
tuner-core.c:(.text+0x901d5): undefined reference to `v4l2_i2c_attach'
drivers/built-in.o: In function `tuner_command':
tuner-core.c:(.text+0x91aed): undefined reference to `v4l_printk_ioctl'
I never had trouble with this before 2.6.26-rc2. I'm happy making
DVB_CORE modular, but it would be nice if the config system didn't allow
inconsistent setups.
jon
P.S. As I was digging into this, I ran into <media/v4l2-i2c-drv-legacy.h>,
which takes an interesting approach - function definitions and
module_init() within a header file? This thing is included in a
number of places; it seems like there should be a better way...
--
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Andi Kleen | [PATCH x86] [0/16] Various i386/x86-64 changes |
| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
git: | |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Natalie Protasevich | [BUG] New Kernel Bugs |
| Arjan van de Ven | Re: [GIT]: Networking |
