From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] AT91 Rework
Date: Thu, 05 Nov 2009 21:12:03 +0100 [thread overview]
Message-ID: <20091105201203.CF4E03F6EC@gemini.denx.de> (raw)
In-Reply-To: <4AF1D190.1010800@scharsoft.de>
Dear Jens Scharsig,
In message <4AF1D190.1010800@scharsoft.de> you wrote:
>
> We discussed the AT91 defs replaced by C structures.
> I have checked the AT91 and the AT91RM9200 tree.
> I have planned the following procedure:
>
> 1. Add the CONFIG_AT_LEGACY to all affected boards
> (until the board is updated)
> 2. Put an warinig to all files that use old defs
> 3. enclose the old def's with #ifdef CONFIG_AT_LEGACY
> 4. Add new C stuctures to header files
> 5. update affected common and driver files
> 6. next steps t.b.d
THis sounds good to me.
> An additional aim of the revision should be the union
> of the AT91 and AT91RM9200 tree. Some part like UART,
> SPI; PIO and so one are the same. Only a lot of devices
> like MAC are different.
> But I can't see, when this work will be done.
I understand this. Let's focus on what you can do now. Evey bit of
improvement is highly welcome.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"Never face facts; if you do, you'll never get up in the morning."
- Marlo Thomas
next prev parent reply other threads:[~2009-11-05 20:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 19:10 [U-Boot] AT91 Rework Jens Scharsig
2009-11-04 20:58 ` Jens Scharsig
2009-11-05 17:06 ` Wolfgang Denk
2009-11-05 18:55 ` Jens Scharsig
2009-11-05 20:12 ` Wolfgang Denk [this message]
2009-11-07 19:37 ` Jens Scharsig
2009-11-09 21:45 ` 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=20091105201203.CF4E03F6EC@gemini.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