From: Andries Brouwer <aebr@win.tue.nl>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: "Frédéric L. W. Meunier" <1@pervalidus.net>,
linux-kernel@vger.kernel.org
Subject: Re: BUG: The key "/ ?" on my abtn2 keyboard is dead with kernel 2.6.1
Date: Mon, 12 Jan 2004 13:56:55 +0100 [thread overview]
Message-ID: <20040112135655.A980@pclin040.win.tue.nl> (raw)
In-Reply-To: <20040112083647.GB2372@ucw.cz>; from vojtech@suse.cz on Mon, Jan 12, 2004 at 09:36:47AM +0100
On Mon, Jan 12, 2004 at 09:36:47AM +0100, Vojtech Pavlik wrote:
> On Mon, Jan 12, 2004 at 12:17:03AM -0200, Frédéric L. W. Meunier wrote:
> > I tested with the patch and it didn't fix it on the console.
>
> Yes, the patch didn't fix it for the console.
> > showkey under 2.4:
> >
> > keycode 89
>
> This, however, is VERY interesting, I didn't expect this keycode under
> 2.4 at all. Can you check with 'evtest' what it does send there?
See http://www.win.tue.nl/~aeb/linux/kbd/scancodes-5.html#ss5.17
---------------------------------------------------------------------
ABNT (Associao Brasileira de Normas Tecnicas) and ABNT2 are Brazilian
keyboard layout standards. The plain Brazilian keyboard has 103 keys.
The Brazilian ABNT keyboard has two unusual keys, with scancodes 73 (/?)
and 7e (Keypad-.). The former is located to the left of the RShift
(which key therefore is less wide than usually), the latter below the
Keypad-Plus (reducing the Keypad-Plus to single height).
Under Linux, the corresponding key codes are 89 and 121, respectively.
---------------------------------------------------------------------
In the 2.4 source, see the array high_keys[]. It will map 73, 7d
(seen on Japanese keyboards), 7e to keycodes 89, 124, 121.
The 2.6.1 kernel will first untranslate to 51, 6a, 6d and then map
to 181, 182, 124, changing the keycode for all three.
Andries
next prev parent reply other threads:[~2004-01-12 13:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-11 15:45 Murilo Pontes
2004-01-11 20:35 ` Frédéric L. W. Meunier
2004-01-11 23:47 ` Vojtech Pavlik
2004-01-11 23:50 ` Vojtech Pavlik
2004-01-12 2:17 ` Frédéric L. W. Meunier
2004-01-12 8:36 ` Vojtech Pavlik
2004-01-12 12:56 ` Andries Brouwer [this message]
2004-01-14 14:24 ` Vojtech Pavlik
2004-01-14 14:44 ` John Bradford
2004-01-14 14:40 ` Vojtech Pavlik
2004-01-14 18:22 ` Vojtech Pavlik
2004-01-14 19:29 ` Mariusz Zielinski
2004-01-14 19:41 ` Vojtech Pavlik
2004-01-14 20:01 ` Andrew Morton
2004-01-14 21:42 ` Vojtech Pavlik
2004-01-14 22:06 ` Andrew Morton
2004-01-14 22:13 ` Vojtech Pavlik
2004-01-19 10:59 ` Go Taniguchi
2004-01-12 11:30 ` Murilo Pontes
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=20040112135655.A980@pclin040.win.tue.nl \
--to=aebr@win.tue.nl \
--cc=1@pervalidus.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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®