From: Jon Loeliger <jdl@jdl.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH: cmdcfg: 00/19] Introduce initial versions of new Command Config files.
Date: Mon, 11 Jun 2007 18:56:29 -0500 [thread overview]
Message-ID: <E1HxtkL-0002Be-K0@jdl.com> (raw)
Wolfgang,
This series of 19 patches introduces new CONFIG_CMD_*
names to replace the existing CFG_CMD_* and eliminates
the need for the bit-wise command configuration scheme.
In this step, the new names are introduced in "all"
and "default" files. Individual boards can then be
configured with either of those starting points and
augmented with additional #define or #undef statements
as desired.
This patch series implements a "temporary step" in
which both the old and new configuration mechanism
are still fully supported, but the old style using
CFG_CMD_* is deprecated. All references that used
to exist with CFG_CMD_* are now duplicated to have
(CFG_CMD_x || CONFIG_CMD_x)
as a temporary measure, until all the individual
board config files are updated to use the new symbols.
When that happens, the old symbols will be removed.
An example new style command config file is shown
in include/configs/MPC8641HPCN.h.
I've made this series of patches available as a git
repository called u-boot-cfg.git:
gitweb:
http://www.jdl.com/git_repos
git:
git clone git://www.jdl.com/software/u-boot-cfg.git
Enjoy!
jdl
next reply other threads:[~2007-06-11 23:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 23:56 Jon Loeliger [this message]
2007-06-12 15:22 ` [U-Boot-Users] [PATCH: cmdcfg: 00/19] Introduce initial versions of new Command Config files Timur Tabi
2007-06-12 15:59 ` Wolfgang Denk
2007-06-12 16:07 ` Jon Loeliger
2007-06-12 16:08 ` Timur Tabi
2007-06-12 16:56 ` Wolfgang Denk
2007-06-12 17:41 ` Timur Tabi
2007-06-12 17:33 ` Ben Warren
2007-07-03 22:45 ` Wolfgang Denk
2007-07-05 0:59 ` Jon Loeliger
2007-07-05 1:43 ` Wolfgang Denk
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=E1HxtkL-0002Be-K0@jdl.com \
--to=jdl@jdl.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