linux-kernel - Re: Lenovo ThinkPads need acpi

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 14 Jan 2008 11:06:33 -0200
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	Pavel Machek <pavel@....cz>, Len Brown <lenb@...nel.org>,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Lenovo ThinkPads need acpi_osi="Linux"

On Mon, 14 Jan 2008, Matthew Garrett wrote:
> Userspace is in a better position to make this determination. Of course, 

That's fine with me.

> this also means not passing the Linux OSI to the firmware. Our hardware 
> interaction is sufficiently in flux that any attempt to work around it 
> in the firmware is just going to lead to bizarre breakage down the road.

The Linux OSI string does more. I just found out that it also drives the
MUTE key behaviour (and you want the behaviour *with* the Linux OSI string
loaded).

Some of the behaviours are actually linux-version agnostic.  E.g. we'll
always prefer that the Mute key send a KEY_MUTE event over the keyboard
controller *without* touching the hardware (which is what it does if the
Linux OSI string is *present*) in ThinkPads where there is no
firmware-specific mixer hardware (i.e. the T61 and probably X61).  For such
uses, the OSI string is fine.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
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/