public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mikael Magnusson <mikaelmagnusson@tjohoo.se>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1/2: keyboard funnies in textmode
Date: Sun, 10 Aug 2003 20:40:23 +0200	[thread overview]
Message-ID: <20030810184023.GA10709@skinner.hem.za.org> (raw)
In-Reply-To: <20030801221627.GA3397@win.tue.nl>

On Sat, Aug 02, 2003 at 12:16:27AM +0200, Andries Brouwer wrote:
> On Fri, Aug 01, 2003 at 07:56:04PM +0200, Jurgen Kramer wrote:
> 
> > PC 2.4 showkey:
> > keycode  43 release
> > keycode  43 press
> > 
> > PC 2.6 showkey:
> > keycode  84 press
> > keycode  84 release
> 

I have got the same problem in 2.6.0-test3 with a swedish USB keyboard. 
It's a Microsoft Natural Keyboard pro. The "'/*" key generates keycode 
43 in 2.4.21 and keycode 84 in 2.6.0-test3. But my swedish AT keyboard 
still generates the same keycode (43) in both releases.

I have tried to find what caused the change. In 2.4 keycode 84 is 
translated to 43 by x86_keycodes table in drivers/input/keybdev.c. But 
in 2.6 I think the table is used only in raw mode, otherwise the keymap 
is used directly (in drivers/char/keyboard.c). 

My workaround is to define keycode 84 in the keymap file/s. I have added 
the following to my US keymap:

keycode  84 = backslash        bar
        control keycode  84 = Control_backslash

Regards,
Mikael Magnusson

      reply	other threads:[~2003-08-10 18:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01 14:25 2.6.0-test1/2: keyboard funnies in textmode Jurgen Kramer
2003-08-01 14:52 ` Andries Brouwer
2003-08-01 15:33   ` Jurgen Kramer
2003-08-01 16:37     ` Andries Brouwer
2003-08-01 17:56       ` Jurgen Kramer
2003-08-01 20:16         ` Andries Brouwer
2003-08-01 22:16         ` Andries Brouwer
2003-08-10 18:40           ` Mikael Magnusson [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=20030810184023.GA10709@skinner.hem.za.org \
    --to=mikaelmagnusson@tjohoo.se \
    --cc=linux-kernel@vger.kernel.org \
    /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