mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Marcel Korpel <marcel.lists@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Changes to include/linux/input.h are no longer taken into account
Date: Wed, 31 Aug 2011 14:08:26 -0700	[thread overview]
Message-ID: <20110831210825.GA32646@core.coreip.homeip.net> (raw)
In-Reply-To: <CAJuji_EeLBCB4qpbCQLGFgqAqsWJ97qKYPK8b7hDa91Xr50Tmg@mail.gmail.com>

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

      reply	other threads:[~2011-08-31 21:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-27 20:44 Marcel Korpel
2011-08-31 21:08 ` Dmitry Torokhov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110831210825.GA32646@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel.lists@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®