LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: kbuild question
Date: Sun, 18 Feb 2007 18:16:00 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0702181811220.14457@scrub.home> (raw)
In-Reply-To: <9AF725F4-FE65-4357-B7EB-CC03808C105D@kernel.crashing.org>
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
next prev parent reply other threads:[~2007-02-18 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 19:18 Kumar Gala
2007-02-15 22:33 ` Sam Ravnborg
2007-02-15 23:44 ` Kumar Gala
2007-02-16 8:50 ` Sam Ravnborg
2007-02-16 10:23 ` Roman Zippel
2007-02-16 14:14 ` Kumar Gala
2007-02-18 17:16 ` Roman Zippel [this message]
2007-02-18 19:25 ` Sam Ravnborg
2007-03-15 15:22 ` Kumar Gala
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=Pine.LNX.4.64.0702181811220.14457@scrub.home \
--to=zippel@linux-m68k.org \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--subject='Re: kbuild question' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).