From: Grant Erickson <marathon96@gmail.com>
To: "Premi, Sanjeev" <premi@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Which toolchain are we using?
Date: Thu, 10 Nov 2011 09:07:04 -0800 [thread overview]
Message-ID: <CAE144B8.32218%marathon96@gmail.com> (raw)
In-Reply-To: <E28AAFD00EFAA646AE3DF9B89CD24A8903B687@DBDE01.ent.ti.com>
On 11/10/11 12:47 AM, Premi, Sanjeev wrote:
> I have been running latest linux-omap/master on OMAP3EVM (boot from MMC).
> When building with CodeSourcery 2011.03-41, I see frequent "hangs" just
> after "Uncompressing Linux... done, booting the kernel"
>
> However, builds with CodeSourcery 2009q1-203 boot consistently all the
> time.
>
> Before trying to investigate further, wanted to know if someone else has
> seen the problem. If no, which toolchain is being used.
Sanjeev:
I've seen this behavior with kernels as far back as 2.6.32. The solutions
explored in discussions on the Web seem to be around soft- vs. hardware
alignment exception handling.
Mentor is aware of the issue but has no specific recommendations at this
time.
Best,
Grant
prev parent reply other threads:[~2011-11-10 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 8:47 Which toolchain are we using? Premi, Sanjeev
2011-11-10 17:07 ` Grant Erickson [this message]
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=CAE144B8.32218%marathon96@gmail.com \
--to=marathon96@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=premi@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.