[Buildroot] Target support for Atmel ARM/AVR32
ulfs at dof.se
Thu Jan 25 12:42:20 UTC 2007
Bernhard Fischer wrote:
> On Thu, Jan 25, 2007 at 12:58:57AM +0100, Ulf Samuelsson wrote:
>> Bernhard Fischer wrote:
>>> On Wed, Jan 24, 2007 at 12:06:31PM +0100, Ulf Samuelsson wrote:
>>>> 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
>>>> 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.
>>>> 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
>>>> At the end, the result is moved to
>>>> 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?
>> My goal is to have people download the buildroot source,
>> then copy a .config file to the topdir and type "make".
>> Then everything should work without surprises.
>> "Grand-Ma" should be able to do it!
>> Many people that will uses this will be complete new to Linux and
>> the thing below looks dangerous if you want to avoid support phone
>> The question is really, will a patch be rejected if it is built up
>> as above?
> If the TODO that is mentioned in r17516 would be fixed, would that
> help that problem in any way? I, personally, don't use the concept of
> a board in the context of buildroot. Put that aside, what about this
> -) toolchain_<arch>_<subarch>_<cpu>
> -) same for build_
> -) board_<device> as default COPY_TO
> $device is target/device/*
> $arch would be generic arch e.g. i386, arm
> $subarch is the real -march=
> $cpu is the real -mtune=
That is a different problem.
I can either build an ARM based buildroot or an AVR32 based buildroot.
They will build in: build_arm and build_avr32, same for toolchain.
My problem is that I want to build for
using a common toolchain
(The toolchain is generic arm, even though I use different CPU cores)
and maybe a common root file system (today it is).
This means that
* 7 different Linux versions,
* 7 different U-boot
* 7 different bootstraps.
Possibly, the root file system should be populated differently.
When I have built a board, I want to have all binaries stored
in one place which can be easily compressed into a tarball.
Your suggestion is more for building different toolchains for different
but this is not the case.
It is a big bonus, If I do not have to recompile the root file system
packages, just because I build support for a new board.
> PS: r17516 was, for your convenience:
> buildroot mailing list
> buildroot at uclibc.org
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'
More information about the buildroot