From: Daniel Drake <dsd@gentoo.org>
To: toralf.foerster@gmx.de
Cc: linux-kernel@vger.kernel.org, linux-dvb@linuxtv.org
Subject: Should DVB depend on I2C?
Date: Tue, 30 May 2006 00:29:47 +0100 [thread overview]
Message-ID: <447B83EB.4020700@gentoo.org> (raw)
In-Reply-To: <200605292214.10378.toralf.foerster@gmx.de>
> Got the following compile error :
>
> LD .tmp_vmlinux1
> drivers/built-in.o: In function `tda8083_writereg':
> drivers/media/dvb/frontends/tda8083.c:69: undefined reference to `i2c_transfer'
> drivers/built-in.o: In function `tda8083_readregs':
> drivers/media/dvb/frontends/tda8083.c:84: undefined reference to `i2c_transfer'
> drivers/built-in.o: In function `l64781_writereg':
> drivers/media/dvb/frontends/l64781.c:60: undefined reference to `i2c_transfer'
> drivers/built-in.o: In function `l64781_readreg':
> drivers/media/dvb/frontends/l64781.c:75: undefined reference to `i2c_transfer'
> drivers/built-in.o: In function `reset_and_configure':
> drivers/media/dvb/frontends/l64781.c:119: undefined reference to `i2c_transfer'
> drivers/built-in.o:drivers/media/dvb/frontends/l64781.c:524: more undefined references to `i2c_transfer' follow
> make: *** [.tmp_vmlinux1] Error 1
>
> .config is attached
Still waiting on a response at
http://marc.theaimsgroup.com/?l=linux-video&m=114787670927881&w=2
Oh wait, there was one, but apparently I wasn't CC'd. Adding the right
list now.
DVB people:
Attila Stehr in a Gentoo bug report pointed out that the DVB frontends
do not link without CONFIG_I2C, and there is no dependency listed in the
Kconfig files.
e.g.:
drivers/built-in.o: In function `stv0299_readregs':
stv0299.c:(.text+0xa4d8a): undefined reference to `i2c_transfer'
I checked and I see this is the case for other DVB components too, such
as the dvb-usb drivers.
I'm happy to patch this, but I'm not sure which approach should be best.
Should I make CONFIG_DVB or CONFIG_DVB_CORE depend on I2C, or should I
modify the config blocks for all of the individual options which use I2C
stuff?
Thanks,
Daniel
prev parent reply other threads:[~2006-05-29 23:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 20:14 compile error: i2c_transfer Toralf Förster
2006-05-29 21:26 ` Chris Byrne
2006-05-29 23:29 ` Daniel Drake [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=447B83EB.4020700@gentoo.org \
--to=dsd@gentoo.org \
--cc=linux-dvb@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.