mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, sven.kissner@consistencies.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: logitech cordless desktop deluxe optical keyboard issues
Date: Sun, 11 Jan 2004 14:58:18 +0100 (MET)	[thread overview]
Message-ID: <UTC200401111358.i0BDwIM08113.aeb@smtp.cwi.nl> (raw)

    > That is a kernel message, not showkey output.
    > (BTW - which kernel precisely? The message is not the 2.6.0 one.)
    > Maybe showkey -s never sees them?

    i'm running a vanilla 2.6.1-kernel, without any additional patches.
    you're right about the message, showkey is exiting after 10s, even
    if i keep one of the 'problematic' keys pressed..

Yes, I see. Looking at 2.6.1 things are a bit different again,
but raw mode is very broken. Instead of reporting what the
keyboard sends, as raw mode is supposed to do, the scancode
is first converted to a keycode, and in the case of an unknown
scancode it is then just thrown away. In raw mode the keycode
is later translated back to a scancode (using a correspondence
that is not 1-1), but in your case we never get that far.

Did you try using setkeycodes? Say

# setkeycodes 91 120 92 121

to map scancode 0x91 to keycode 120 and 0x92 to 121.

Andries

             reply	other threads:[~2004-01-11 14:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-11 13:58 Andries.Brouwer [this message]
2004-01-11 16:05 ` sven kissner
2004-01-11 16:32   ` Andries Brouwer
2004-01-11 18:37     ` sven kissner
  -- strict thread matches above, loose matches on Subject: below --
2004-01-11 19:03 Andries.Brouwer
2004-01-11 19:35 ` sven kissner
2004-01-11 19:46   ` Andries Brouwer
2004-01-22 22:49     ` sven kissner
2004-01-11  4:05 Andries.Brouwer
2004-01-11  8:27 ` sven kissner
2004-01-11  0:28 Andries.Brouwer
2004-01-11  1:53 ` logitech cordless desktop deluxe optical keyboard issues sven kissner
2004-01-10 21:30 sven kissner

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=UTC200401111358.i0BDwIM08113.aeb@smtp.cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sven.kissner@consistencies.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

all inboxes | Powered by JetHome®