From: Frank Murphy <murphyf+linux-ppc@f-m.fm>
To: Gabriel Paubert <paubert@iram.es>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Linux kernel / USB keyboard scancode problems
Date: Fri, 29 Aug 2003 17:28:01 +0200 [thread overview]
Message-ID: <200308291728.01954.murphyf+linux-ppc@f-m.fm> (raw)
In-Reply-To: <20030827182950.GA12646@iram.es>
On Wednesday 27 August 2003 8:29, Gabriel Paubert wrote:
> Well, except for Scroll Lock, it's a mess. It depends on the other which
> are down at the time the key is pressed.
Thanks for these. Because they're such a mess, perhaps the codes for F13, F14,
and F15 should be used instead. Now just to find out what they are, and if
all Apple keyboards have these keys as F13, 14, & 15.
> > > The following might be sufficient (just a wild guess, and it will
> > > certainly break if you don't use linux keycodes):
> >
> > Thanks for your guessed fix. I'll have to look at what you've done, but,
> > wow, it's pretty cryptic.
>
> Well, it is really simple. Replace 101 by 127 in the ADB to Linux keycode
> mappings. In this way the translation back to "raw" keycodes (only cooked
> twice!) gives 349, which is 256 + 93 (0xe0 0x5d).
Well, I guess the trick is to know which one to change. :)
Frank
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-08-29 15:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-23 12:09 Linux kernel / USB keyboard scancode problems Frank Murphy
2003-08-26 9:35 ` Gabriel Paubert
2003-08-26 19:24 ` Frank Murphy
2003-08-26 20:03 ` Gabriel Paubert
2003-08-27 7:48 ` Frank Murphy
2003-08-27 18:29 ` Gabriel Paubert
2003-08-29 15:28 ` Frank Murphy [this message]
2003-08-30 15:20 ` Gabriel Paubert
2003-09-01 10:56 ` Frank Murphy
2003-09-01 11:46 ` Gabriel Paubert
2003-09-01 12:59 ` Frank Murphy
2003-09-02 12:12 ` Gabriel Paubert
2003-09-02 15:59 ` Frank Murphy
2003-09-08 9:03 ` Frank Murphy
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=200308291728.01954.murphyf+linux-ppc@f-m.fm \
--to=murphyf+linux-ppc@f-m.fm \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paubert@iram.es \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.