From: Thomas Huth <thuth@redhat.com>
To: Stephen Checkoway <stephen.checkoway@oberlin.edu>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Testing sysbus devices
Date: Mon, 18 Feb 2019 17:38:50 +0100 [thread overview]
Message-ID: <7f53b5d1-f0a7-6d51-a647-a1b98cd50a75@redhat.com> (raw)
In-Reply-To: <BD5AEBD4-0B91-4756-B8D6-C0E643CF1F42@oberlin.edu>
On 18/02/2019 17.02, Stephen Checkoway wrote:
>
>
> On Feb 18, 2019, at 08:43, Thomas Huth <thuth@redhat.com> wrote:
>
>> I think you could use one of the machines that has a cfi02 on board. For
>> example: Write some random data to a temporary file. Run qemu with:
>>
>> 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, I'm also not an expert in that area, but I think -global should do
the job here.
Thomas
next prev parent reply other threads:[~2019-02-18 16:39 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 [this message]
2019-02-18 18:08 ` Markus Armbruster
2019-02-18 18:31 ` Stephen Checkoway
2019-02-19 6:09 ` Markus Armbruster
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=7f53b5d1-f0a7-6d51-a647-a1b98cd50a75@redhat.com \
--to=thuth@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stephen.checkoway@oberlin.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).