From: Nikita V. Youshchenko <yoush@debian.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] fix compilation problem for mpc8349itx CFG_RAMBOOT
Date: Thu, 24 May 2007 00:13:43 +0400 [thread overview]
Message-ID: <200705240013.48844@sercond.localdomain> (raw)
In-Reply-To: <20070523195138.A061F35264A@atlas.denx.de>
> > Please take a look at my MPC8349ITX.h to see the full extent of what I
> > was trying to do.
>
> Yes, I know what it does. Frankly, it's ugly.
I think that the original reason of such 'ugly' solutions is the usage of
singe macro (CONFIG_COMMANDS) with bit-fields. This is causing problems,
because:
- it is nos scalable to manually define CONFIG_COMMANDS as a bitwise-or of
all needed CFG_CMD_* in each file under include/configs - because adding
new 'arch-independent' command in this case will require mo9dification of
all those files;
- so things as CONFIG_CMD_DFL become needed;
- but C preprocessor is has poor redefining capabilities - we can't just
redefine a macro using it's previous definition - so usage of
CONFIG_CMD_DFL causes issues like one being discussed.
A much better solution could be to have a macro-per-command.
In this case:
- command xxx could be compiled in, if CONFIG_CMD_XXX is defined, and not
compiled in if not defined;
- it could be easy to define/undefine such macros in config
But I don't think that such a change could be possible at the current stage
of u-boot development.
Nikita
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20070524/32f49331/attachment.pgp
next prev parent reply other threads:[~2007-05-23 20:13 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 [this message]
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
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=200705240013.48844@sercond.localdomain \
--to=yoush@debian.org \
--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