public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Benoit Plessis <benoit@plessis.info>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Input system and keycodes > 256
Date: Thu, 3 Jun 2004 01:42:33 +0200	[thread overview]
Message-ID: <20040602234233.GC1366@ucw.cz> (raw)
In-Reply-To: <1082938686.21842.50.camel@osiris.localnet.fr>

On Mon, Apr 26, 2004 at 02:18:07AM +0200, Benoit Plessis wrote:
> Hi,
> 
> I've digged into the kernel source/tools since i do own a new logitech
> USB keyboard MX with a great number a keys.
> 
> There are two kind of addons keys, some works (scancode in the e0 XX
> form): Email, Prev, Next, Play/Pause, Vol+/-, Mute, ...
>  + some of thoses generate a simple keycode eg 
>      Vol+: 0x73 | 0xf3 (scancodes: 0xe0 0x30 | 0xe0 0xb0)
>  + some doesn't eg:
>      play: 0x00 0x81 0xa4 | 0x80 0x81 0xa4  (scancodes: 0xe0 0x22 | 0xe0
> 0xa2)
>  _   but all thoses key work quite well under X.
> 
> The pb come from the new 'Function' keys with replace F1-F12 when the
> Flock mod isn't active (it's an hardware mod) and some other (Messenger,
> Webcam, iTouch and Buy).
> 
> When grabbing with 'showkey -s' nothing appear
> When grabbing with 'showkey' i got keycodes like '0x00 0x82 0xd0 | 0x80
> 0x82 0xd0' (i got same keycodes when pressing mouse buttons except those
> are in 0x82 0x90 -> 0x82 0x97 range)
> 
> When using the evbug module see that those keys generates > 255
> keycodes. (see attached file)
> And strangely all thoses keys generates the sames strings than keys with
> keycode2 = keycode - 256.
> 
> Eg: the 'New' function key (shared with F1) reported by evbug as 336
> keycode as the same effect as keycode 80 (keypad 2).
> 
> So i'm a little lost :(
> And i wanted some direction on how make thoses keys work correctly on
> the console (and X eventually. Actually under X some keys generate mouse
> button event, some doesn't generate anything).
> 
> I am wondering if a good start would not be to extend the kbentry
> structure, to use unsigned short at least for the index so whe can acces
> a fully 512 entry keymap.

I'm sorry, but X only understands the RAW PS/2 protocol, and that one
can only transport keycodes up to 240.

For keycodes above 240, XFree86 would either need to use the MediumRAW
mode, or use event devices for parsing the keyboard.

-- 

      parent reply	other threads:[~2004-06-02 23:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-26  0:18 Input system and keycodes > 256 Benoit Plessis
2004-04-26 10:48 ` David Gómez
2004-04-26  9:20   ` Benoit Plessis
2004-06-02 23:40   ` Vojtech Pavlik
2004-04-28 23:48 ` Andries Brouwer
2004-05-04 21:31   ` Benoit Plessis
2004-05-09 18:47     ` Andries Brouwer
2004-06-02 23:43   ` Vojtech Pavlik
2004-06-02 23:42 ` Vojtech Pavlik [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=20040602234233.GC1366@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=benoit@plessis.info \
    --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