On Tue, Dec 18, 2012 at 04:42:08PM +, Alexander Spyridakis wrote:
> On 18 December 2012 12:10, Liviu Dudau
> mailto:liviu.du...@arm.com>> wrote:
> Hi Alexander,
>
> Could you explain with a bit more detail what's the intended usage
> scenario for this code?
>
> If you have BootMonitor, it is
On 18 December 2012 16:42, Alexander Spyridakis
wrote:
> On 18 December 2012 12:10, Liviu Dudau wrote:
>> If you have BootMonitor, it is already capable of booting the kernel.
> The major difference is that BootMonitor doesn't initialize Hyp mode and
> without it we can't start KVM.
It would be
On 18 December 2012 12:10, Liviu Dudau wrote:
> Hi Alexander,
>
> Could you explain with a bit more detail what's the intended usage
> scenario for this code?
>
>
If you have BootMonitor, it is already capable of booting the kernel.
>
The major difference is that BootMonitor doesn't initialize
Hi Alexander,
Could you explain with a bit more detail what's the intended usage
scenario for this code?
If you have BootMonitor, it is already capable of booting the kernel.
Regards,
Liviu
On Wed, Dec 12, 2012 at 08:35:10PM +, Alexander Spyridakis wrote:
> - A new output binary (board.a
- A new output binary (board.axf) has been added exclusively for
board usage, which uses a different linker script (board.lds.S).
- BootMonitor has already placed secondary CPUs in wfi state,
generate a software interrupt first and point other cores to
jump to the right location by writing th
