From: Vojtech Pavlik <vojtech@suse.cz>
To: Skip Ford <skip.ford@verizon.net>
Cc: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: KDSETKEYCODE work with new input layer?
Date: Tue, 1 Oct 2002 15:17:22 +0200 [thread overview]
Message-ID: <20021001151722.A11750@ucw.cz> (raw)
In-Reply-To: <200210011231.g91CVCdG000289@pool-141-150-241-241.delv.east.verizon.net>; from skip.ford@verizon.net on Tue, Oct 01, 2002 at 08:31:05AM -0400
On Tue, Oct 01, 2002 at 08:31:05AM -0400, Skip Ford wrote:
> Vojtech Pavlik wrote:
> > On Mon, Sep 30, 2002 at 10:40:10AM -0400, Skip Ford wrote:
> >
> > > I can no longer change keycodes since switching to the new input layer.
> > > Has anyone been able to?
> >
> > I've tested it and it should work. What exactly doesn't work for you?
> > What are you trying to do?
>
> I'm trying to assign keycodes using the kbd package. Multimedia keys
> and some regular keys. Here is one example. The key I'm pressing is
> e05e.
Ok, the problem is that because the ioctls are no longer i386-centric,
the layout of the tables has changed.
What used to be scancode e05e is now scancode 15e, basically all
scancodes beginning with e0 are now offset by just 100 hex.
getkeycodes/setkeycodes translates e05e to de, while the table needs 15e.
> ~# showkey
> kb mode was XLATE
>
> press any key (program terminates 10s after last keypress)...
> keycode 116 press
> keycode 116 release
>
> ~# getkeycodes
> Plain scancodes xx (hex) versus keycodes (dec)
> 0 is an error; for 1-88 (0x01-0x58) scancode equals keycode
>
> 0x58: 88 54 28 27 0 43 0 0
> 0x60: 85 86 90 91 92 93 14 94
> 0x68: 95 79 0 75 71 121 0 123
> 0x70: 82 83 80 76 77 72 1 69
> 0x78: 87 78 81 74 55 73 70 99
>
> Escaped scancodes e0 xx (hex)
>
> e0 00: 252 0 0 65 99 0 0 0
> e0 08: 0 0 0 0 0 0 0 0
> e0 10: 0 0 0 0 0 0 0 0
> e0 18: 0 0 0 0 0 0 0 0
> e0 20: 0 0 0 0 0 0 0 0
> e0 28: 0 0 251 0 0 0 0 0
> e0 30: 0 0 0 0 0 0 0 0
> e0 38: 0 0 0 0 0 0 0 0
> e0 40: 0 0 0 0 0 0 0 0
> e0 48: 0 0 0 0 0 0 0 0
> e0 50: 0 0 0 0 0 0 0 0
> e0 58: 0 0 0 0 0 0 0 0
> ^^^ <-- e05e
> e0 60: 252 253 0 0 0 0 0 0
> e0 68: 0 0 0 0 0 0 0 0
> e0 70: 254 0 0 0 0 0 0 0
> e0 78: 0 0 0 0 0 0 0 255
Ignore getkeycodes output, except for the 0x58-0x7f the output is not
correct anymore. (e000-e07f lines show entries for scancodes 0x80-0xff,
as they always did, though).
> ~# setkeycodes e05e 89
Use setkeycodes 15e 89
> ~# getkeycodes
> Plain scancodes xx (hex) versus keycodes (dec)
> 0 is an error; for 1-88 (0x01-0x58) scancode equals keycode
>
> 0x58: 88 54 28 27 0 43 0 0
> 0x60: 85 86 90 91 92 93 14 94
> 0x68: 95 79 0 75 71 121 0 123
> 0x70: 82 83 80 76 77 72 1 69
> 0x78: 87 78 81 74 55 73 70 99
>
> Escaped scancodes e0 xx (hex)
>
> e0 00: 252 0 0 65 99 0 0 0
> e0 08: 0 0 0 0 0 0 0 0
> e0 10: 0 0 0 0 0 0 0 0
> e0 18: 0 0 0 0 0 0 0 0
> e0 20: 0 0 0 0 0 0 0 0
> e0 28: 0 0 251 0 0 0 0 0
> e0 30: 0 0 0 0 0 0 0 0
> e0 38: 0 0 0 0 0 0 0 0
> e0 40: 0 0 0 0 0 0 0 0
> e0 48: 0 0 0 0 0 0 0 0
> e0 50: 0 0 0 0 0 0 0 0
> e0 58: 0 0 0 0 0 0 89 0
> ^^^^ <-- e05e
> e0 60: 252 253 0 0 0 0 0 0
> e0 68: 0 0 0 0 0 0 0 0
> e0 70: 254 0 0 0 0 0 0 0
> e0 78: 0 0 0 0 0 0 0 255
>
> ~# showkey
> kb mode was XLATE
>
> press any key (program terminates 10s after last keypress)...
> keycode 116 press
> keycode 116 release
>
> ----------------------------------------------------------
> The same thing happens with every key.
No, keycodes without e0 should be fine.
> I've tried every config option
> that seems even remotely related to keyboards and nothing changes. It's
> detected as:
>
> input: AT Set 2 keyboard on isa0060/serio0
> serio: i8042 KBD port at 0x60,0x64 irq 1
>
> It's a PS2 keyboard attached via PS2/AT adapter. The actual changes I'm
> trying to make are the same ones I've been using through all of 2.4 and
> 2.5
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-10-01 13:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 14:40 KDSETKEYCODE work with new input layer? Skip Ford
2002-10-01 9:54 ` Vojtech Pavlik
2002-10-01 12:31 ` Skip Ford
2002-10-01 13:17 ` Vojtech Pavlik [this message]
2002-10-01 15:32 ` Skip Ford
2002-10-01 15:41 ` Vojtech Pavlik
2002-10-01 15:54 ` Andries Brouwer
2002-10-01 15:55 ` Vojtech Pavlik
2002-10-01 16:29 ` Andries Brouwer
2002-10-07 12:06 ` Vojtech Pavlik
2002-10-07 12:52 ` Andries Brouwer
2002-10-07 13:23 ` Skip Ford
2002-10-07 13:39 ` Vojtech Pavlik
2002-10-01 16:49 ` Skip Ford
2002-10-01 16:51 ` Vojtech Pavlik
2002-10-01 17:41 ` Skip Ford
2002-10-01 17:39 ` Vojtech Pavlik
2002-10-01 18:11 ` Skip Ford
2002-10-01 18:38 ` Vojtech Pavlik
2002-10-01 20:04 ` Skip Ford
2002-10-01 20:53 ` Vojtech Pavlik
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=20021001151722.A11750@ucw.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=skip.ford@verizon.net \
/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;
as well as URLs for NNTP newsgroup(s).