From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Atmel pull request?
Date: Thu, 09 Jun 2011 11:03:19 +0200 [thread overview]
Message-ID: <4DF08C57.8080901@gmail.com> (raw)
In-Reply-To: <4DF0727E.7010209@eukrea.com>
Dear Eric B?nard,
Am 09.06.2011 09:13, schrieb Eric B?nard:
> Hi,
>
> On 09/06/2011 09:06, Wolfgang Denk wrote:
>> what are the chances to see a pull request for the Atmel boards any
>> time soon? As is, theyu still form the majority of broken ARM boards,
>> and I would like to get the release out as soon as possible.
>>
>> So I'd appreciate if we could have your pull request ASAP, then I
>> could make a -rc3 and allow for a few days of testing, before
>> releasing v2011.06.
>>
> And the clock update for AT91RM9200 :
> http://patchwork.ozlabs.org/patch/99344/
> http://patchwork.ozlabs.org/patch/99550/
These are not really required. These two are the first steps to get
atmel_usart working (I've got it now since yesterday evening on my
at91rm9200ek!). After another patch (replace at91rm9200_usart by
atmel_usart) we can remove at91rm9200_usart. The next step would be to
remove the whole a/a/c/arm920t/at91rm9200 directory and complete the
transition to at91 for at91rm9200 devices as described in README.at91-soc.
But I do not want to get these changes in precipitately. I'm fine with
an integration for 2011.09.
@Wolfgang: Deletion of defective ARM boards will start after 2011.06
release. Is that correct?
regards
Andreas Bie?mann
next prev parent reply other threads:[~2011-06-09 9:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 7:06 [U-Boot] Atmel pull request? Wolfgang Denk
2011-06-09 7:13 ` Eric Bénard
2011-06-09 9:03 ` Andreas Bießmann [this message]
2011-06-09 11:17 ` Wolfgang Denk
2011-06-09 7:59 ` Reinhard Meyer
2011-06-09 11:11 ` 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=4DF08C57.8080901@gmail.com \
--to=andreas.devel@googlemail.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 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.