[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130506131150.GB18007@localhost>
Date: Mon, 6 May 2013 10:11:52 -0300
From: Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>
To: "Yann E. MORIN" <yann.morin.1998@...e.fr>
Cc: Mauro Carvalho Chehab <mchehab@...hat.com>,
Randy Dunlap <rdunlap@...radead.org>,
Ezequiel García <elezegarcia@...il.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-media <linux-media@...r.kernel.org>,
linux-kbuild@...r.kernel.org
Subject: Re: Splitting stk1160-ac97 as a module (Re: linux-next: Tree for May
1 (media/usb/stk1160))
On Sat, May 04, 2013 at 09:59:50PM +0200, Yann E. MORIN wrote:
> Ezequiel, All,
>
> On Sat, May 04, 2013 at 02:21:44PM -0300, Ezequiel Garcia wrote:
> > I'm trying to split the ac97 support into a separate module.
> > So far I've managed to do this with two different approaches,
> > but both of them are broken in some way :-(
> >
> > Couple questions:
> >
> > 1. Is it possible to force two symbols to be both built-in (=y) or both
> > modules (=m)? This would make one of my solutions work.
>
> If they are always the same value, there is no need to have two symbols
> in the first place.
>
> However, given the original problem from this thread, if what you meant
> was to have the second symbol either 'n' or the same as the first symbol,
> ie. the following table:
>
> A: n m m y y
> B: n n m n y
>
> Then the closest I came up with is:
>
> config MODULES
> bool "Modules"
>
> config A
> tristate "A"
>
> config B_dummy
> bool "B"
> depends on A
>
> config B
> tristate
> default m if A=m && B_dummy
> default y if A=y && B_dummy
>
> where B_dummy is not used outside of Kconfig, and only A and B are the
> symbols of interest (eg. to build the drivers).
>
That worked like a charm!
Thanks a lot,
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
--
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