From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/u-boot/2009.01-rc1
Date: Tue, 06 Jan 2009 16:16:47 +0100 [thread overview]
Message-ID: <1231255007.32308.107.camel@elrond.atmel.com> (raw)
In-Reply-To: <87mye4qz4d.fsf@macbook.be.48ers.dk>
tis 2009-01-06 klockan 15:37 +0100 skrev Peter Korsgaard:
> >>>>> "ulf" == ulf <ulf@uclibc.org> writes:
>
> ulf> Author: ulf
> ulf> Date: 2009-01-03 00:06:13 +0000 (Sat, 03 Jan 2009)
> ulf> New Revision: 24658
>
I discovered I made a mistake and checked in the
1.3.4 patch so it will be updated later today
The original is part of the atmel 1.3.4 patch freom www.linux4sam.org
?There will be some other fixes due to the CFG->CONFIG(_SYS)
I have tested the new patches to build for all possible AT91 targets
in buildroot as well as for a PowerPC target.
Generally on patches to u-boot:
The AT91 team got zero response from the U-Boot during 2003-2005
so they dropped all attempts to submit new stuff.
After it was decided to split the responsibilities up
to several people, the submission process has improved a lot,
so the AT91 team started to be interested again last year.
The board support for AT91 processors has improved.
The AT91RM9200 has less priority on support from the product line
and has therefore not been submitted, even if patches
has been available for a long time.
Currently the merge window is closed, but I expect
to submit the board support patches and some of the
new commands end of January.
The factory default command relies heavily on
the buildroot configuration, so it may make less
sense to include that in the main u-boot trunk.
> ulf> Log:
> ulf> Add support for at91sam9g20 to U-Boot
>
> What's the upstream status of this patch?
>
next prev parent reply other threads:[~2009-01-06 15:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 0:06 [Buildroot] svn commit: trunk/buildroot/target/u-boot/2009.01-rc1 ulf at uclibc.org
2009-01-06 14:37 ` Peter Korsgaard
2009-01-06 15:16 ` Ulf Samuelsson [this message]
2009-01-06 15:26 ` Peter Korsgaard
2009-01-06 15:56 ` Ulf Samuelsson
2009-01-06 16:18 ` Peter Korsgaard
2009-01-06 17:22 ` Ulf Samuelsson
2009-01-06 18:13 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2009-01-06 16:24 ulf at uclibc.org
2009-01-06 16:24 ulf at uclibc.org
2009-01-06 16:33 ` Peter Korsgaard
2009-01-06 16:21 ulf at uclibc.org
2009-01-06 16:17 ulf at uclibc.org
2009-01-06 16:17 ulf at uclibc.org
2009-01-06 16:32 ` Peter Korsgaard
2009-01-06 16:13 ulf at uclibc.org
2009-01-06 16:10 ulf at uclibc.org
2009-01-06 16:09 ulf at uclibc.org
2009-01-03 0:05 ulf at uclibc.org
2009-01-03 0:04 ulf at uclibc.org
2009-01-06 14:39 ` Peter Korsgaard
2009-01-06 15:20 ` Ulf Samuelsson
2009-01-06 15:28 ` Peter Korsgaard
2009-01-06 16:03 ` Ulf Samuelsson
2009-01-03 0:04 ulf at uclibc.org
2009-01-03 0:03 ulf at uclibc.org
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=1231255007.32308.107.camel@elrond.atmel.com \
--to=ulf.samuelsson@atmel.com \
--cc=buildroot@busybox.net \
/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