From: Laszlo Ersek <lersek@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Jan Tomko <jtomko@redhat.com>, John Snow <jsnow@redhat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 2/3] hw/i386/pc: reflect any FDC @ ioport 0x3f0 in the CMOS
Date: Fri, 26 Jun 2015 14:25:42 +0200 [thread overview]
Message-ID: <558D44C6.4070807@redhat.com> (raw)
In-Reply-To: <87ioaa24uc.fsf@blackfin.pond.sub.org>
On 06/26/15 11:31, Markus Armbruster wrote:
> Laszlo Ersek <lersek@redhat.com> writes:
>
>> With the pc-q35-2.4 machine type, if the user creates an ISA FDC manually:
>>
>> -device isa-fdc,driveA=drive-fdc0-0-0 \
>> -drive file=...,if=none,id=drive-fdc0-0-0,format=raw
>>
>> then the board-default FDC will be skipped, and only the explicitly
>> requested FDC will exist. qtree-wise, this is correct; however such an FDC
>> is currently not registered in the CMOS, because that code is only reached
>> for the board-default FDC.
>>
>> The pc_cmos_init_late() one-shot reset handler -- one-shot because the
>> CMOS is not reprogrammed during warm reset -- should search for any ISA
>> FDC devices, created implicitly (by board code) or explicitly, and set the
>> CMOS accordingly to the ISA FDC(s) with iobase=0x3f0:
>>
>> - if there is no such FDC, report both drives absent,
>> - if there is exactly one such FDC, report its drives in the CMOS,
>> - if there are more than one such FDCs, then pick one (it is not specified
>> which one), and print a warning about the ambiguity.
>>
>> Cc: Jan Tomko <jtomko@redhat.com>
>> Cc: John Snow <jsnow@redhat.com>
>> Cc: Markus Armbruster <armbru@redhat.com>
>> Cc: Paolo Bonzini <pbonzini@redhat.com>
>> Reported-by: Jan Tomko <jtomko@redhat.com>
>> Suggested-by: Markus Armbruster <armbru@redhat.com>
>> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
>> Reviewed-by: John Snow <jsnow@redhat.com>
>
> Reviewed-by: Markus Armbruster <armbru@redhat.com>
Thank you. Can you or John please send a PULL req for this? (Or include
it in an upcoming PULL of yours.)
I've been Cc'ing Paolo because the get-maintainer script reported him at
the top for the patch set, but I believe he might not have time for this
now.
Thanks!
Laszlo
next prev parent reply other threads:[~2015-06-26 12:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 13:35 [Qemu-devel] [PATCH v2 0/3] update CMOS for ISA-FDC with iobase=0x3f0 Laszlo Ersek
2015-06-25 13:35 ` [Qemu-devel] [PATCH v2 1/3] hw/i386/pc: factor out pc_cmos_init_floppy() Laszlo Ersek
2015-06-25 13:35 ` [Qemu-devel] [PATCH v2 2/3] hw/i386/pc: reflect any FDC @ ioport 0x3f0 in the CMOS Laszlo Ersek
2015-06-26 9:31 ` Markus Armbruster
2015-06-26 12:25 ` Laszlo Ersek [this message]
2015-06-26 18:50 ` John Snow
2015-06-26 19:09 ` Eduardo Habkost
2015-06-29 9:33 ` Markus Armbruster
2015-06-29 9:56 ` Michael S. Tsirkin
2015-07-06 21:58 ` Laszlo Ersek
2015-06-29 9:55 ` Michael S. Tsirkin
2015-06-25 13:35 ` [Qemu-devel] [PATCH v2 3/3] hw/i386/pc: don't carry FDC from pc_basic_device_init() to pc_cmos_init() Laszlo Ersek
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=558D44C6.4070807@redhat.com \
--to=lersek@redhat.com \
--cc=armbru@redhat.com \
--cc=jsnow@redhat.com \
--cc=jtomko@redhat.com \
--cc=pbonzini@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).