On 1 February 2012 13:04, Anthony Liguori <anth...@codemonkey.ws> wrote: > How does it race? Devices normally never touch memory so a loader device > will be the only thing mucking with memory.
The obvious one is "loader reset function wants to set starting PC to entry point of kernel/etc" vs "CPU device reset wants to set starting PC to hardware-mandated reset vector". We have this at the moment, of course, and I think we implicitly rely on reset handlers being called in order of registration... (The other irritating case is where the CPU device reset wants to read the starting PC out of memory, like the Cortex-M3, but really that one is because we don't distinguish "going into reset" from "coming out of reset".) -- PMM
