From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Renninger Subject: Re: [ANNOUNCE] ACPI BIOS Guideline for Linux Date: Fri, 25 Jul 2008 13:20:24 +0200 Message-ID: <200807251320.26213.trenn@suse.de> References: <200807241732.23412.trenn@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from cantor2.suse.de ([195.135.220.15]:54673 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751820AbYGYLU2 (ORCPT ); Fri, 25 Jul 2008 07:20:28 -0400 In-Reply-To: Content-Disposition: inline Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Len Brown Cc: linux-acpi@vger.kernel.org, Andi Kleen , Linux Kernel Mailing List 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