From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] BSP patch
Date: Mon, 30 Apr 2007 15:37:13 +0200 [thread overview]
Message-ID: <016301c78b2c$b1b835d0$0402a8c0@atmel.com> (raw)
In-Reply-To: 20070322164017.GB3907@codepoet.org
> On Thu Mar 22, 2007 at 02:53:12PM +0100, Ulf Samuelsson wrote:
>>
>> >>The BSP patch also put some structure on where the result ends up.
>> >>Today everything is stored in the top directory, but if you
>> >>want to build multiple boards, then you are going to get a lot of clutter.
>> >
>> > We need to better differentiate between arch and cpu (generally, not in
>> > your board support patch).
>> >
>> > Applying your patch now locally. Let's see..
>> >
>>
>> Thank You,
>>
>> So far the patch does not create anything, only defines locations.
>>
>> The beef is in the patches that follows
>> but I plan to submit the AVR32 toolset patches first.
>>
>> The idea is to avoid keeping the toolset patches
>> inside the buildroot,and instead download the patches
>> before they are applied.
>
> Mind sharing the the next patchset with us, so we can see where
> you are going with this? I do like the general idea and I
> recognize the need to make changes such as you describe. But I
> would like to have a chance to review the actual changes you plan
> to implement should this be applied...
>
> -Erik
I did send you my preliminary buildroot quite some time ago,
and published a script which downloads and build buildroot
one week ago.
This new script will build the following board:
* at91rm9200df, at91sam9260dfc, at91sam9261ek, at91sam9263ek
(Fragments of avr32 support is there but not tested lately)
Except for the root file system (in ext2/jffs2) it also builds:
* linux-2.6.20.4 now defined in target/linux/Config.in; Makefile.in
* u-boot-1.2.0
* at91bootstrap-2.3
* datflashboot-1.05
everything "configurable" or board dependent builds in the
target_build_$BR2_ARCH)/$(BR2_HOSTNAME)
(Linux/U-boot/Busybox/root/at91bootstrap/dataflashboot)
and results are published in
binaries/$(BR2_HOSTNAME)
Note that BR2_HOSTNAME is used instead of BR2_BOARD_NAME
since they refer to two different things.
You can build several versions of the same board so
you can have several .config files with a common BR2_BOARD_NAME
but BR2_HOSTNAME differs.
What else is required to move on ?
Best Regards
Ulf Samuelsson ulf at atmel.com
Atmel Nordic AB
Mail: Box 2033, 174 02 Sundbyberg, Sweden
Visit: Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22 Fax +46 (8) 441 54 29
GSM +46 (706) 22 44 57
Technical support when I am not available:
AT90 AVR Applications Group: mailto:avr at atmel.com
AT91 ARM Applications Group: mailto:at91support at atmel.com
AVR32 Applications Group mailto:avr32 at atmel.com
http://www.avrfreaks.net/; http://avr32linux.org/
http://www.at91.com/ ; ftp://at91dist:distrib at 81.80.104.162/
next prev parent reply other threads:[~2007-04-30 13:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 22:24 [Buildroot] BSP patch Ulf Samuelsson
2007-03-21 22:43 ` Bernhard Fischer
2007-03-21 23:13 ` Ulf Samuelsson
2007-03-22 13:26 ` Bernhard Fischer
2007-03-22 13:53 ` Ulf Samuelsson
2007-03-22 16:40 ` Erik Andersen
2007-03-22 17:24 ` Ulf Samuelsson
2007-04-30 13:37 ` Ulf Samuelsson [this message]
2007-03-29 10:30 ` Ulf Samuelsson
2007-04-10 12:18 ` Bernhard Fischer
2007-04-10 13:22 ` Ulf Samuelsson
2007-04-12 11:02 ` Haavard Skinnemoen
2007-03-21 23:16 ` Ulf Samuelsson
2007-03-22 16:30 ` Erik Andersen
-- strict thread matches above, loose matches on Subject: below --
2007-04-16 13:57 Ulf Samuelsson
2007-02-16 0:25 [Buildroot] difference between this list and gmane? Daniel Ng
2007-02-16 9:36 ` Bernhard Fischer
2007-02-16 10:18 ` [Buildroot] BSP patch Ulf Samuelsson
2007-01-25 22:44 [Buildroot] (no subject) Ulf Samuelsson
2007-01-28 22:18 ` Bernhard Fischer
2007-01-29 0:26 ` [Buildroot] BSP patch Ulf Samuelsson
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='016301c78b2c$b1b835d0$0402a8c0@atmel.com' \
--to=ulf@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