From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Thomas Renninger <trenn@suse.de>
Cc: Carlos Corbacho <carlos@strangeworlds.co.uk>,
linux-acpi@vger.kernel.org, Len Brown <lenb@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: Thu, 28 Aug 2008 11:56:16 +0100 [thread overview]
Message-ID: <20080828105616.GA24515@srcf.ucam.org> (raw)
In-Reply-To: <200808281141.30178.trenn@suse.de>
On Thu, Aug 28, 2008 at 11:41:28AM +0200, Thomas Renninger wrote:
> On Wednesday 27 August 2008 22:29:15 Carlos Corbacho wrote:
> > 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.
A documented WMI interface is easier to use than an entirely custom
documented interface, and reduces the amount of work the vendor has to
do in Windows. To be honest, I think it's the sort of thing we should be
encouraging.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-08-28 10:56 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
2008-08-27 20:29 ` Carlos Corbacho
2008-08-28 9:41 ` Thomas Renninger
2008-08-28 10:56 ` Matthew Garrett [this message]
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=20080828105616.GA24515@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=ak@linux.intel.com \
--cc=carlos@strangeworlds.co.uk \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trenn@suse.de \
/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.