[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2c0942db0802071533l5c3b98fel90946b73f8a9586b@mail.gmail.com>
Date: Thu, 7 Feb 2008 15:33:54 -0800
From: "Ray Lee" <ray-lk@...rabbit.org>
To: "Carlos Corbacho" <carlos@...angeworlds.co.uk>
Cc: "Pavel Machek" <pavel@....cz>, "Len Brown" <lenb@...nel.org>,
"kernel list" <linux-kernel@...r.kernel.org>,
"Linux-pm mailing list" <linux-pm@...ts.osdl.org>,
linux-acpi@...r.kernel.org
Subject: Re: ACPI_WMI: worst config description of all times
On Feb 7, 2008 3:18 PM, Carlos Corbacho <carlos@...angeworlds.co.uk> wrote:
> As for the Kconfig - I'm open to suggestions.
While the kconfig text is supposed to say 'what' something is, the
more valuable piece of information it provides is *why* one would want
to enable it.
Do you have list of hardware/platforms that require this feature to
get the hardware to work? (acer abc123, tcm1100 xyz) If so, providing
that information to the user/distributions is the right first step.
Tell them why they want this feature.
Better, if there are kernel drivers that require this (and currently
only those drivers), then have those kernel drivers enable ACPI WMI,
and otherwise leave it off. If/when the userspace accessible bits go
in, it can be exposed to the configurator then.
Ray
--
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