From: Alistair John Strachan <alistair@devzero.co.uk>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Robin Holt <holt@sgi.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.26-rc1
Date: Tue, 6 May 2008 09:02:25 +0100 [thread overview]
Message-ID: <200805060902.25835.alistair@devzero.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0805051656180.3218@bombadil.infradead.org>
On Monday 05 May 2008 22:04:17 Mauro Carvalho Chehab wrote:
> Alistair,
>
> Sorry for not answering earlier, I got some days off (I still didn't read
> all messages from you - I'm flooded of messages here).
>
> >> I have DVB_CORE=n and VIDEO_DEV=y. VIDEO_DEV is:
> >>
> >> config VIDEO_DEV
> >> tristate "Video For Linux"
> >>
> >> So if you enable Video For Linux, the tuner-core is automatically built,
> >> even if no tuners are selected? Surely that's wrong..
> >
> > That is probably correct. Video For Linux is used for capturing video
> > streams. The fact that you can get this invalid config to fail to build
> > should be reported to the v4l folks and let them fix it up.
>
> Yes, this is correct, if you select a board that supports tuner (for
> example, bttv, or cx88).
>
> The error is that most tuners are dependent of I2C. The right fix seems to
> do this:
>
>
> config MEDIA_TUNER
> tristate
> default (DVB_CORE || VIDEO_DEV) && I2C
> depends on (DVB_CORE || VIDEO_DEV) && I2C
This still seems imperfect -- if I have I2C=y and VIDEO_DEV=y, but DVB_CORE=n
(and no board types selected), it'll still build at least some of the tuner
code into the V4L core.
This is still true even if I set MEDIA_TUNER_CUSTOMIZE=y and set all of the
tuners to 'n'. I'd assumed that this was an artefact of the complex Kconfig
logic here, and was not intentional.
Thanks for fixing the compile issue though, I've confirmed that it works.
--
Cheers,
Alistair.
137/1 Warrender Park Road, Edinburgh, UK.
next prev parent reply other threads:[~2008-05-06 8:02 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8287f540805041818g534c4e02qaadb0e749c5f3439@mail.gmail.com>
2008-05-03 19:38 ` Linux 2.6.26-rc1 Linus Torvalds
2008-05-03 21:47 ` Alistair John Strachan
2008-05-03 21:53 ` Alistair John Strachan
2008-05-04 12:30 ` Robin Holt
2008-05-04 13:56 ` Alistair John Strachan
2008-05-04 16:09 ` Robin Holt
2008-05-04 16:33 ` Alistair John Strachan
2008-05-05 21:04 ` Mauro Carvalho Chehab
2008-05-06 8:02 ` Alistair John Strachan [this message]
2008-05-06 10:31 ` Mauro Carvalho Chehab
2008-05-06 14:34 ` Stefan Richter
2008-05-06 14:54 ` Stefan Richter
2008-05-06 19:13 ` Mauro Carvalho Chehab
2008-05-06 19:44 ` Stefan Richter
2008-05-06 20:06 ` Mauro Carvalho Chehab
2008-05-06 20:47 ` Stefan Richter
2008-05-06 22:39 ` Mauro Carvalho Chehab
2008-05-06 23:36 ` Stefan Richter
2008-05-08 12:48 ` Mauro Carvalho Chehab
2008-05-08 14:11 ` Stefan Richter
2008-05-06 23:48 ` Stefan Richter
2008-05-04 7:29 ` [patch] sysfs: build fix Ingo Molnar
2008-05-04 18:40 ` Linux 2.6.26-rc1 Jan Engelhardt
2008-05-05 5:39 ` Andreas Mohr
2008-05-05 7:30 ` Ingo Molnar
2008-05-05 20:14 ` Mauro Carvalho Chehab
2008-05-06 13:07 ` Ingo Molnar
2008-05-07 8:35 ` Ingo Molnar
2008-05-05 23:51 ` Stephen Rothwell
2008-05-05 23:55 ` David Miller
2008-05-06 0:16 ` Andrew Morton
2008-05-06 5:57 ` Stephen Rothwell
2008-05-06 0:21 ` Ingo Molnar
2008-05-06 5:35 ` Stephen Rothwell
2008-05-06 6:56 ` David Miller
2008-05-06 7:26 ` Stephen Rothwell
2008-05-06 0:17 ` Ingo Molnar
2008-05-06 5:48 ` Stephen Rothwell
2008-05-06 6:07 ` Scheduling problems ? [ Was: Linux 2.6.26-rc1 ] J.A. Magallón
2008-05-06 13:11 ` Ingo Molnar
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=200805060902.25835.alistair@devzero.co.uk \
--to=alistair@devzero.co.uk \
--cc=holt@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=torvalds@linux-foundation.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