mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* V4L2-based build error
@ 2008-05-12 22:14 Jonathan Corbet
  2008-05-13  3:32 ` Mauro Carvalho Chehab
  0 siblings, 1 reply; 2+ messages in thread
From: Jonathan Corbet @ 2008-05-12 22:14 UTC (permalink / raw)
  To: linux-kernel; +Cc: mchehab

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


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

* Re: V4L2-based build error
  2008-05-12 22:14 V4L2-based build error Jonathan Corbet
@ 2008-05-13  3:32 ` Mauro Carvalho Chehab
  0 siblings, 0 replies; 2+ messages in thread
From: Mauro Carvalho Chehab @ 2008-05-13  3:32 UTC (permalink / raw)
  To: Jonathan Corbet; +Cc: linux-kernel, Hans Verkuil

Hi Jon,

On Mon, 12 May 2008 16:14:09 -0600
Jonathan Corbet <corbet@lwn.net> wrote:

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

I have a number of patches meant to fix several troubles at v4l/dvb
compilation. I intend to send they soon for merging, but I want first to test
some random builds.


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

This file is meant to be an interim approach to allow a smoothly change from
the old i2c probing way to the newer format. It should be there for some time,
until we can convert all v4l2 drivers to the new approach.


Cheers,
Mauro

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

end of thread, other threads:[~2008-05-13  3:32 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-05-12 22:14 V4L2-based build error Jonathan Corbet
2008-05-13  3:32 ` Mauro Carvalho Chehab

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

all inboxes | Powered by JetHome®