linux-kernel - Re: Changes to include/linux/input.h are no longer taken into account

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: <20110831210825.GA32646@core.coreip.homeip.net>
Date:	Wed, 31 Aug 2011 14:08:26 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Marcel Korpel <marcel.lists@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Changes to include/linux/input.h are no longer taken into account

Hi Marcel,

On Sat, Aug 27, 2011 at 10:44:30PM +0200, Marcel Korpel wrote:
> Hi,
> 
> Up until recently, in order to be able to use the zoom slider on my MS
> Natural Ergonomic Keyboard 4000 I used a patched version of
> include/linux/input.h, in which a few definitions were changed so
> several special keys produced keycodes <= 255, like
> 
> #define KEY_ZOOMIN		0x0f6	/* AC Zoom In == 246 */
> #define KEY_ZOOMOUT		0x0f7	/* AC Zoom Out == 247  */
> 
> Now X is able to process these keycodes.
> 
> Earlier this month, I upgraded the kernel and made sure that input.h
> still contained these changed values. However, when I use showkey I
> get the following output
> 
> keycode 418 press
> keycode 418 release
> keycode 419 press
> keycode 419 release
> 
> instead of the lower values I provided. I flipped through the latest
> kernel changes, but was not able to find a change that might have
> influenced the keycodes, only one change about the inclusion order
> inside linux/input.h [1]. I am currently using commit
> d31bf2883542cd3414674238f94123bd1d9c0b9f.
> 
> I know that the actual problem resides in the way how X handles
> keycodes [2] and it can (also) be circumvented using a patched
> xf86-input-evdev [3], but I still think this case is a bug.
> 

Make sure udev does not load a custom map for this device for you.

Thanks.

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