All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Denis V. Lunev" <den@openvz.org>
To: Igor Mammedov <imammedo@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	qemu-devel@nongnu.org, Roman Kagan <rkagan@virtuozzo.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	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 18:11:53 +0300	[thread overview]
Message-ID: <566EDC39.9020507@openvz.org> (raw)
In-Reply-To: <20151214160503.0c684638@igors-macbook-pro.local>

On 12/14/2015 06:05 PM, 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
>
> to avoid touching ASL code and avoid conflicts with API changes
> Patch also could be simpler if you generate _FDE,_FDI
> dynamically instead of trying to detect drive presence
> from guest side.
> See below for comments.
Igor,

do you have any GIT tree we could be based on :) ?

Den

  reply	other threads:[~2015-12-14 15:12 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 [this message]
2015-12-14 15:27     ` Igor Mammedov
2015-12-14 15:38   ` Roman Kagan
2015-12-14 15:59     ` Igor Mammedov

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=566EDC39.9020507@openvz.org \
    --to=den@openvz.org \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@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 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.