From: Alistair John Strachan <alistair@devzero.co.uk>
To: Robin Holt <holt@sgi.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: Linux 2.6.26-rc1
Date: Sun, 4 May 2008 14:56:14 +0100 [thread overview]
Message-ID: <200805041456.14415.alistair@devzero.co.uk> (raw)
In-Reply-To: <20080504123008.GE19717@sgi.com>
On Sunday 04 May 2008 13:30:08 Robin Holt wrote:
> On Sat, May 03, 2008 at 10:53:22PM +0100, Alistair John Strachan wrote:
> > On Saturday 03 May 2008 22:47:38 Alistair John Strachan wrote:
> > > On Saturday 03 May 2008 20:38:20 Linus Torvalds wrote:
> > > > So go out and test it.
> >
> > [snip]
> >
> > > Why is this option acting like CONFIG_EMBEDDED and not like basically
> > > every other subsystem where I can turn ON support for hardware, but by
> > > default it's OFF? (Obviously in my hasty oldconfig run I just went with
> > > the default.)
> >
> > Amazingly, even if I say Y to this option and disable all tuners, it
> > still tries (and fails) to compile this file. What is pulling in this
> > tuner-core dependency?
>
> What if you change CONFIG_MEDIA_TUNER to a 'n'
This isn't a menu-visible option. Your hint does explain why it turns itself
on, however:
config MEDIA_TUNER
tristate
default DVB_CORE || VIDEO_DEV
depends on DVB_CORE || VIDEO_DEV
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..
--
Cheers,
Alistair.
137/1 Warrender Park Road, Edinburgh, UK.
next prev parent reply other threads:[~2008-05-04 13:56 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 [this message]
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
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=200805041456.14415.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