> On Mon, 25 Mar 2019 at 13:29, Alex Bennée <email address hidden> wrote:
>> I was going to suggest -cpu cortex-a53,aarch64=off but that seems to be
>> only for KVM guests.
>>
>> Is there actually a v8 A profile 32 bit only CPU part?
>
> You can for instance connect up a Cortex-A53 with the
> AA64nAA32 config signals hardwired to 0 ("go into AArch32
> on power-on-reset"), which is functionally the same thing.
Peter Maydell <email address hidden> writes:
> On Mon, 25 Mar 2019 at 13:29, Alex Bennée <email address hidden> wrote: a53,aarch64= off but that seems to be
>> I was going to suggest -cpu cortex-
>> only for KVM guests.
>>
>> Is there actually a v8 A profile 32 bit only CPU part?
>
> You can for instance connect up a Cortex-A53 with the
> AA64nAA32 config signals hardwired to 0 ("go into AArch32
> on power-on-reset"), which is functionally the same thing.
So would it be reasonable to have a
#ifndef TARGET_AARCH64
{ .name = "cortex-a53 (32bit)", .initfn = aarch32_a53_initfn },
#endif
and the appropriate init function in cpu.c? That should be all we need right?
>
> thanks
> -- PMM
--
Alex Bennée