From: Thomas Renninger <trenn@suse.de>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] ACPI BIOS Guideline for Linux
Date: Fri, 25 Jul 2008 13:20:24 +0200 [thread overview]
Message-ID: <200807251320.26213.trenn@suse.de> (raw)
In-Reply-To: <alpine.LFD.1.10.0807241937500.6098@localhost.localdomain>
On Friday 25 July 2008 01:47:04 Len Brown wrote:
> It is not an ACPI specification violation that Linux
> (and ACPICA) claim compatibility with the interfaces
> advertised by one or multiple versions of Windows.
>
> Yes, there are be cases where BIOS vendors will want
> to know if the running version of Linux supports,
> or does not support, an interface/feature.
> We (the Linux community that maintain Linux/ACPI) are
> eager to support them in this. However, the interface
> needs to be sufficiently defined so that we know when
> to _not_ advertise that feature.
>
> eg. There are proposals for
>
> _OSI("Linux-Needs ATI S3 video re-POST")
> _OSI("Linux-Needs NVIDIA S3 video re-POST")
> _OSI("Linux-Native IPMI Support")
Great!
Please add me to CC as soon as you agreed to something and
I'll pick those up.
Thanks,
Thomas
next prev parent reply other threads:[~2008-07-25 11:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 15:32 [ANNOUNCE] ACPI BIOS Guideline for Linux Thomas Renninger
2008-07-24 23:47 ` Len Brown
2008-07-25 11:20 ` Thomas Renninger [this message]
2008-08-27 20:29 ` Carlos Corbacho
2008-08-28 9:41 ` Thomas Renninger
2008-08-28 10:56 ` Matthew Garrett
2008-08-28 12:16 ` Thomas Renninger
2008-08-28 12:22 ` Matthew Garrett
2008-08-29 15:29 ` Thomas Renninger
2008-08-30 12:47 ` Matthew Garrett
2008-08-31 13:18 ` Thomas Renninger
2008-08-31 17:25 ` Matthew Garrett
2008-09-03 15:09 ` Thomas Renninger
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=200807251320.26213.trenn@suse.de \
--to=trenn@suse.de \
--cc=ak@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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