From: Ulf Samuelsson <ulf@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] New version of AT91-Bootstrap forAT91SAM92xU-Boot/Buildroot/Linux users
Date: Mon, 26 Mar 2007 09:17:27 +0200 [thread overview]
Message-ID: <00a001c76f77$382b4660$01c4af0a@Glamdring> (raw)
In-Reply-To: 20070326000519.9337335260B@atlas.denx.de
> In message <4606F5D2.4060005@atmel.com> you wrote:
>>
>> Since I am using buildroot, I want everything to compile using uclibc,
>> NWFPE and a dynamic C library.
>
> Please correct me if I'm wrong, but we are talking about a < 4kB
> standalone NAND / dataflash bootstrap loader here, right?
>
> I don't think you use *any* of NWFPE or uclibc specific code in it,
> nor any "dynamic C library".
>
>
> Requiring to use "uclibc, NWFPE and a dynamic C library" for such a
> piece of code seems fundamentally broken to me.
>
The requirement is not that at91-bootstrap must use this.
The requirement is that it is *able* to be built by this.
I am using buildroot with extensions, and my requirement is that
I want to have one single package, which can as output generate
* Single Cross Compiler able to build all things below
* Standalone NAND/Dataflash bootloader
* U-Boot
* Linux Kernel
* Root File System
The Linux kernel is built using NWFPE, uclibc and dynamic C library.
Thus I need to be able to use the same toolchain for the rest to fulfil the
goal.
Not including the C library routines memset, memcpy and div
*forces* you to use the C library, and you cant have a dynamic loaded
library in 4 kB, so it has to be static and thus it fails .
The new at91-bootstrap, with those routines can be built
* using NWFPE or softfloat - did not matter in the old version either
* static or dynamic c library - old version HAD to have a static library
* cross-compiler compiled for uclibc, glibc or newlib
The NWFPE issue is with U-Boot.
U-Boot cannot compile, since it has -msoftfloat hard-wired
and this is really not neccessary. By removing the -msoftfloat
you can compile using a NWFPE enabled compiler.
Due to dataflash sector boundaries, the natural size for U-Boot + Loader is
256 kB or less. I did not check the effect on U-Boot code size
due to NWFPE enabled, but there should be little or none FPU code
in U-Boot.
It is more important to me to have a single toolchain, and it will be
Linux needs which determines the toolchain.
> Best regards,
>
> Wolfgang Denk
>
> --
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:
AT89 C51 Applications Group: mailto:micro.hotline at nto.atmel.com
AT90 AVR Applications Group: mailto:avr at atmel.com
AT91 ARM Applications Group: mailto:at91support at atmel.com
FPSLIC Application Group: mailto:fpslic at atmel.com Best AVR
link: www.avrfreaks.net
next prev parent reply other threads:[~2007-03-26 7:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-25 15:43 [U-Boot-Users] New version of AT91-Bootstrap for AT91SAM92x U-Boot/Buildroot/Linux users Ulf Samuelsson
2007-03-25 15:50 ` Ulf Samuelsson
2007-03-25 20:42 ` Wolfgang Denk
2007-03-25 21:00 ` [U-Boot-Users] New version of AT91-Bootstrap for AT91SAM92xU-Boot/Buildroot/Linux users Ulf Samuelsson
2007-03-25 22:01 ` Wolfgang Denk
2007-03-25 22:10 ` Ulf Samuelsson
2007-03-26 0:01 ` Wolfgang Denk
2007-03-25 22:24 ` Andreas Schweigstill
2007-03-25 22:21 ` Ulf Samuelsson
2007-03-26 0:05 ` Wolfgang Denk
2007-03-26 7:17 ` Ulf Samuelsson [this message]
2007-03-26 11:42 ` [U-Boot-Users] New version of AT91-Bootstrap forAT91SAM92xU-Boot/Buildroot/Linux users Wolfgang Denk
2007-03-26 13:07 ` [U-Boot-Users] New version of AT91-BootstrapforAT91SAM92xU-Boot/Buildroot/Linux users Ulf Samuelsson
2007-03-26 14:35 ` Wolfgang Denk
2007-03-26 16:29 ` 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='00a001c76f77$382b4660$01c4af0a@Glamdring' \
--to=ulf@atmel.com \
--cc=u-boot@lists.denx.de \
/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