From: Gary Thomas <gary@mlbassoc.com>
To: "Kamble, Nitin A" <nitin.a.kamble@intel.com>
Cc: Poky Project <poky@yoctoproject.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [poky] GCC 4.6.0 on ARM?
Date: Wed, 11 May 2011 05:00:48 -0600 [thread overview]
Message-ID: <4DCA6C60.6050203@mlbassoc.com> (raw)
In-Reply-To: <9DA5872FEF993D41B7173F58FCF6BE94D88F0101@orsmsx504.amr.corp.intel.com>
On 05/10/2011 09:28 PM, Kamble, Nitin A wrote:
>
>
>> -----Original Message-----
>> From: poky-bounces@yoctoproject.org [mailto:poky-
>> bounces@yoctoproject.org] On Behalf Of Gary Thomas
>> Sent: Monday, May 02, 2011 5:57 AM
>> To: Khem Raj
>> Cc: Poky Project; Patches and discussions about the oe-core layer
>> Subject: Re: [poky] GCC 4.6.0 on ARM?
>>
>> On 04/30/2011 04:10 PM, Khem Raj wrote:
>>> On Thu, Apr 28, 2011 at 11:23 AM, Khem Raj<raj.khem@gmail.com>
>> wrote:
>>>> On Thu, Apr 28, 2011 at 10:09 AM, Gary Thomas<gary@mlbassoc.com>
>> wrote:
>>>>> I got my OMAP target to build with GCC-4.6.0 using the latest
>>>>> Poky tree after a fresh rebuild. Sadly, the Linux kernel
>> (2.6.37.3)
>>>>> does not run correctly when built with this compiler. It
>>>>> fails when enumerating the USB bus :-(
>>>>>
>>>>> Are there known issues with the Linux kernel on ARM and GCC-4.6?
>>>>>
>>>>
>>>> There has been fixes on top of 4.6.0 the one we have right now is
>> vanilla
>>>> 4.6.0 release. I plan to add second set of patches but you have to
>> dig a bit
>>>> more to identify the problem
>>>>
>>>
>>> I have some updates for gcc 4.6.0
>>> they are staged in
>>>
>>> http://git.openembedded.org/cgit.cgi/openembedded-core-
>> contrib/log/?h=kraj/gcc-4.6
>>>
>>> (top 3 patches)
>>>
>>> Please test them out and if you are lucky
>>> your problem might be fixed too.
>>>
>>> All, please try these patches and provide any feedback
>>
>> I was able to build my kernel (ARM OMAP/3530 based) using this, but
>> the USB still doesn't work, so no improvement, sorry.
>
> Gary,
> Is the USB breakage is due to gcc 4.6.0 ?
Yes, that's the only change. Building the kernel from the same
source repository with 4.5.2 (using patches from you and Khem Raj)
works perfectly.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-05-11 11:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 17:09 GCC 4.6.0 on ARM? Gary Thomas
2011-04-28 18:23 ` [poky] " Khem Raj
2011-04-30 22:10 ` Khem Raj
2011-05-02 11:37 ` Gary Thomas
[not found] ` <4DBE9E61.9030206@gmail.com>
2011-05-02 22:24 ` Khem Raj
2011-05-02 12:57 ` Gary Thomas
2011-05-02 22:57 ` Khem Raj
2011-05-11 3:28 ` Kamble, Nitin A
2011-05-11 11:00 ` Gary Thomas [this message]
2011-05-11 15:35 ` Kamble, Nitin A
2011-05-11 15:39 ` Gary Thomas
[not found] ` <9DA5872FEF993D41B7173F58FCF6BE94D8A2E4FE@orsmsx504.amr.corp.intel.com>
2011-05-16 22:46 ` Gary Thomas
2011-05-17 16:56 ` Kamble, Nitin A
2011-05-11 17:03 ` Khem Raj
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=4DCA6C60.6050203@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=nitin.a.kamble@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@yoctoproject.org \
/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