From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] ARM status as of 2011-08-30
Date: Wed, 31 Aug 2011 12:25:50 +0200 [thread overview]
Message-ID: <4E5E0C2E.2030902@aribaud.net> (raw)
In-Reply-To: <20110830190817.47FA418C46FA@gemini.denx.de>
Le 30/08/2011 21:08, Wolfgang Denk a ?crit :
> Dear Albert ARIBAUD,
>
> In message<4E5D088B.7090702@aribaud.net> you wrote:
>>
>> I have just applied Wolfgang's updated ARM board removal patch set.
>>
>> Currently, u-boot-arm/master builds 182 boards, of which:
>>
>> - ELDK4.2 finds 37 boards with warnings or errors ( dnp1110 gcplus lart
>
> I think we should try and separate the errors cases from the warnings
> only ones - those boards with build errors need to be fixed, or
> removed.
Right, but the current MAKEALL output does not make it easy to sort this
out. Maybe we could change MAKEALL to distinguish between error and
warning counts (and produce LOG/*.MAKELOG, LOG/*.ERR and LOG/*.WARN
accordingly).
> We can clean up warnings then, as we go on.
Agreed. However, I'd prefer it if no ARM board produced any warning --
granted, here it *looks like* many of these warnings are inocuous, and
any new toolchain might produce some more, but if we don't keep the
warning count at zero, then a less inocuous warning could creep in
unnoticed.
>> - CodeSourcery 2010q1 finds 100 (!) boards with warnings or errors (
>
> I guess it's additional warnings. You will see even more when using
> ELDK 5.x
>
>> (Cc:ing R?my for USB stuff; for yaffs, I don't know whom I should Cc:)
>
> yeaffs is generic code, i. e. it ends up on my plate.
There you are, then. :)
>> For both CS and ELDK, there are a lot of "arm-linux-ld: stubs.o:
>> compiled for a big endian system and target is little endian
>> arm-linux-ld: failed to merge target specific data of file stubs.o"
>> which I'll look into.
>
> You need a big endian ARM compiler for the ixp systems.
Got it -- actually, it is not a compiler issue, but a library issue: CS
does compile for big-endian as well as little-endian, but does not
provide big-endian libs
(<http://www.codesourcery.com/sgpp/lite/arm/portal/kbentry36>, at least
as I understand it). Apparently ELDK4.2 does not either. Would ELDK5.0
have them? I haven't gotten around to setting it up.
>> Meanwhile, I suggest that the current u-boot-arm/master be considered
>> rc1-ready, with the effort until rc2 focused on finding and fixing
>> code-wide bugs such as those two above.
>
> Agreed.
>
>> If that is ok, I'll send out a pull request today.
>
> Thanks a lot!
Done, with a few hour's delay.
> Best regards,
>
> Wolfgang Denk
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-08-31 10:25 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 22:09 [U-Boot] [STATUS] ARM Albert ARIBAUD
2011-08-19 9:38 ` Aneesh V
2011-08-19 18:19 ` Dirk Behme
2011-08-20 11:12 ` Albert ARIBAUD
2011-08-20 15:32 ` Albert ARIBAUD
2011-08-21 7:11 ` Dirk Behme
2011-08-21 7:22 ` Albert ARIBAUD
2011-08-23 2:02 ` V, Aneesh
2011-08-21 7:46 ` Dirk Behme
2011-08-21 7:54 ` V, Aneesh
2011-08-21 7:51 ` V, Aneesh
2011-08-21 8:14 ` Albert ARIBAUD
2011-08-21 8:56 ` V, Aneesh
2011-08-21 10:13 ` Albert ARIBAUD
2011-08-22 8:15 ` Simon Schwarz
2011-08-23 11:27 ` Michael Jones
2011-08-20 11:16 ` Marek Vasut
2011-08-20 11:44 ` Albert ARIBAUD
2011-08-20 12:24 ` Marek Vasut
2011-08-20 12:54 ` Albert ARIBAUD
2011-08-20 13:33 ` Marek Vasut
2011-08-20 18:50 ` [U-Boot] [STATUS] ARM (Tegra) Mike Frysinger
2011-08-30 15:20 ` Mike Frysinger
2011-08-30 15:34 ` Albert ARIBAUD
2011-08-30 15:57 ` Simon Glass
2011-08-30 16:27 ` Simon Glass
2011-08-30 16:31 ` Albert ARIBAUD
2011-08-30 16:36 ` Simon Glass
2011-08-30 16:39 ` Albert ARIBAUD
2011-08-30 16:45 ` Simon Glass
2011-08-21 10:17 ` [U-Boot] [STATUS] ARM Dirk Behme
2011-08-30 15:58 ` [U-Boot] [STATUS] ARM status as of 2011-08-30 Albert ARIBAUD
2011-08-30 19:08 ` Wolfgang Denk
2011-08-31 10:25 ` Albert ARIBAUD [this message]
2011-08-31 19:55 ` Wolfgang Denk
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=4E5E0C2E.2030902@aribaud.net \
--to=albert.u.boot@aribaud.net \
--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