From: Jon Loeliger <jdl@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-boot refactoring
Date: Thu, 05 Jul 2007 15:29:13 -0500 [thread overview]
Message-ID: <1183667353.26273.71.camel@ld0161-tx32> (raw)
In-Reply-To: <20070705200942.AA57F353CCC@atlas.denx.de>
On Thu, 2007-07-05 at 15:09, Wolfgang Denk wrote:
> In message <1183661913.26273.49.camel@ld0161-tx32> you wrote:
> >
> > Say.... Not to put _too_ fine a spin on this, but there
> > is a _veeery_ similar issue brewing with the POST CFG_ symbols...
>
> Let me know if you have specific ideas how to change these; we're
> working in that area right now (adding 440EPx POST support), so we
> can do it better right from the start.
Ah, these have the same problem that the Command Line
selection has -- Bit fields are being used at compile
time to select code portions. We'll need to introduce
symbols such as CONFIG_POST_x for each of the existing
CFG_POST_x symbols, and modify the users to have the
features conditionally compiled like #if defined(CONFIG_POST_x)
as well as modifying some (fewer!) board config files
to explicitly list which CONFIG_POST_x features are wanted.
Naturally, this can be done in a round after the Command
Line Config updates too!
jdl
next prev parent reply other threads:[~2007-07-05 20:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 18:48 [U-Boot-Users] U-boot refactoring Grant Likely
2007-07-03 21:04 ` Wolfgang Denk
2007-07-03 21:19 ` Jon Loeliger
2007-07-03 21:40 ` Wolfgang Denk
2007-07-03 22:00 ` Jon Loeliger
2007-07-03 22:44 ` Wolfgang Denk
2007-07-04 18:15 ` Jon Loeliger
2007-07-04 8:20 ` Robert Schwebel
2007-07-04 13:44 ` Wolfgang Denk
2007-07-04 19:11 ` Carsten Schlote
2007-07-05 18:58 ` Jon Loeliger
2007-07-05 20:09 ` Wolfgang Denk
2007-07-05 20:29 ` Jon Loeliger [this message]
2007-07-05 23:53 ` Carsten Schlote
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=1183667353.26273.71.camel@ld0161-tx32 \
--to=jdl@freescale.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