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: Tue, 2 Sep 2003 17:59:12 +0200 [thread overview]
Message-ID: <200309021759.13949.murphyf+linux-ppc@f-m.fm> (raw)
In-Reply-To: <20030902121204.A28288@mrt-lx1.iram.es>
On Tuesday 02 September 2003 2:12, Gabriel Paubert wrote:
> On Mon, Sep 01, 2003 at 02:59:21PM +0200, Frank Murphy wrote:
> > On Monday 01 September 2003 1:46, Gabriel Paubert wrote:
> > > 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.
>
> What? Exactly the same code for keycodes and scancodes?
>
> (85=0x55, 115=0x73, 119=0x77)
Exactly the same. I just double-checked.
F13 = 85 / 0x55 0xd5
F14 = 115 / 0x73 0xf3
F15 = 119 / 0x77 0xf7
> P.S: I'm going to be a lot less responsive the rest of the week, I'm
> having a few free days right now after having worked all over the
> week-end.
Enjoy the time off.
Frank
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-09-02 15: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
2003-09-02 12:12 ` Gabriel Paubert
2003-09-02 15:59 ` Frank Murphy [this message]
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=200309021759.13949.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.