All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 27 Aug 2003 09:48:04 +0200	[thread overview]
Message-ID: <200308270948.04190.murphyf+linux-ppc@f-m.fm> (raw)
In-Reply-To: <20030826200303.GA14385@iram.es>


On Tuesday 26 August 2003 10:03, Gabriel Paubert wrote:
> On Tue, Aug 26, 2003 at 09:24:02PM +0200, Frank Murphy wrote:
> > On Tuesday 26 August 2003 11:35, Gabriel Paubert wrote:
> > > X does its own mapping of raw keycodes to keycodes, and the mapping
> > > is surjective (arghh). The option CustomKeyCodes in X allows you to
> > > bypass this mapping (medium raw modes) but I believe it is deprecated.
>
> On a PC, the Menu key sends e0 5d (and obviously e0 dd for key up). The
> linux keycode is 127 but the X one is 117.

Could you tell me what the keycodes are for Print Screen/SysRq, Scroll Lock,
and Pause are on your keyboard? Just so I can track what F13, F14, & F15
could be.

> 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.

> BTW, I'd also like to keep somewhere the state of the fn key in the
> ADB keyboard driver. I've seen a MacOS utility which allows you to
> use the trackpad as a scroll wheel while the fn button is pressed.
> Thta's what I'd ike to copy.

Huh. That would be pretty cool. Perhaps the real numlock state as well (if
that's even possible).

Frank


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-08-27  7:48 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 [this message]
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
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=200308270948.04190.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.