From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Cleanup cpu/arm920t
Date: Mon, 09 Aug 2004 22:07:23 +0200 [thread overview]
Message-ID: <20040809200728.57C84C109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 09 Aug 2004 08:49:28 +0200." <41171E78.6070101@imc-berlin.de>
In message <41171E78.6070101@imc-berlin.de> you wrote:
>
> Accepted. I found some processor specific driver code in drivers/ (like
> s3c24x0_i2c.c s3c4510b_eth.c s3c4510b_eth.h s3c4510b_uart.c
> s3c4510b_uart.h) so I thought it becomes "common practice" to put peripheral
Yes - this has sneaked in because there was no better solution. Given
the planned restructuring this belongs to cpu/XXX/ as well.
> driver code for uart or ethernet (although it might be processor specific)
> into drivers/.
No, I don't want to have this. drivers/ is for common (processor
independent) conde.
> > Be careful. Do you really think this is a good idea? The 52xx USB
> > code suffers from the endinaess problem of the 52xx. I'm not sure if
> > this is a good base for common code.
>
> The only difference I found is
Agreed - so please use the MPC5200 version as base, not the other
one.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de
Hiring experienced unix people is like a built-in filter against
idiots. Hiring experienced NT people provides no such guarantee.
-- Miguel Cruz in WgL96.349$CC.122704 at typhoon2.ba-dsg.net
next prev parent reply other threads:[~2004-08-09 20:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 16:02 [U-Boot-Users] [PATCH] Cleanup cpu/arm920t Steven Scholz
2004-08-06 16:41 ` Wolfgang Denk
2004-08-09 6:49 ` Steven Scholz
2004-08-09 9:02 ` llandre
2004-08-09 20:08 ` Wolfgang Denk
2004-08-09 20:07 ` Wolfgang Denk [this message]
2004-08-09 10:50 ` llandre
2004-08-09 20:10 ` Wolfgang Denk
2004-08-10 6:12 ` Steven Scholz
2004-08-10 7:44 ` Wolfgang Denk
2004-08-10 7:50 ` Steven Scholz
2004-08-10 8:24 ` Wolfgang Denk
2004-08-10 9:09 ` Steven Scholz
2004-08-11 10:45 ` Steven Scholz
2004-08-11 14:23 ` llandre
2004-08-11 15:02 ` Wolfgang Denk
2004-08-11 15:53 ` Steven Scholz
2004-08-11 16:06 ` Steven Scholz
2004-08-11 17:09 ` Wolfgang Denk
2004-08-11 16:31 ` Wolfgang Denk
2004-08-11 16:34 ` llandre
2004-08-11 17:10 ` Wolfgang Denk
2004-08-11 17:28 ` llandre
2004-08-11 18:10 ` Wolfgang Denk
2004-08-12 7:44 ` llandre
2004-08-12 11:56 ` Steven Scholz
2004-08-12 12:54 ` Wolfgang Denk
2004-08-12 14:10 ` Steven Scholz
2004-08-10 7:34 ` llandre
2004-08-10 8:22 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2004-08-10 6:31 Mészáros Lajos
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=20040809200728.57C84C109F@atlas.denx.de \
--to=wd@denx.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