From: Kumar Gala <galak@kernel.crashing.org>
To: Sam Ravnborg <sam@ravnborg.org>, Roman Zippel <zippel@linux-m68k.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: fake config option w/kbuild?
Date: Thu, 15 Mar 2007 10:19:03 -0500 [thread overview]
Message-ID: <C6F49569-655E-4B17-B9DA-9644C8B3668D@kernel.crashing.org> (raw)
Guys, I was wondering if there was a way to have a fake config
option, one that acts just like a normal config option, but doesn't
get a #define CONFIG_<FOOBAR> .. for it and thus can't be used in code.
I explain my problem, and maybe there is a better solution.
I have a config option call QE that exists on two flavor's of
powerpc. For PPC, we have one top level menu to select the processor
(in this case 83xx or 85xx). We than have a second top level menu to
select the platform (which board). The platform menu is where I want
the 'QE' option to exist. Each flavor (83xx, 85xx) has its own
Kconfig that defines what's in the platform menu. However, the QE
config choice is common between them.
So for now we are doing something like:
arch/powerpc/Kconfig:
config QE
bool
default n
arch/powerpc/platform/83xx/Kconfig:
config QE_83xx
bool "QUICC Engine Support"
select QE
depends on PPC_MPC836x || PPC_MPC832x
default y
---help---
The QUICC Engine (QE) is a new generation of communications
coprocessors on Freescale embedded CPUs (akin to CPM in
older chips).
arch/powerpc/platform/85xx/Kconfig:
config QE_85xx
bool "QUICC Engine Support"
select QE
depends on PPC_MPC8568
default y
---help---
The QUICC Engine (QE) is a new generation of communications
coprocessors on Freescale embedded CPUs (akin to CPM in
older chips).
My initial question is that I don't want anyone using CONFIG_QE_83xx
or CONFIG_QE_85xx in code, the second part is if there is a way to
remove duplicating the QE_83xx/QE_85xx options down in platform/8{3,5}
xx/Kconfig.
thanks
- kumar
next reply other threads:[~2007-03-15 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 15:19 Kumar Gala [this message]
2007-03-15 19:12 ` Adrian Bunk
2007-03-15 20:08 ` Kumar Gala
2007-03-17 23:33 ` Adrian Bunk
2007-03-18 16:24 ` Roman Zippel
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=C6F49569-655E-4B17-B9DA-9644C8B3668D@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®