From: Markus Armbruster <armbru@redhat.com>
To: Stephen Checkoway <stephen.checkoway@oberlin.edu>
Cc: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Testing sysbus devices
Date: Tue, 19 Feb 2019 07:09:33 +0100 [thread overview]
Message-ID: <87ef84z4v6.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <91720BD9-D5A6-4457-BC99-D2132550BEDA@oberlin.edu> (Stephen Checkoway's message of "Mon, 18 Feb 2019 13:31:01 -0500")
Stephen Checkoway <stephen.checkoway@oberlin.edu> writes:
> On Feb 18, 2019, at 13:08, Markus Armbruster <armbru@redhat.com> wrote:
>
>> Stephen Checkoway <stephen.checkoway@oberlin.edu> writes:
>>
>>> On Feb 18, 2019, at 08:43, Thomas Huth <thuth@redhat.com> wrote:
>>>
>>>> On 18/02/2019 07.07, Stephen Checkoway wrote:
>>>>> Hi all,
>>>>>
>>>>> I've been working on some improvements to the pflash_cfi02 block device (interleaved flash devices similar to pflash_cfi01, multi-sector erase, nonuniform sector sizes, and some bug fixes and I'm planning on implementing sector erase suspend/resume commands in the near future).
>>
>> Any chance you could do multiple region support, too?
>
> Can you point me at the data sheet for a flash chip with multiple region support? For my purposes, I only need the features I mentioned, but if it's a simple change, I'll consider it.
I'm not familiar with CFI pflash, but I can operate a search engine.
Have a look at page 27 and 56 of
https://media.digikey.com/pdf/Data%20Sheets/Intel%20PDFs/28F160C3,320C3,640C3,800C3%20(x16).pdf
and tell us whether it's helpful.
>>>> QTestState *qts;
>>>> qts = qtest_initf(" qemu-system-arm -M musicpal,accel=qtest "
>>>> "-drive if=pflash,file=%s,format=raw", filename);
>>>
>>> If I do that, will it be possible for the test to override the properties set by pflash_cfi02_register? It looks like I should be able to use -global to set properties that aren't set explicitly.
>>
>> Yes.
>>
>> Won't work for properties set by pflash_cfi02_register(), though. To
>> test the full range of values there, you'd have to make them
>> configurable somehow. We currently don't have a good way to do that.
>> Please see
>>
>> Subject: Re: Configuring pflash devices for OVMF firmware
>> Message-ID: <87mun8gd2x.fsf@dusky.pond.sub.org>
>> https://lists.nongnu.org/archive/html/qemu-devel/2019-02/msg01734.html
>
> I see. That's too bad.
I think a test would be quite welcome even if it only tests what's
testable now with reasonable effort.
next prev parent reply other threads:[~2019-02-19 6:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 6:07 [Qemu-devel] Testing sysbus devices Stephen Checkoway
2019-02-18 13:43 ` Thomas Huth
2019-02-18 16:02 ` Stephen Checkoway
2019-02-18 16:38 ` Thomas Huth
2019-02-18 18:08 ` Markus Armbruster
2019-02-18 18:31 ` Stephen Checkoway
2019-02-19 6:09 ` Markus Armbruster [this message]
2019-02-19 14:42 ` Stephen Checkoway
2019-02-19 15:28 ` Markus Armbruster
2019-02-19 16:00 ` Stephen Checkoway
2019-02-19 17:55 ` Markus Armbruster
2019-02-20 8:55 ` Laszlo Ersek
2019-02-20 10:14 ` Markus Armbruster
2019-02-21 19:57 ` Stephen Checkoway
2019-02-22 7:42 ` Markus Armbruster
2019-02-22 8:03 ` Laszlo Ersek
2019-02-22 13:31 ` Stephen Checkoway
2019-02-22 7:55 ` Laszlo Ersek
2019-02-22 13:35 ` Stephen Checkoway
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ef84z4v6.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stephen.checkoway@oberlin.edu \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.