FS#38574 - [linux] Please set CONFIG_THINKPAD_ACPI_UNSAFE_LEDS
Attached to Project:
Arch Linux
Opened by ValdikSS (ValdikSS) - Sunday, 19 January 2014, 14:46 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 19 January 2014, 16:02 GMT
Opened by ValdikSS (ValdikSS) - Sunday, 19 January 2014, 14:46 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 19 January 2014, 16:02 GMT
|
Details
Please set CONFIG_THINKPAD_ACPI_UNSAFE_LEDS=y to make mic
mute LED usable on Thinkpad X220.
|
This task depends upon
Closed by Dave Reisner (falconindy)
Sunday, 19 January 2014, 16:02 GMT
Reason for closing: Upstream
Additional comments about closing: Will be fixed in 3.13 if not backported to 3.12.y
Sunday, 19 January 2014, 16:02 GMT
Reason for closing: Upstream
Additional comments about closing: Will be fixed in 3.13 if not backported to 3.12.y
Unrestricted access to all LEDs requires that thinkpad-acpi be
compiled with the CONFIG_THINKPAD_ACPI_UNSAFE_LEDS option enabled.
Distributions must never enable this option. Individual users that
are aware of the consequences are welcome to enabling it.
Sorry, I haven't.
Can we apply the following patch then?
http://permalink.gmane.org/gmane.linux.drivers.platform.x86.devel/1962
http://marc.info/?l=ibm-acpi-devel&m=130652086217381&w=4
Other distros (I checked Ubuntu and Fedora) do not apply this patch in their kernel build.
Newer patches are more complex and include both ALSA and thinkpad-acpi patching.
http://comments.gmane.org/gmane.linux.drivers.platform.x86.devel/4917
Sorry for inconvenience caused.