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]
Message-ID: <929318d30706121315n3d2d20efp6fd3ff590cce894c@mail.gmail.com>
Date:	Tue, 12 Jun 2007 22:15:37 +0200
From:	"Giel de Nijs" <giel@...feinetrip.com>
To:	"Dmitry Torokhov" <dtor@...ightbb.com>
Cc:	linux-kernel@...r.kernel.org, linux-input@...ey.karlin.mff.cuni.cz,
	"Vojtech Pavlik" <vojtech@...e.cz>,
	"Matthew Garrett" <mjg59@...f.ucam.org>,
	"Matt Domsch" <matt_domsch@...l.com>,
	"Rezwanul Kabir" <rezwanul_kabir@...l.com>
Subject: Re: [PATCH] input: fix broken behaviour of Dell Latitude special keys

Hi Dmitry,

On 6/12/07, Dmitry Torokhov <dtor@...ightbb.com> wrote:

> Thank you for the patch. Is there any way I could see data coming from i8042
> when you press on these special keys? If you could do:
>
> echo 1 > /sys/module/i8042/parameters/debug
> tehn presses and released all these keys
> echo 0 > /sys/module/i8042/parameters/debug
>
> and send me dmesg I woudl appreciate that.

Here's the data from i8042 of, in order, Fn-F1, Fn-F3, Fn-F7, Fn-F8, Fn-Up,
Fn-Down, and Fn-Left:

drivers/input/serio/i8042.c: e0 <- i8042 (interrupt, 0, 1) [2277118]
drivers/input/serio/i8042.c: 0a <- i8042 (interrupt, 0, 1) [2277118]
drivers/input/serio/i8042.c: e0 <- i8042 (interrupt, 0, 1) [2277643]
drivers/input/serio/i8042.c: 07 <- i8042 (interrupt, 0, 1) [2277643]
drivers/input/serio/i8042.c: e0 <- i8042 (interrupt, 0, 1) [2277987]
drivers/input/serio/i8042.c: 0f <- i8042 (interrupt, 0, 1) [2277988]
drivers/input/serio/i8042.c: e0 <- i8042 (interrupt, 0, 1) [2278175]
drivers/input/serio/i8042.c: 0b <- i8042 (interrupt, 0, 1) [2278175]
drivers/input/serio/i8042.c: e0 <- i8042 (interrupt, 0, 1) [2279806]
drivers/input/serio/i8042.c: 06 <- i8042 (interrupt, 0, 1) [2279806]
drivers/input/serio/i8042.c: e0 <- i8042 (interrupt, 0, 1) [2279940]
drivers/input/serio/i8042.c: 05 <- i8042 (interrupt, 0, 1) [2279940]
drivers/input/serio/i8042.c: e0 <- i8042 (interrupt, 0, 1) [2280101]
drivers/input/serio/i8042.c: 13 <- i8042 (interrupt, 0, 1) [2280102]

As you can see, no release events :).

There's also Fn-End, Fn-PgUp, Fn-PgDown (all audio related) and the wireless
switch at the side, those do generate release events. Also, the Fn
combinations for num lock, scroll lock, sysrq and pause/break seem to act
normal. There's also Fn-Esc, but that's an ACPI key.

Hope this helps.

Greetings,
Giel
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ