[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200808311518.25421.trenn@suse.de>
Date: Sun, 31 Aug 2008 15:18:24 +0200
From: Thomas Renninger <trenn@...e.de>
To: Matthew Garrett <mjg59@...f.ucam.org>
Cc: Carlos Corbacho <carlos@...angeworlds.co.uk>,
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 Saturday 30 August 2008 02:47:13 pm Matthew Garrett wrote:
> 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,
Autoloading does not work yet?
It is working fine with ordinary ACPI devices providing a HID.
> as long as they're willing to document their
> implementation.
I'll point that out, something like:
If you really have to use WMI for Windows compatibility reason, make
sure the important parts (is there already something to mention?
Against what is the driver loaded -> autoloading?) are documented well.
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