From: Igor Mammedov <imammedo@redhat.com>
To: Roman Kagan <rkagan@virtuozzo.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
"Denis V. Lunev" <den@openvz.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH for 2.5? 1/1] DSDT: add floppy-related objects
Date: Mon, 14 Dec 2015 16:59:02 +0100 [thread overview]
Message-ID: <20151214165902.48bf8ff3@igors-macbook-pro.local> (raw)
In-Reply-To: <20151214153801.GA14224@rkaganb.sw.ru>
On Mon, 14 Dec 2015 18:38:03 +0300
Roman Kagan <rkagan@virtuozzo.com> wrote:
> On Mon, Dec 14, 2015 at 04:05:03PM +0100, Igor Mammedov wrote:
> > On Mon, 14 Dec 2015 11:22:39 +0300
> > "Denis V. Lunev" <den@openvz.org> wrote:
> >
> > > From: Roman Kagan <rkagan@virtuozzo.com>
> > >
> > > On x86-based systems Linux determines the presence and the type of
> > > floppy drives via a query of a CMOS field. So does SeaBIOS when
> > > populating the return data for int 0x13 function 0x08.
> > >
> > > Windows doesn't; instead, it requests this information from BIOS
> > > via int 0x13/0x08 or through ACPI objects _FDE (Floppy Drive
> > > Enumerate) and _FDI (Floppy Drive Information). On UEFI systems
> > > only ACPI-based detection is supported.
> > >
> > > QEMU used not to provide those objects in its DSDT; as a result
> > > floppy drives were invisible to Windows on UEFI/OVMF.
> > >
> > > This patch implements those objects in ASL, making the ACPI
> > > interpreter query the CMOS field and populate the objects. The
> > > data values used for _FDI (which, per ACPI spec, is supposed to be
> > > equivalent to BIOS int 0x13/0x08) are taken from SeaBIOS.
> > We are in process of removing static DSDT (ASL template) and
> > replacing it with dynamically generated one.
> > So please do not add new ASL to it, instead of it
> > please redo patch using AML API and it would be better if you
> > do it on top of following series:
> > "[PATCH 00/74] pc: acpi: convert DSDT to AML API and drop ASL
> > templates support"
> > http://qemu.patchew.org/series/%3C1449704528-289297-1-git-send-email-imammedo@redhat.com%3E
>
> Yes we do know about this effort. However we thought of this patch
> as a bugfix rather than a new feature so we did it against the
> current tree, to make it easy both to merge in the master and to
> backport to the branches so that the distros could pick it up in
> their packages.
>
> Do I get you right that we should better direct this patch to
> qemu-stable, and cook up a new one on top of your series for master?
You can do just single patch for both trees without dependency on above
series, just put new AML into SSDT as described in comments.
>
> Roman.
prev parent reply other threads:[~2015-12-14 15:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 8:22 [Qemu-devel] [PATCH for 2.5? 1/1] DSDT: add floppy-related objects Denis V. Lunev
2015-12-14 9:21 ` Michael S. Tsirkin
2015-12-14 9:26 ` Denis V. Lunev
2015-12-14 9:28 ` Paolo Bonzini
2015-12-14 9:41 ` Denis V. Lunev
2015-12-14 9:44 ` Paolo Bonzini
2015-12-14 9:49 ` Denis V. Lunev
2015-12-14 9:52 ` Paolo Bonzini
2015-12-14 14:21 ` Michael S. Tsirkin
2015-12-14 15:05 ` Igor Mammedov
2015-12-14 15:11 ` Denis V. Lunev
2015-12-14 15:27 ` Igor Mammedov
2015-12-14 15:38 ` Roman Kagan
2015-12-14 15:59 ` Igor Mammedov [this message]
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=20151214165902.48bf8ff3@igors-macbook-pro.local \
--to=imammedo@redhat.com \
--cc=den@openvz.org \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.com \
--cc=rth@twiddle.net \
/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).