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...

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/