From: Alexander Holler <holler@ahsoftware.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] OMAP3: relocation and bss usage (timer, gpmc, ...)
Date: Tue, 30 Nov 2010 23:59:16 +0100 [thread overview]
Message-ID: <4CF581C4.7050704@ahsoftware.de> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB5930247AFD391@dbde02.ent.ti.com>
Hello,
Am 30.11.2010 19:21, schrieb Premi, Sanjeev:
> For omap3evm - I was getting multiple errors during compilation.
> Most for undefined symbols - which existed in the compiled objects
> but, I suspect, not in right sequence.
>
> Haven't still been able to look back at these errors; still surprised
> to find that you had the code running on beagle.
When I'm compiling the current master with gcc 4.3.5 (using binutils
2.20.1) u.boot currently works (at least it loads and starts the kernel
from mmc).
But I assume that is just some lucky condition because 4.3.5 does some
things different than 4.5.1 which causes some sill existent bugs to not
appear.
Browsing the source to search those problems (which arise when I'm using
gcc 4.5.1) is just some freetime activity I'm doing when I feel bored,
without spending much time. For actually working on those problems I
would have to build a TI<->ARM JTAG cable, which is still on my list of
low priority todos. ;)
Regards,
Alexander
next prev parent reply other threads:[~2010-11-30 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 16:28 [U-Boot] OMAP3: relocation and bss usage (timer, gpmc, ...) Alexander Holler
2010-11-30 18:21 ` Premi, Sanjeev
2010-11-30 22:59 ` Alexander Holler [this message]
2010-12-02 13:33 ` zfsdk
2010-12-02 14:56 ` Alexander Holler
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=4CF581C4.7050704@ahsoftware.de \
--to=holler@ahsoftware.de \
--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