From: Manu Abraham <abraham.manu@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: v4l-dvb-maintainer@linuxtv.org, Andrew Morton <akpm@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [v4l-dvb-maintainer] DVB build fails without I2C
Date: Sat, 09 Sep 2006 19:13:51 +0400 [thread overview]
Message-ID: <4502DA2F.5050905@gmail.com> (raw)
In-Reply-To: <45029DB0.5020300@garzik.org>
Jeff Garzik wrote:
> In an effort to speed up my all-filesystems build, I disabled several
> things in my allyesconfig-generated .config. As luck would have it, I
> wound up disabling I2C but did not disable DVB.
>
> This led to a link failure at the end of the build, with the linker
> complaining that many I2C-related symbols were not present.
>
> Recommended solution: Add I2C as a dependency (or select) in DVB Kconfig.
DVB-CORE does not depend on I2C, since it does not rely on any I2C at
all. (DVB-CORE can use other methods) It is the PCI bridges that depend
on I2C. IIRC, we had a patch adding I2C dependencies for the Kconfig for
the relevant bridge chips. The frontends which are connected to the
bridges, depend on DVB-Core and I2C. So that dependency exists.
frontends foo
depends on DVB_CORE && I2C
pci bridges foo
depends on DVB_CORE && I2C && PCI
Maybe that patch has not made it yet to mainline.
Manu
next prev parent reply other threads:[~2006-09-09 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-09 10:55 DVB build fails without I2C Jeff Garzik
2006-09-09 15:13 ` Manu Abraham [this message]
2006-09-10 13:17 ` [v4l-dvb-maintainer] " Mauro Carvalho Chehab
2006-09-10 15:16 ` Mauro Carvalho Chehab
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=4502DA2F.5050905@gmail.com \
--to=abraham.manu@gmail.com \
--cc=akpm@osdl.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=v4l-dvb-maintainer@linuxtv.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 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.