linux-kernel - Re: Regression in thinkpad-acpi events

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111125002543.GC28516@khazad-dum.debian.net>
Date:	Thu, 24 Nov 2011 22:25:43 -0200
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Tom Gundersen <teg@...m.no>
Cc:	maciej.rutecki@...il.com, Natanji <natanji@...il.com>,
	linux-acpi@...r.kernel.org, lenb@...nel.org,
	ibm-acpi-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: Regression in thinkpad-acpi events

On Thu, 24 Nov 2011, Tom Gundersen wrote:
> It looks like my problem was something else. We don't do anything to
> synthesize the ACPI HKEY events (AFAIK), so I believe that KDE (which
> I am using) should be using the input events and that the HKEY stuff
> does not matter.

I have no idea if KDE can do it or not.

> As to the original report about the change in HKEY events, this is
> (probably) due to PROCFS_ACPI being disabled in the Arch kernel as of
> 3.1.

Well, maybe Arch needs to update its userspace to cope with its kernel...
but still, we will only really know whether this is the problem or not if
someone checks the input devices and the acpi events over netlink in that
Arch kernel.

-- 
  "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/