From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] ARM
Date: Sun, 21 Aug 2011 09:46:50 +0200 [thread overview]
Message-ID: <4E50B7EA.8090307@googlemail.com> (raw)
In-Reply-To: <4E4FD3A0.7060309@aribaud.net>
On 20.08.2011 17:32, Albert ARIBAUD wrote:
> Hi all,
>
> Le 20/08/2011 13:12, Albert ARIBAUD a ?crit :
...
>>>> 2. http://patchwork.ozlabs.org/patch/108865/
>
> This one kind of half-fixes the two boards it touches: they now build
> but with warnings, all the same, of which here is one:
>
> clocks.c:274: warning: comparison is always true due to limited range of
> data type
>
> I'll put this one on hold unless somebody can tell me what's going on.
First, the patch 108865 above fixes a linking issue with the SPL for
these boards. So I think that this is independent of the clocks.c
warning you report above. That would mean it would be worth to apply
108865 to fix at least the linking issue.
Second, applying 108865 to the recent u-boot-arm.git doesn't show any
clocks.c warning for me [1]. Could this be tool chain dependent? I
tried it with [2] and [3], without any warning.
Btw, about which clocks.c (directory) do we talk?
Best regards
Dirk
[1]
> cat include/configs/omap4_sdp4430.h | grep CONFIG_SPL_MAX_SIZE
#define CONFIG_SPL_MAX_SIZE (38 * 1024)
> ./MAKEALL omap4_sdp4430
Configuring for omap4_sdp4430 board...
text data bss dec hex filename
191043 4468 202816 398327 613f7 ./u-boot
--------------------- SUMMARY ----------------------------
Boards compiled: 1
----------------------------------------------------------
> cat include/configs/omap4_panda.h | grep CONFIG_SPL_MAX_SIZE
#define CONFIG_SPL_MAX_SIZE (38 * 1024)
> ./MAKEALL omap4_panda
Configuring for omap4_panda board...
text data bss dec hex filename
189478 4380 202820 396678 60d86 ./u-boot
--------------------- SUMMARY ----------------------------
Boards compiled: 1
----------------------------------------------------------
[2] gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203)
[3] gcc version 4.5.1 (Sourcery G++ Lite 2010.09-50)
next prev parent reply other threads:[~2011-08-21 7:46 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 [this message]
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
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=4E50B7EA.8090307@googlemail.com \
--to=dirk.behme@googlemail.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