From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: V4L2-based build error
Date: Tue, 13 May 2008 00:32:30 -0300 [thread overview]
Message-ID: <20080513003230.52b36b78@gaivota> (raw)
In-Reply-To: <18844.1210630449@vena.lwn.net>
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
prev parent reply other threads:[~2008-05-13 3:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 22:14 Jonathan Corbet
2008-05-13 3:32 ` Mauro Carvalho Chehab [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080513003230.52b36b78@gaivota \
--to=mchehab@infradead.org \
--cc=corbet@lwn.net \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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®