From: Jerry Van Baren <gerald.vanbaren@comcast.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] MPC8360EMDS: Avoid replicating CFG_CMD commands
Date: Thu, 21 Dec 2006 22:27:51 -0500 [thread overview]
Message-ID: <458B50B7.1040400@comcast.net> (raw)
Hi Dave,
This is a fairly simple patch that rearranges the command configuration
so there are not four very similar lists of commands for the four
configurations (with/without PCI, with/without CFG_RAMBOOT). I got
tired of editing four sets of commands (or worse, editing the wrong set
of commands).
The patch creates a CONFIG_COMMANDS_COMMON with the common commands, a
CONFIG_COMMANDS_PCI with the PCI-related commands (or 0), and
CONFIG_COMMANDS_REMOVE with the commands that are removed for
CFG_RAMBOOT operation (or ~0).
Diff didn't produce a very readable patch. :-( The result of the patch is:
#define CONFIG_COMMANDS_COMMON (CONFIG_CMD_DFL \
| CFG_CMD_ASKENV \
| CFG_CMD_DHCP \
| CFG_CMD_I2C \
| CFG_CMD_PING)
#if defined(CONFIG_PCI)
#define CONFIG_COMMANDS_PCI CFG_CMD_PCI
#else
#define CONFIG_COMMANDS_PCI 0ULL
#endif
#if defined(CFG_RAMBOOT)
#define CONFIG_COMMANDS_REMOVE ~(CFG_CMD_ENV \
| CFG_CMD_LOADS)
#else
#define CONFIG_COMMANDS_REMOVE ~0ULL
#endif
#define CONFIG_COMMANDS ((CONFIG_COMMANDS_COMMON \
| CONFIG_COMMANDS_PCI) \
& CONFIG_COMMANDS_REMOVE)
Best regards,
gvb
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 0001-MPC8360EMDS-Avoid-replicating-CFG_CMD-commands.txt
Url: http://lists.denx.de/pipermail/u-boot/attachments/20061221/05449739/attachment.txt
reply other threads:[~2006-12-22 3:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=458B50B7.1040400@comcast.net \
--to=gerald.vanbaren@comcast.net \
--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