All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Scharsig <js_at_ng@scharsoft.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS: AT91/AVR32]
Date: Tue, 08 Feb 2011 22:11:57 +0100	[thread overview]
Message-ID: <4D51B19D.2080600@scharsoft.de> (raw)
In-Reply-To: <4D5162B4.50606@emk-elektronik.de>

Am 08.02.2011 16:35, schrieb Reinhard Meyer:
> Hello AT91/AVR32 users and maintainers,
> 
> since relocation was introduced most ARM boards and therefore all AT91 based boards are
> inherently broken.
> 
> We also used this "opportunity" to rework most of the AT91 include files mess.
> 
> You can find the current efforts at git.denx.de/u-boot-atmel.git, branch rework110202.
> 
Dear Reinhard Meyer,

I am maintainer of eb_cpux9k2 board and if you now do the soc rework 2009.

Currently the arm920t/at91 are not touched by your rework.

I can try to update the at91rm9200.h to the atmel_xxxx name scheme and update 
the two board in arm920t/at91 tree including drivers. 
Maybe I can still send a patch this week.

But I can't test the at91rm9200ek.

A second problem is, both boards use the legacy at91rm9200 usart driver. So we could try 
to use the  atmel_usart in a second step.


best regards 


Jens Scharsig

  parent reply	other threads:[~2011-02-08 21:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-08 15:35 [U-Boot] [STATUS: AT91/AVR32] Reinhard Meyer
     [not found] ` <0F3EF05CA2A70E43B140EF090B9F97183EFDC28A@CERNXCHG22.cern.ch>
2011-02-08 16:43   ` Reinhard Meyer
2011-02-08 19:05     ` Remy Bohmer
2011-02-09  7:33     ` Uli Raich
2011-02-08 21:11 ` Jens Scharsig [this message]
2011-02-08 23:02   ` Andreas Bießmann

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=4D51B19D.2080600@scharsoft.de \
    --to=js_at_ng@scharsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.