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: <200808281141.30178.trenn@suse.de>
Date:	Thu, 28 Aug 2008 11:41:28 +0200
From:	Thomas Renninger <trenn@...e.de>
To:	Carlos Corbacho <carlos@...angeworlds.co.uk>
Cc:	linux-acpi@...r.kernel.org, Len Brown <lenb@...nel.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 Wednesday 27 August 2008 22:29:15 Carlos Corbacho wrote:
> On Thursday 24 July 2008 16:32:22 Thomas Renninger wrote:
> > \section{WMI - Windows Management Instrumentation}
> >
> > WMI is a Microsoft specific service. A small part of it
> > describes possible ACPI WMI implementations provided by the BIOS.
> > This is not part of the official ACPI specification and BIOS developers
> > should avoid using it. The Linux kernel driver supports basic WMI ACPI
> > functionality (since 2.6.25), but it is marked experimental.
> > ACPI functionality should not depend on the WMI interface.
>
> Perhaps it would be more useful to suggest to vendors/ BIOS writers what
> they should use here instead?

They can use their own devices.
There is a section about if you provide your own device, document it, etc.:

2 Vendor specific ACPI implementations
...
2. If new devices or functions are introduced, document how to use them. A
   short specification or a request for comments (RFC) can form the basis of
   a new standard which follows your needs.


But yes, it could be pointed out clearer.
I'll look closer at it when I touch it the next time.
Text snippets/suggestions are also appreciated.

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