From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/target/u-boot/2009.01-rc1
Date: Tue, 06 Jan 2009 16:26:17 +0100 [thread overview]
Message-ID: <874p0cpiau.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1231255007.32308.107.camel@elrond.atmel.com> (Ulf Samuelsson's message of "Tue\, 06 Jan 2009 16\:16\:47 +0100")
>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
Hi,
Ulf> I discovered I made a mistake and checked in the
Ulf> 1.3.4 patch so it will be updated later today
Ulf> The original is part of the atmel 1.3.4 patch freom www.linux4sam.org
Why is that not in mainline U-Boot?
Ulf> ?There will be some other fixes due to the CFG->CONFIG(_SYS)
Yes, that's what I mentioned last week. This again will complicate
stuff when we're supporting 3+ U-Boot versions.
Ulf> I have tested the new patches to build for all possible AT91 targets
Ulf> in buildroot as well as for a PowerPC target.
Ulf> Generally on patches to u-boot:
Ulf> The AT91 team got zero response from the U-Boot during 2003-2005
Ulf> so they dropped all attempts to submit new stuff.
They just have to try again like the rest of us, or maybe ping wdenx
on irc.
I know he can be a pain, but that's his job.
Ulf> After it was decided to split the responsibilities up
Ulf> to several people, the submission process has improved a lot,
Ulf> so the AT91 team started to be interested again last year.
Ulf> The board support for AT91 processors has improved.
Ulf> The AT91RM9200 has less priority on support from the product line
Ulf> and has therefore not been submitted, even if patches
Ulf> has been available for a long time.
Ulf> Currently the merge window is closed, but I expect
Ulf> to submit the board support patches and some of the
Ulf> new commands end of January.
Ok, please do so. There's afaik nothing stopping you from submitting
patches now so they can be integrated by the arm/at91 subtree
maintainer.
Ulf> The factory default command relies heavily on
Ulf> the buildroot configuration, so it may make less
Ulf> sense to include that in the main u-boot trunk.
What's the point of it? Is it any different than simply erasing the
environment and resetting the board?
I don't like us carrying feature patches in buildroot.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-01-06 15:26 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
2009-01-06 15:26 ` Peter Korsgaard [this message]
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=874p0cpiau.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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