[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC] extensions to the -m memory option
From: |
Liviu Ionescu |
Subject: |
Re: [Qemu-devel] [RFC] extensions to the -m memory option |
Date: |
Fri, 29 May 2015 23:38:37 +0300 |
> On 29 May 2015, at 23:15, Paolo Bonzini <address@hidden> wrote:
>
>> ... But then in the common case I suspect you want your flash to be
>> non-zero at startup?
nope. I just want a method to adjust the size of the internal ram & flash,
existing inside the MCU, sizes currently hard-wired in the QEMU definitions of
a given MCU.
the point is that there are thousand of different Cortex-M MCUs, and unless we
define a mechanism for QEMU to read the CMSIS xml definitions and
auto-magically provide emulated devices with exactly the vendor specifications,
there will always be some users in need of a MCU that is not present in QEMU,
but might have a close relative already implemented, the difference between the
two being in ram and/or flash size.
---
so, for such cases, where would be more appropriate to define the ram/flash
sizes? -machine is definitely not the right place, -cpu seems also not
appropriate, what else do we have left?
regards,
Liviu
- Re: [Qemu-devel] [RFC] extensions to the -m memory option, (continued)
- Re: [Qemu-devel] [RFC] extensions to the -m memory option, Peter Maydell, 2015/05/29
- Re: [Qemu-devel] [RFC] extensions to the -m memory option, Liviu Ionescu, 2015/05/29
- Re: [Qemu-devel] [RFC] extensions to the -m memory option, Peter Maydell, 2015/05/29
- Re: [Qemu-devel] [RFC] extensions to the -m memory option, Liviu Ionescu, 2015/05/29
- Re: [Qemu-devel] [RFC] extensions to the -m memory option, Peter Crosthwaite, 2015/05/30
Re: [Qemu-devel] [RFC] extensions to the -m memory option, Paolo Bonzini, 2015/05/29
Re: [Qemu-devel] [RFC] extensions to the -m memory option, Peter Crosthwaite, 2015/05/30