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: Sat, 30 Aug 2008 13:47:13 +0100 [thread overview]
Message-ID: <20080830124713.GA5910@srcf.ucam.org> (raw)
In-Reply-To: <200808291729.53628.trenn@suse.de>
On Fri, Aug 29, 2008 at 05:29:52PM +0200, Thomas Renninger wrote:
> On Thursday 28 August 2008 14:22:29 Matthew Garrett wrote:
> > Little. But what advantage do we get in the same functionality being
> > implemented in an entirely custom way? Even less.
> It is all about documentation, right.
> WMI is complicating things by one needless and complicated layer.
Not really. It provides approximately no complexity for Linux drivers,
and makes it easier for vendors to provide Windows support. WMI has not
been the hard bit of the drivers I've written. I don't see any reason to
ask vendors not to use it, as long as they're willing to document their
implementation.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-08-30 12:47 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
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 [this message]
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=20080830124713.GA5910@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox