From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARMv7: Fix linker errors across toolchain versions
Date: Thu, 02 Dec 2010 09:26:36 +0100 [thread overview]
Message-ID: <4CF7583C.7000001@free.fr> (raw)
In-Reply-To: <20101202081320.DBD5FEA6600@gemini.denx.de>
Le 02/12/2010 09:13, Wolfgang Denk a ?crit :
> Dear Albert ARIBAUD,
>
> In message<4CF74FED.2030102@free.fr> you wrote:
>>
>> BTW... Why on Earth is it an uint8? Probably a space saving measure, but
>> one I think is not really fruitful, because of probable paddings and
>> alignments; making it an int would allow using smsc_id directly as
>> values for the OMAP3EVM_BOARD_GEN_1 and OMAP3EVM_BOARD_GEN_2...
>>
>> ... plus it removes the linker warning!
>
> Oops. Why would this make a difference?
Alignement issues, possibly, although we do align the location pointer
before the overlay point -- or some bug in the linker.
>> I thus suggest turning omap3_evm_version from uint8 to int and get on
>> with debugging the board.
>
> No, I don't think this is a good idea as it just papers over an
> existing problem.
Oh--I did not mean to forget the linker warning thing. Just separate the
issues, because I think this particular linker warning is unrelated with
getting the board working.
So Sanjeev would change the u8 to an int and proceed with board debug,
and I would investigate this issue -- actually, try and find a minimal
example that I could go to the binutils list with rather than a
full-blown u-boot tree.
> Does it help when you change the "*(.bss)" in
> "arch/arm/cpu/armv7/u-boot.lds" into "*(.*bss)"
> (so it also includes any .sbss objects) ?
No change.
> Best regards,
>
> Wolfgang Denk
Amicalement,
--
Albert.
next prev parent reply other threads:[~2010-12-02 8:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 15:17 [U-Boot] [PATCH] ARMv7: Fix linker errors across toolchain versions Sanjeev Premi
2010-12-01 15:58 ` Premi, Sanjeev
2010-12-01 19:55 ` Wolfgang Denk
2010-12-01 17:13 ` Albert ARIBAUD
2010-12-01 17:19 ` Premi, Sanjeev
2010-12-01 17:32 ` Albert ARIBAUD
2010-12-01 18:19 ` Premi, Sanjeev
2010-12-01 18:36 ` Albert ARIBAUD
2010-12-01 18:54 ` Premi, Sanjeev
2010-12-01 21:39 ` Albert ARIBAUD
2010-12-02 6:59 ` Albert ARIBAUD
2010-12-02 7:34 ` Wolfgang Denk
2010-12-02 7:51 ` Albert ARIBAUD
2010-12-02 8:13 ` Wolfgang Denk
2010-12-02 8:26 ` Albert ARIBAUD [this message]
2010-12-02 8:30 ` Premi, Sanjeev
2010-12-02 8:42 ` Albert ARIBAUD
2010-12-02 11:25 ` Premi, Sanjeev
2010-12-02 11:39 ` Wolfgang Denk
2010-12-02 12:45 ` Premi, Sanjeev
2010-12-02 14:00 ` Wolfgang Denk
2010-12-02 8:56 ` Wolfgang Denk
2010-12-02 8:14 ` Premi, Sanjeev
2010-12-02 8:18 ` Premi, Sanjeev
2010-12-01 20:08 ` Wolfgang Denk
2010-12-01 18:23 ` Premi, Sanjeev
2010-12-01 18:28 ` Albert ARIBAUD
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=4CF7583C.7000001@free.fr \
--to=albert.aribaud@free.fr \
--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