RFC: ARM Boot standard for passing device tree blob

Ben Dooks ben-linux at fluff.org
Tue Mar 30 21:10:02 EDT 2010


On Fri, Mar 26, 2010 at 07:43:20AM -1000, Mitch Bradley wrote:
> Catalin Marinas wrote:
>> On Thu, 2010-03-25 at 21:04 +0000, Russell King - ARM Linux wrote:
>>   
>>> On Wed, Mar 24, 2010 at 09:11:56AM -0600, Grant Likely wrote:
>>>     
>>>> ===Required System State===
>>>>       
>> [...]
>>   
>>>> *IRQs disabled
>>>> *MMU off
>>>> *Instruction cache either on or off
>>>> *Data cache turned off
>>>>       
>>> Would recommend saying "Data cache(s) turned off" so that L2 cache is
>>> included.
>>>     
>>
>> There are platforms where the L2 cache is turned on by the boot monitor
>> (secure monitor) and Linux has no control over it (I think OMAP).
>>   
>
> What is the reason for turning off the data caches?  Leaving all caches  
> turned on and coherent with one another has always worked well for me at  
> the interface from firmware to a booted program.

Dealing with cache maintainace early in the kernel is difficult, you
end up with piles of ASM replicated from the arm mm to deal with
coherency, code modification due to decompression, etc.

-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.




More information about the linux-arm-kernel mailing list