From: Dan Malek <dan@embeddededge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: Patch: Support for PQ27e (8247/48/71/72) chips and MPC8272ADS board
Date: Wed, 17 Mar 2004 09:15:48 -0500 [thread overview]
Message-ID: <40585D94.70103@embeddededge.com> (raw)
In-Reply-To: 16472.15001.340060.100485@gargle.gargle.HOWL
Sorry to jump into this late, but since I do tons of PQ work
I want to add my comments.
> .... I personally don't like such
> Yuli> compile-time definitions because chip version can be easily
> Yuli> detected in run-time.
No, it can't in all cases. You can determine the core type and can
sometimes find something about the CPM rom version, but tracking down
and maintaining the permutations isn't trivial. You have great inside
information on this stuff, but it doesn't help the rest of us add or
maintain this software.
> Wolfgang> The advantage of compile-time definitions is that they
> Wolfgang> result in smaller code.
I agree. We've been doing it this way in Linux for years, the compiler
makes it pretty clear when you don't have something #defined. What's
run-time code going to do when it can't determine the core or CPM type?
Assume some defaults and hope a message gets printed?
Thanks.
-- Dan
next prev parent reply other threads:[~2004-03-17 14:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 19:04 [U-Boot-Users] Patch: Support for PQ27e (8247/48/71/72) chips and MPC8272ADS board Yuli Barcohen
2004-03-13 23:54 ` Wolfgang Denk
2004-03-15 9:45 ` [U-Boot-Users] " Yuli Barcohen
2004-03-15 10:07 ` Wolfgang Denk
2004-03-15 13:25 ` Yuli Barcohen
2004-03-15 13:37 ` Wolfgang Denk
2004-03-17 11:46 ` Yuli Barcohen
2004-03-17 14:15 ` Dan Malek [this message]
2004-03-17 15:12 ` Yuli Barcohen
2004-03-17 21:18 ` Wolfgang Denk
2004-03-18 8:54 ` Yuli Barcohen
2004-03-17 17:21 ` Kumar Gala
2004-03-17 17:39 ` Yuli Barcohen
2004-03-16 6:51 ` [U-Boot-Users] " Kumar Gala
2004-03-16 7:23 ` Yuli Barcohen
2004-03-16 14:37 ` Kumar Gala
2004-03-17 10:54 ` Yuli Barcohen
2004-03-17 15:03 ` Kumar Gala
2004-03-23 21:38 ` 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=40585D94.70103@embeddededge.com \
--to=dan@embeddededge.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