From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] fix compilation problem for mpc8349itx CFG_RAMBOOT
Date: Thu, 24 May 2007 08:49:40 -0400 [thread overview]
Message-ID: <465589E4.2020701@smiths-aerospace.com> (raw)
In-Reply-To: <20070524123653.1231835264E@atlas.denx.de>
Wolfgang Denk wrote:
> Dear Nikita,
>
> in message <200705241210.19623@zigzag.lvk.cs.msu.su> you wrote:
>>> * all commands except foo, bar and baz
>> #include "define_all_cmds.h"
>> #undef CONFIG_CMD_FOO
>> #undef CONFIG_CMD_BAR
>> #undef CONFIG_CMD_BAZ
>>
>>> * all default commands plus foo, but without baz
>> #include "define_default_cmds.h"
>> #define CONFIG_CMD_FOO
>> #undef CONFIG_CMD_BAZ
>>
>>> I guess then you will have to list up all commands you want to
>>> include somewhere - either in the board onfig file or in another
>>> header file.
>> Sure - in separate headers files. I see no problems here. It scales.
>
> Good idea. Shall we go for that?
>
> Any other opinions, ACKs or NACKs?
>
> Best regards,
> Wolfgang Denk
Just to poke the sleeping lions, :-) we've discussed going to a linux
kconfig "script" in the past and was not pursued for various reasons,
most of which I've forgotten. It has some nice features
* Help text
* Conditional logic to guard against nonsensical configurations
Should we reconsider it?
I believe the above is compatible with kconfig, the missing part being
piles and piles of configuration snippets that would have to be written.
Anybody with more knowledge than me? (OK, that last was rhetorical. ;-)
Best regards,
gvb
next prev parent reply other threads:[~2007-05-24 12:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 8:45 [U-Boot-Users] [PATCH] fix compilation problem for mpc8349itx CFG_RAMBOOT Nikita V. Youshchenko
2007-05-23 15:09 ` Timur Tabi
2007-05-23 15:37 ` Nikita V. Youshchenko
2007-05-23 15:55 ` Timur Tabi
2007-05-23 16:30 ` Wolfgang Denk
2007-05-23 16:50 ` Timur Tabi
2007-05-23 16:52 ` Timur Tabi
2007-05-23 18:59 ` Nikita V. Youshchenko
2007-05-23 19:08 ` Timur Tabi
2007-05-23 17:48 ` Timur Tabi
2007-05-23 18:38 ` Wolfgang Denk
2007-05-23 18:43 ` Timur Tabi
2007-05-23 19:51 ` Wolfgang Denk
2007-05-23 20:01 ` Nikita V. Youshchenko
2007-05-23 20:13 ` Nikita V. Youshchenko
2007-05-23 23:11 ` Wolfgang Denk
2007-05-24 8:10 ` Nikita V. Youshchenko
2007-05-24 12:36 ` Wolfgang Denk
2007-05-24 12:49 ` Jerry Van Baren [this message]
2007-05-24 15:25 ` Timur Tabi
2007-05-24 18:36 ` Jon Loeliger
2007-05-24 18:38 ` Timur Tabi
2007-05-24 19:43 ` Wolfgang Grandegger
2007-05-24 12:39 ` Wolfgang Grandegger
2007-05-23 20:29 ` Timur Tabi
2007-06-01 20:18 ` Kim Phillips
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=465589E4.2020701@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.com \
--cc=u-boot@lists.denx.de \
/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