Hello,
> It seems that all three ARM errata workarounds done in omap3 board-init
> (#454179 #430973 #621766) are solved/not longer needed e.g. in the
> AM/DM37xx chips. Other people have noticed this:
> http://e2e.ti.com/support/arm/sitara_arm/f/791/t/254742.aspx
>
>
Hi Andreas,
On 07/09/2013 05:01 PM, Andreas Naumann wrote:
It seems that all three ARM errata workarounds done in omap3 board-init
(#454179 #430973 #621766) are solved/not longer needed e.g. in the
AM/DM37xx chips. Other people have noticed this:
http://e2e.ti.com/support/arm/s
Hi,
It seems that all three ARM errata workarounds done in omap3 board-init
(#454179 #430973 #621766) are solved/not longer needed e.g. in the
AM/DM37xx chips. Other people have noticed this:
http://e2e.ti.com/support/arm/sitara_arm/f/791/t/254742.aspx
When still applying them (especcially #430
Hi Andreas,
On Tue, 09 Jul 2013 12:42:27 +0200, "Andreas Bießmann"
wrote:
> Another solution could be to read the
> silicon revision and enable erratum workarounds on that information. It
> would be a step towards single binary.
Seconded.
> Best regards
>
> Andreas Bießmann
Amicalement,
--
Hi Andreas,
On 07/09/2013 11:10 AM, Albert ARIBAUD wrote:
> Hi Andreas,
>
> On Tue, 09 Jul 2013 10:08:10 +0200, Andreas Naumann
> wrote:
>
>> Hi,
>>
>> It seems that all three ARM errata workarounds done in omap3 board-init
>> (#454179 #430973 #621766) are solved/not longer needed e.g. in the
Hi Andreas,
On Tue, 09 Jul 2013 10:08:10 +0200, Andreas Naumann
wrote:
> Hi,
>
> It seems that all three ARM errata workarounds done in omap3 board-init
> (#454179 #430973 #621766) are solved/not longer needed e.g. in the
> AM/DM37xx chips. Other people have noticed this:
> http://e2e.ti.com/
Hi,
It seems that all three ARM errata workarounds done in omap3 board-init
(#454179 #430973 #621766) are solved/not longer needed e.g. in the
AM/DM37xx chips. Other people have noticed this:
http://e2e.ti.com/support/arm/sitara_arm/f/791/t/254742.aspx
When still applying them (especcially #4
7 matches
Mail list logo