From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Manu Abraham <abraham.manu@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>, Andrew Morton <akpm@osdl.org>,
v4l-dvb-maintainer@linuxtv.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [v4l-dvb-maintainer] DVB build fails without I2C
Date: Sun, 10 Sep 2006 10:17:06 -0300 [thread overview]
Message-ID: <1157894226.4359.10.camel@praia> (raw)
In-Reply-To: <4502DA2F.5050905@gmail.com>
Em Sáb, 2006-09-09 às 19:13 +0400, Manu Abraham escreveu:
> Jeff Garzik wrote:
> > 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.
Yes. There are even a few dvb drivers that doesn't 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.
No, it didn't arrived mainstream. It arrived only -mm series. The patch
depends a previous patch that added DVB attach support. Somebody offered
to backport it to 2.6.18 at #v4l channel (I'm not sure but I think it
was adq).
Cheers,
Mauro.
next prev parent reply other threads:[~2006-09-10 13:18 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 ` [v4l-dvb-maintainer] " Manu Abraham
2006-09-10 13:17 ` Mauro Carvalho Chehab [this message]
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=1157894226.4359.10.camel@praia \
--to=mchehab@infradead.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox