On 28 August 2012 14:32, Paul Brook wrote:
>> No you can't. integratorcp.c doesn't create the parts of the CPU
>> which live in QEMU's 'a15mpcore_priv' device, so the resulting
>> mess is liable to just fall over. If anybody reports bugs in
>> QEMU in such a configuration I will tell them to go aw
> >> Just to pick an obvious example, you can't stick a core
> >> which supports VFPv4 (the A15 is the only one we have) into
> >> the integratorcp
> >
> > Yes you can.
>
> No you can't. integratorcp.c doesn't create the parts of the CPU
> which live in QEMU's 'a15mpcore_priv' device, so the resu
On 28 August 2012 13:58, Paul Brook wrote:
> Peter Maydell wrote:
>> Just to pick an obvious example, you can't stick a core
>> which supports VFPv4 (the A15 is the only one we have) into
>> the integratorcp
>
> Yes you can.
No you can't. integratorcp.c doesn't create the parts of the CPU
which l
> > This changes the driver behavior to choose the default machine
> > model based on the CPU being used. Defaulting the machine this
> > way makes it easier to use QEMU as an ISS by just specifying
> > the -cpu option since a default machine that is suitable for
> > emulating the full ISA can be
On 27 August 2012 21:37, Meador Inge wrote:
> This changes the driver behavior to choose the default machine
> model based on the CPU being used. Defaulting the machine this
> way makes it easier to use QEMU as an ISS by just specifying
> the -cpu option since a default machine that is suitable f
This changes the driver behavior to choose the default machine
model based on the CPU being used. Defaulting the machine this
way makes it easier to use QEMU as an ISS by just specifying
the -cpu option since a default machine that is suitable for
emulating the full ISA can be chosen.
For example
