[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200805041456.14415.alistair@devzero.co.uk>
Date: Sun, 4 May 2008 14:56:14 +0100
From: Alistair John Strachan <alistair@...zero.co.uk>
To: Robin Holt <holt@....com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Mauro Carvalho Chehab <mchehab@...radead.org>
Subject: Re: Linux 2.6.26-rc1
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists