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: Mon, 1 Sep 2003 14:59:21 +0200 [thread overview]
Message-ID: <200309011459.21786.murphyf+linux-ppc@f-m.fm> (raw)
In-Reply-To: <20030901114602.A28710@mrt-lx1.iram.es>
On Monday 01 September 2003 1:46, Gabriel Paubert wrote:
> > Yeah, the keycode/scancode/keysym stuff is a twisty maze. I do have the
> > hardware to test these changes, if you have a guess to what they should
> > be.
>
> What keyboard(s) do you have ?
I have an original iBook with its built-in US layout keyboard. I also have a
"narrow" iMac US keyboard (F1-F12 and no Delete or Insert key). I also have
access to a UK Apple Pro Keyboard. This is the one with the F13, F14, & F15
keys.
> I've only access to my Pismo now, and it obviously does not have the
> F13-F15 keys. I shall be back in front on my G4 in a few days.
>
> I'd first need to know what "showkey -k" and "showkey -s" give for these
> 3 keys on your keybord.
In the order F13, F14, then F15, with showkey -k, I get 85, 115, and 119.
With showkey -s, I get 0x55 0xd5, 0x73 0xf3, and 0x77 0xf7.
Frank
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-09-01 12:59 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
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 [this message]
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=200309011459.21786.murphyf+linux-ppc@f-m.fm \
--to=murphyf+linux-ppc@f-m$(echo .)fm \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
--cc=paubert@iram$(echo .)es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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