lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200807251320.26213.trenn@suse.de>
Date:	Fri, 25 Jul 2008 13:20:24 +0200
From:	Thomas Renninger <trenn@...e.de>
To:	Len Brown <lenb@...nel.org>
Cc:	linux-acpi@...r.kernel.org, Andi Kleen <ak@...ux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [ANNOUNCE] ACPI BIOS Guideline for Linux

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ