From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/8 V2] add at91 SoC access with c structures
Date: Sun, 17 Jan 2010 11:10:42 -0600 [thread overview]
Message-ID: <4B534492.5010203@windriver.com> (raw)
In-Reply-To: <4B522177.3020701@scharsoft.de>
Jens Scharsig wrote:
> * add at91 soc to arm920t, needs to join at91rm9200 into at91 arch
>
>
> Signed-off-by: Jens Scharsig <js_at_ng@scharsoft.de>
> ---
> cpu/arm920t/at91/Makefile | 47 ++++++++++
> cpu/arm920t/at91/lowlevel_init.S | 177 ++++++++++++++++++++++++++++++++++++++
> cpu/arm920t/at91/reset.c | 58 ++++++++++++
> cpu/arm920t/at91/timer.c | 166 +++++++++++++++++++++++++++++++++++
> 4 files changed, 448 insertions(+), 0 deletions(-)
> create mode 100644 cpu/arm920t/at91/Makefile
> create mode 100644 cpu/arm920t/at91/lowlevel_init.S
> create mode 100644 cpu/arm920t/at91/reset.c
> create mode 100644 cpu/arm920t/at91/timer.c
>
It is unclear why arm920t/at91rm9200 -> arm920t/at91
I am not in favor of renaming dirs or making multiple copies
of the same file.
Please make your case on the list and in the commit log of the
patch
Tom
next prev parent reply other threads:[~2010-01-17 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 20:28 [U-Boot] [PATCH 2/8 V2] add at91 SoC access with c structures Jens Scharsig
2010-01-17 17:10 ` Tom [this message]
2010-01-17 17:48 ` Jens Scharsig
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=4B534492.5010203@windriver.com \
--to=tom.rix@windriver.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