[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] hw/nand hw/onenand and read-only
From: |
Kevin Wolf |
Subject: |
Re: [Qemu-devel] hw/nand hw/onenand and read-only |
Date: |
Wed, 19 Oct 2011 11:29:44 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20110927 Thunderbird/7.0 |
Am 19.10.2011 10:46, schrieb Peter Maydell:
> On 19 October 2011 09:03, Markus Armbruster <address@hidden> wrote:
>> <address@hidden> writes:
>>> both device models already support running without a drive as well by
>>> using a memory buffer instead so it would also be possible to make them
>>> use a read-only drive in a way that initial NAND/OneNAND contents would be
>>> read from the drive but any changes would not be written back to the drive
>>> and would be lost when QEMU is killed.
>>
>> Sounds like it could be useful, but it's not what I'd expect for
>> "readonly".
>>
>> You could create a boolean device property to make memory contents
>> transient rather than persistent. Then reject read-only drives only in
>> persistent mode, i.e. when the property is false. Feels cleaner to me.
>
> That doesn't sound very onenand/nand specific to me, though.
And in fact, you already get this with -drive snapshot=on (but still
leaving the drive r/w)
Kevin
- [Qemu-devel] hw/nand hw/onenand and read-only, Markus Armbruster, 2011/10/18
- Re: [Qemu-devel] hw/nand hw/onenand and read-only, Juha.Riihimaki, 2011/10/18
- Re: [Qemu-devel] hw/nand hw/onenand and read-only, Markus Armbruster, 2011/10/18
- Re: [Qemu-devel] hw/nand hw/onenand and read-only, Juha.Riihimaki, 2011/10/19
- Re: [Qemu-devel] hw/nand hw/onenand and read-only, Markus Armbruster, 2011/10/19
- Re: [Qemu-devel] hw/nand hw/onenand and read-only, Peter Maydell, 2011/10/19
- Re: [Qemu-devel] hw/nand hw/onenand and read-only,
Kevin Wolf <=
- Re: [Qemu-devel] hw/nand hw/onenand and read-only, Markus Armbruster, 2011/10/19