From: Gerd Hoffmann <kraxel@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] fdc: fix drive property handling.
Date: Wed, 16 Dec 2009 14:29:43 +0100 [thread overview]
Message-ID: <4B28E0C7.3010605@redhat.com> (raw)
In-Reply-To: <m3pr6f9qww.fsf@crossbow.pond.sub.org>
On 12/16/09 11:03, Markus Armbruster wrote:
> This fixes "-global isa-fdc,driveB=DRIVE-ID" for me, but problems
> remain:
>
> * -drive if=none,id=fd,file=fd.img -global isa-fdc.driveA=fd
>
> dev: isa-fdc, id ""
> dev-prop: driveA = floppy0
> dev-prop: driveB =<null>
> isa irq 6
Patch is on the list.
> * -drive if=none,id=fd,file=fd.img -global isa-fdc.driveA=fd,driveB=fd
Oh, -global works like -set, i.e. you can't set multiple properties in
one go. Should be '-global isa-fdc.driveA=fd -global isa-fdc.driveB=fd'.
The error reporting is *ahem*, well, not perfect. Patch is on the list.
cheers,
Gerd
next prev parent reply other threads:[~2009-12-16 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 15:09 [Qemu-devel] [PATCH] fdc: fix drive property handling Gerd Hoffmann
2009-12-16 10:03 ` Markus Armbruster
2009-12-16 13:29 ` Gerd Hoffmann [this message]
2009-12-16 14:45 ` Markus Armbruster
-- strict thread matches above, loose matches on Subject: below --
2010-03-10 16:30 Gerd Hoffmann
2010-03-13 11:16 ` Aurelien Jarno
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=4B28E0C7.3010605@redhat.com \
--to=kraxel@redhat.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).