From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Huge update
Date: Fri, 7 Mar 2008 08:47:05 +0100 [thread overview]
Message-ID: <008a01c88027$7736d060$040514ac@atmel.com> (raw)
In-Reply-To: 46a136670803061710ka7f2c40u223e1348b1a04d21@mail.gmail.com
Hi John.
Your U-Boot patches unfortunately breaks the AT91 build.
AT91 is not well supported in the main U-Boot trunk.
The U-Boot build in target/device/Atmel/u-boot will therefore download
a prepatched version of u-boot (instead of adding 100s of kB in form
of patches).
Upgrading to mainstream u-boot will therefore ensure that almost
none of the AT91 processors will build.
Also the configuration items for u-boot are irrelevant for mainstream.
I have disabled your u-boot, but the files remain.
Please create a separate u-boot directory outside the Atmel directory and
1) ensure that you do not have any conflicts with the prepatched version
2) AT91 u-boot can selected inside the AT91 target configuration.
3) AVR32 should use the generic u-boot.
once fixed, resubmit.
It will be more complex in the future, since the AT91CAP9
will probably have good u-boot support in the near future,
so ideally the user should have a choice between
building the generic and the prepatched version.
Personally I think that putting the bootloader configuration
inside the root fs build is wrong.
Makes more sense to me to have it in the target.
Don't be dismayed by this, keep the patches coming.
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2008-03-07 7:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 1:10 [Buildroot] Huge update John Voltz
2008-03-07 2:57 ` Hamish Moffatt
2008-03-07 7:47 ` Ulf Samuelsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-07 0:04 John Voltz
2008-03-07 0:08 ` Hamish Moffatt
2008-03-06 19:16 John Voltz
2008-03-06 19:14 ` Erik Andersen
2008-03-06 20:52 ` JS
2008-03-06 23:44 ` Ulf Samuelsson
2008-03-07 8:21 ` Hans-Christian Egtvedt
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='008a01c88027$7736d060$040514ac@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