Re: ACPI_WMI: worst config description of all times

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Feb 7, 2008 3:18 PM, Carlos Corbacho <carlos@xxxxxxxxxxxxxxxxxxx> 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
_______________________________________________
linux-pm mailing list
linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/linux-pm

[Index of Archives]     [Linux ACPI]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [CPU Freq]     [Kernel Newbies]     [Fedora Kernel]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux