* [U-Boot] Toolchain for 0map35xx
@ 2009-04-09 15:26 Ing.G.Morandi
2009-04-09 16:02 ` Dirk Behme
2009-04-09 19:41 ` Wolfgang Denk
0 siblings, 2 replies; 4+ messages in thread
From: Ing.G.Morandi @ 2009-04-09 15:26 UTC (permalink / raw)
To: u-boot
Hello to everyone,
Few weeks ago, I've followed a thread on this list regarding the toolchain
should be used to compile code for omap 35xx.
Surfing on the net, I've also found a msg of Koen Kooi where he described a
patch to be applied on /arch/arm/Makefile in order to let gcc 4.3.x work.
Now I am not an expert of toolchain and I didn't understand what is the
actual status, thus my question is:
may I use the toolchain coming with the ELDK 4.2 to compile for omap35xx or
do I have to apply some patches?
Best Regards
Gianfranco Morandi
^ permalink raw reply [flat|nested] 4+ messages in thread
* [U-Boot] Toolchain for 0map35xx
2009-04-09 15:26 [U-Boot] Toolchain for 0map35xx Ing.G.Morandi
@ 2009-04-09 16:02 ` Dirk Behme
2009-04-10 14:45 ` Ing.G.Morandi
2009-04-09 19:41 ` Wolfgang Denk
1 sibling, 1 reply; 4+ messages in thread
From: Dirk Behme @ 2009-04-09 16:02 UTC (permalink / raw)
To: u-boot
Hi Gianfranco,
Ing.G.Morandi (Portatile) wrote:
> Hello to everyone,
>
> Few weeks ago, I've followed a thread on this list regarding the toolchain
> should be used to compile code for omap 35xx.
> Surfing on the net, I've also found a msg of Koen Kooi where he described a
> patch to be applied on /arch/arm/Makefile in order to let gcc 4.3.x work.
>
> Now I am not an expert of toolchain and I didn't understand what is the
> actual status, thus my question is:
> may I use the toolchain coming with the ELDK 4.2 to compile for omap35xx or
> do I have to apply some patches?
I don't know toolchain coming with ELDK 4.2, but for U-Boot for OMAP
35x you don't need a special compiler. A non-broken arm-linux-gcc or
similar will work. While bringing OMAP U-Boot support to mainline, we
explicitly switched to a more conservative toolchain configuration
(-march=armv5 instead of v7a) to enable more toolchains to work.
Try the toolchain you have and ask or report errors if it doesn't work.
Best regards
Dirk
Btw.: For other code, e.g. Linux user space programs which need
special optimizations, other toolchain might be necessary, though.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [U-Boot] Toolchain for 0map35xx
2009-04-09 16:02 ` Dirk Behme
@ 2009-04-10 14:45 ` Ing.G.Morandi
0 siblings, 0 replies; 4+ messages in thread
From: Ing.G.Morandi @ 2009-04-10 14:45 UTC (permalink / raw)
To: u-boot
Hi Dirk, Hi Wolfgang,
many thanks for Your suggestions.
They have been very useful.
Have a nice Eastern holidays
Gianfranco Morandi
----- Original Message -----
From: "Dirk Behme" <dirk.behme@googlemail.com>
To: "Ing.G.Morandi (Portatile)" <gianfranco.morandi@euro-studio.it>
Cc: "u-boot users" <u-boot@lists.denx.de>
Sent: Thursday, April 09, 2009 6:02 PM
Subject: Re: [U-Boot] Toolchain for 0map35xx
> Hi Gianfranco,
>
> Ing.G.Morandi (Portatile) wrote:
>> Hello to everyone,
>>
>> Few weeks ago, I've followed a thread on this list regarding the
>> toolchain should be used to compile code for omap 35xx.
>> Surfing on the net, I've also found a msg of Koen Kooi where he described
>> a patch to be applied on /arch/arm/Makefile in order to let gcc 4.3.x
>> work.
>>
>> Now I am not an expert of toolchain and I didn't understand what is the
>> actual status, thus my question is:
>> may I use the toolchain coming with the ELDK 4.2 to compile for omap35xx
>> or do I have to apply some patches?
>
> I don't know toolchain coming with ELDK 4.2, but for U-Boot for OMAP 35x
> you don't need a special compiler. A non-broken arm-linux-gcc or similar
> will work. While bringing OMAP U-Boot support to mainline, we explicitly
> switched to a more conservative toolchain configuration (-march=armv5
> instead of v7a) to enable more toolchains to work.
>
> Try the toolchain you have and ask or report errors if it doesn't work.
>
> Best regards
>
> Dirk
>
> Btw.: For other code, e.g. Linux user space programs which need special
> optimizations, other toolchain might be necessary, though.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [U-Boot] Toolchain for 0map35xx
2009-04-09 15:26 [U-Boot] Toolchain for 0map35xx Ing.G.Morandi
2009-04-09 16:02 ` Dirk Behme
@ 2009-04-09 19:41 ` Wolfgang Denk
1 sibling, 0 replies; 4+ messages in thread
From: Wolfgang Denk @ 2009-04-09 19:41 UTC (permalink / raw)
To: u-boot
Dear "Ing.G.Morandi \(Portatile\)",
In message <B4BBC786F9164F6BB1C778A5F3223A67@Thinkpad01> you wrote:
>
> Few weeks ago, I've followed a thread on this list regarding the toolchain
> should be used to compile code for omap 35xx.
> Surfing on the net, I've also found a msg of Koen Kooi where he described a
> patch to be applied on /arch/arm/Makefile in order to let gcc 4.3.x work.
>
> Now I am not an expert of toolchain and I didn't understand what is the
> actual status, thus my question is:
> may I use the toolchain coming with the ELDK 4.2 to compile for omap35xx or
> do I have to apply some patches?
I am not aware of any problems when using the ELDK to build code for
the OMAP processors. There may be benchmarks where other toolchains
give some percent betterperformance, but as far as U-Boot or Linux is
concerned that should not be a problem (if you are even able to
measure the difference).
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Keep your head and your heart going in the right direction and you
will not have to worry about your feet.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2009-04-10 14:45 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-04-09 15:26 [U-Boot] Toolchain for 0map35xx Ing.G.Morandi
2009-04-09 16:02 ` Dirk Behme
2009-04-10 14:45 ` Ing.G.Morandi
2009-04-09 19:41 ` Wolfgang Denk
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox