[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0702181811220.14457@scrub.home>
Date: Sun, 18 Feb 2007 18:16:00 +0100 (CET)
From: Roman Zippel <zippel@...ux-m68k.org>
To: Kumar Gala <galak@...nel.crashing.org>
cc: Sam Ravnborg <sam@...nborg.org>,
Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: kbuild question
Hi,
On Fri, 16 Feb 2007, Kumar Gala wrote:
> > Could you please be more specific about the problem you're trying to
> > solve, instead of how you're trying to solve it?
> > A real example would help a lot to understand the actual problem.
>
> Sure, on powerpc for some of the embedded sub-architectures you can only
> select a single board to build for. For a lot of people this is sufficient,
> however we are moving towards a world where you can easily build in support
> for multiple boards into a single kernel.
>
> I'd like to have it such that if I'm only building support for one board
> (CONFIG_ONLY_HAVE_ONE, not going to call it that, but for this discussion its
> sufficient), you get a choice menu from Kconfig enforcing the ability to only
> select one board. However if !CONFIG_ONLY_HAVE_ONE than you can select
> multiple boards to build into your kernel.
>
> if CONFIG_ONLY_HAVE_ONE is set we can optimize out the runtime checks that get
> added for handling the multiple board case.
On m68k we have the same problem, but what I'm what I'm considering is to
add a new mode for choice groups - at least one must be selected and
kconfig generates the extra information if only one is selected.
bye, Roman
-
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