From: Steven Scholz <steven.scholz@imc-berlin.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: nomen est omen: i.MX or mc9329 ?
Date: Mon, 28 Jun 2004 14:14:34 +0200 [thread overview]
Message-ID: <40E00BAA.9060101@imc-berlin.de> (raw)
In-Reply-To: <20040628105102.GB14287@pengutronix.de>
Robert Schwebel wrote:
> On Mon, Jun 28, 2004 at 11:35:01AM +0200, Wolfgang Denk wrote:
>
>>In U-Boot we just split in "cpu" and "board".
>
>
> Which is no good idea. CPU is ARM920T and each and every board copies
> everything it needs from other boards.
But still we should add it this way right now to get it into CVS a.s.a.p. so
other people can test your patch and contribute to it. Following "release
early, release often" policy.
I know it is "no good idea" (TM). But it's the same for the AT91RM9200 -
which is ARM9 too.
We could clean up and reconstruct later when we know how to do it right.
BTW: Does your patch remove the iMX stuff already in CVS?
Or should Wolfgang delete this patch:
* Patch by Ming-Len Wu, 09 Jun 2004:
Add suppport for MC9328 (Dargonball) CPU and Motorola MX1ADS board
after/before applying yours?
Steven
next prev parent reply other threads:[~2004-06-28 12:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-27 11:25 [U-Boot-Users] nomen est omen: i.MX or mc9329 ? Steven Scholz
2004-06-27 18:18 ` [U-Boot-Users] " Robert Schwebel
2004-06-28 7:11 ` Steven Scholz
2004-06-28 7:19 ` llandre
2004-06-28 9:20 ` Robert Schwebel
2004-06-28 9:31 ` Steven Scholz
2004-06-28 9:35 ` Wolfgang Denk
2004-06-28 10:51 ` Robert Schwebel
2004-06-28 11:37 ` Wolfgang Denk
2004-06-28 12:38 ` Robert Schwebel
2004-06-28 14:10 ` Wolfgang Denk
2004-06-28 14:17 ` Steven Scholz
2004-06-28 12:14 ` Steven Scholz [this message]
2004-06-28 13:01 ` Robert Schwebel
2004-06-28 15:15 ` Sascha Hauer
2004-06-28 9:57 ` llandre
2004-06-28 10:09 ` Steven Scholz
2004-06-28 11:07 ` llandre
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=40E00BAA.9060101@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--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