On Feb 7, 2008 3:18 PM, Carlos Corbacho <carlos@strangeworlds.co.uk> wrote: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 --
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Linus Torvalds | Re: init's children list is long and slows reaping children. |
| Kohei KaiGai | [PATCH 0/3] exporting capability name/code pairs (final#2) |
git: | |
| Gerrit Renker | [PATCH 33/37] dccp: Initialisation framework for feature negotiation |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Arjan van de Ven | Re: [GIT]: Networking |
| Mark Ryden | Re: Linux Wireless Mini-Summit -- Ottawa -- July 22, 2008 |
