On 10/03/2014 07:21 PM, Simon Glass wrote:
> On 2 October 2014 16:20, York Sun wrote:
>> Commit 294b91a5817147d4b7f47be2ac69bac2a1f26491 moved initr_malloc
>> earlier than initr_unlock_ram_in_cache. This causes issue on T4240.
>> It may be related to locked L1 d-cache and unlocked L2 cache. D-
>>
On Fri, 2014-10-03 at 21:31 -0500, Sun York-R58495 wrote:
>
> On 10/3/14 7:21 PM, "Simon Glass" wrote:
>
> >On 2 October 2014 16:20, York Sun wrote:
> >> Commit 294b91a5817147d4b7f47be2ac69bac2a1f26491 moved initr_malloc
> >> earlier than initr_unlock_ram_in_cache. This causes issue on T4240.
>
On 10/3/14 7:21 PM, "Simon Glass" wrote:
>On 2 October 2014 16:20, York Sun wrote:
>> Commit 294b91a5817147d4b7f47be2ac69bac2a1f26491 moved initr_malloc
>> earlier than initr_unlock_ram_in_cache. This causes issue on T4240.
>> It may be related to locked L1 d-cache and unlocked L2 cache. D-
>>
On 2 October 2014 16:20, York Sun wrote:
> Commit 294b91a5817147d4b7f47be2ac69bac2a1f26491 moved initr_malloc
> earlier than initr_unlock_ram_in_cache. This causes issue on T4240.
> It may be related to locked L1 d-cache and unlocked L2 cache. D-
> cache could and should be unlock earlier for norm
Commit 294b91a5817147d4b7f47be2ac69bac2a1f26491 moved initr_malloc
earlier than initr_unlock_ram_in_cache. This causes issue on T4240.
It may be related to locked L1 d-cache and unlocked L2 cache. D-
cache could and should be unlock earlier for normal operation.
This patch moves initr_unlock_ram_i
5 matches
Mail list logo