>>> For omap34/35xx class hardware definitely turn on
>>> CONFIG_ARM_ERRATA_430973=y
>>>
>>> When using a mix of arm/thumb application binaries on this core.
I can confirm that this fixed my problem. The other two errata seem to have
no noticeable effect, e.g. not using them doesn't cause cras
Email client got the best of me again. Sorry, Robert, for sending this to you
twice. First, a note on my earlier situation:
I just had one end-to-end build finish successfully, but it
caused htop (a completely independent process) to die. Says it gave me
a core dump. Without a kernel core dump thi
On Mon, Sep 24, 2012 at 12:14 PM, Ash Charles wrote:
> On Fri, Sep 21, 2012 at 2:48 PM, Robert Nelson
> wrote:
>> For omap34/35xx class hardware definitely turn on
>> CONFIG_ARM_ERRATA_430973=y
>>
>> When using a mix of arm/thumb application binaries on this core.
> Thanks Robert. Do you kn
On Fri, Sep 21, 2012 at 2:48 PM, Robert Nelson wrote:
> For omap34/35xx class hardware definitely turn on
> CONFIG_ARM_ERRATA_430973=y
>
> When using a mix of arm/thumb application binaries on this core.
Thanks Robert. Do you know of any references for these errata beyond
just the kernel conf
On Thu, Sep 20, 2012 at 7:33 PM, Ash Charles wrote:
> Like Jeff mentioned, I also saw some illegal instructions on early
> linaro builds but didn't pursue it at the time. I just did a little
> digging online and there was some mention of ARM errata causing issues
> ( https://bugs.launchpad.net/ub
Like Jeff mentioned, I also saw some illegal instructions on early
linaro builds but didn't pursue it at the time. I just did a little
digging online and there was some mention of ARM errata causing issues
( https://bugs.launchpad.net/ubuntu/+source/fakeroot/+bug/495536)
Based on,
https://github.
