On 31 October 2015 at 03:40, Peter Crosthwaite
wrote:
> On Fri, Oct 30, 2015 at 2:14 PM, Peter Maydell
> wrote:
>> On 30 October 2015 at 20:59, Peter Crosthwaite
>> wrote:
>>> On Fri, Oct 30, 2015 at 1:49 PM, Peter Maydell
>>> wrote:
Is it an error for the board to set secure_board_setup
On Fri, Oct 30, 2015 at 2:14 PM, Peter Maydell wrote:
> On 30 October 2015 at 20:59, Peter Crosthwaite
> wrote:
>> On Fri, Oct 30, 2015 at 1:49 PM, Peter Maydell
>> wrote:
>>> I thought you were planning to have the generic code do the
>>> S->NS transition; but I guess it works better in the bo
On Fri, Oct 30, 2015 at 3:04 PM, Peter Maydell wrote:
> On 30 October 2015 at 21:24, Peter Crosthwaite
> wrote:
>> On Fri, Oct 30, 2015 at 2:14 PM, Peter Maydell
>> wrote:
>>> The other question is what happens on a board like this if
>>> the user says -enable-kvm -cpu cortex-a15 ? Does that ge
On 30 October 2015 at 21:24, Peter Crosthwaite
wrote:
> On Fri, Oct 30, 2015 at 2:14 PM, Peter Maydell
> wrote:
>> The other question is what happens on a board like this if
>> the user says -enable-kvm -cpu cortex-a15 ? Does that get us
>> a CPU without the EL3 property? (I forget...) In any ca
On Fri, Oct 30, 2015 at 2:14 PM, Peter Maydell wrote:
> On 30 October 2015 at 20:59, Peter Crosthwaite
> wrote:
>> On Fri, Oct 30, 2015 at 1:49 PM, Peter Maydell
>> wrote:
>>> I thought you were planning to have the generic code do the
>>> S->NS transition; but I guess it works better in the bo
On 30 October 2015 at 20:59, Peter Crosthwaite
wrote:
> On Fri, Oct 30, 2015 at 1:49 PM, Peter Maydell
> wrote:
>> I thought you were planning to have the generic code do the
>> S->NS transition; but I guess it works better in the board
>> code (we have to go up into Monitor and back down again,
On Fri, Oct 30, 2015 at 1:49 PM, Peter Maydell wrote:
> On 30 October 2015 at 05:34, Peter Crosthwaite
> wrote:
>> Add a flag that when set, will cause the primary CPU to start in secure
>> mode, even if the overall boot in non-secure. This is useful for when
>
> "is non-secure".
>
>> there is a
On 30 October 2015 at 05:34, Peter Crosthwaite
wrote:
> Add a flag that when set, will cause the primary CPU to start in secure
> mode, even if the overall boot in non-secure. This is useful for when
"is non-secure".
> there is a board-setup blob that needs to run from secure mode, but
> device
Add a flag that when set, will cause the primary CPU to start in secure
mode, even if the overall boot in non-secure. This is useful for when
there is a board-setup blob that needs to run from secure mode, but
device and secondary CPU init should still be done as-normal for a non-
secure boot.
Sig
