From: Ulf Samuelsson <ulfs@dof.se>
To: buildroot@busybox.net
Subject: [Buildroot] Target support for Atmel ARM/AVR32
Date: Wed, 24 Jan 2007 12:06:31 +0100 [thread overview]
Message-ID: <014901c73faa$8e9c8100$01c4af0a@atmel.com> (raw)
I am hoping to add Target support for a number of Atmel Development board,
but before I do that, I would like to discuss how this is done.
Would like to separate building the root file system from other utilities,
since the "build_<arch>" directory is overcrowded.
Currently I am using a "target_build_<arch>" directory.
In this directory, I create a subdirectory for each target_board.
I.E:
buildroot/target_build_arm
at91rm9200dk
at91rm9200df
at91rm9200ek
at91sam9260ek
at91sam9261ek
at91sam9262ek
or
buildroot/target_build_avr32
atstk1002
In the target_build_<arch>/<target_board> directory
I download patches for Linux/U-Boot before I apply them
and then build
* Bootstrap
* U-Boot
* Linux
* Other Utitlties
in that directory.
The results are renamed to show <target_board> and date.
Would like to move "buildroot/build_<arch>/root" to
"buildroot/target_build_<arch>/<target_board>/root" as well,
but have not yet gotten this to work.
(This will allow me to have different contents for different boards)
At the end, the result is moved to "buildroot/binaries/<target_board>"
so that I have easy way to create a delivery by just compressing
that directory into a tarball.
Does this seem to be a reasonable approach?
Best Regards,
Ulf Samuelsson
ulf at atmel.com
GSM: +46 (706) 22 44 57
Tel: +46 (8) 441 54 22
Fax: +46 (8) 441 54 29
Mail: Box 2033 174 02 Sundbyberg
Visit: Kavalleriv?gen 24
174 58 Sundbyberg'
Sweden
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20070124/edc5a8b4/attachment.html
next reply other threads:[~2007-01-24 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 11:06 Ulf Samuelsson [this message]
2007-01-24 23:37 ` [Buildroot] Target support for Atmel ARM/AVR32 Bernhard Fischer
2007-01-24 23:58 ` Ulf Samuelsson
2007-01-25 9:04 ` Bernhard Fischer
2007-01-25 12:42 ` Ulf Samuelsson
2007-01-25 13:47 ` Bernhard Fischer
2007-01-25 14:07 ` Bernhard Fischer
2007-01-25 15:28 ` 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='014901c73faa$8e9c8100$01c4af0a@atmel.com' \
--to=ulfs@dof.se \
--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