From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Need the lists opinion on the "right" way to fix something (long)
Date: Wed, 7 Nov 2007 09:19:34 +0100 [thread overview]
Message-ID: <200711070919.34669.matthias.fuchs@esd-electronics.com> (raw)
In-Reply-To: <fa686aa40711011617n1d79fccq710a8ecefefd69ce@mail.gmail.com>
Hi,
On Friday 02 November 2007 00:17, Grant Likely wrote:
> On 11/1/07, Wolfgang Denk <wd@denx.de> wrote:
> > In message <OF35EFB6C6.4311E888-ON88257386.007BCD10-88257386.007E0B81@selinc.com> you wrote:
> > >
> > > Since I've only been working with u-boot/open source for about 9 months,
> > > I'm not really sure what the design philosophies are and what the
> > > acceptable and/or "righ" way of fixing this would be. Any input or
> > > direction would be greatly appreciated. Thanks.
> >
> > The simple rule is: whenever you use a variable / macro you must make
> > sure it is defined. You use CFG_XILINX_SPARTAN3 in your board config,
> > so you must make sure to include all needed header files there.
>
> Also, the whole CFG_FPGA bitmask is a bad approach and should be
> removed. Instead the config should be based on whether or not the
> CFG_XILINX_SPARTAN et al are defined or not. CONFIG_CMD used to be
> done with a bit field too, but it was removed due to it being
> difficult to extend.
Ack. That's what I also throught about.
Matthias
next prev parent reply other threads:[~2007-11-07 8:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 22:56 [U-Boot-Users] Need the lists opinion on the "right" way to fix something (long) Bruce_Leonard at selinc.com
2007-11-01 23:14 ` Wolfgang Denk
2007-11-01 23:17 ` Grant Likely
2007-11-07 8:19 ` Matthias Fuchs [this message]
2007-11-01 23:28 ` Bruce_Leonard at selinc.com
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=200711070919.34669.matthias.fuchs@esd-electronics.com \
--to=matthias.fuchs@esd-electronics.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