linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Giuliano Pochini <pochini@shiny.it>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: keyboard
Date: Thu, 17 Aug 2000 09:37:17 +0200 (CEST)	[thread overview]
Message-ID: <XFMail.000817093717.pochini@shiny.it> (raw)
In-Reply-To: <Pine.LNX.4.10.10008162005100.22954-100000@opal.biophys.uni-duesseldorf.de>


>> Aug 15 15:56:35 Jay kernel: keyboard.c: can't emulate rawmode for keycode
>> 165
>>
>> I see that there are some unused codes in the translation table in
>> usb/keybdev.c. May I use them to map the new keys ?
>
> Big win if all of these keys produce the same keycode :-)
>
> You can solve your problem much easier with loadkeys and a tailored
> console keymap.

No, I can't. mac_keyb.c uses a byte to store the pressed key. 1 bit is used
for pressed/released flag, so key codes range is 1-127. That special keys
have a code > 127 so currently they're not mapped at all.
I must change the kernel to remap that codes to something < 128.

Or perhaps I'll fix it by allowing int16_t keycodes just like on peecees.

Bye.
    Giuliano Pochini ->)|(<- Shiny Corporation {AS6665} ->)|(<-


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

  reply	other threads:[~2000-08-17  7:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-16 23:02 keyboard Giuliano Pochini
2000-08-16 18:07 ` keyboard Michael Schmitz
2000-08-17  7:37   ` Giuliano Pochini [this message]
2000-08-17  9:48     ` keyboard Michael Schmitz
2000-08-17 11:03       ` keyboard Giuliano Pochini
2000-08-17 17:47         ` keyboard Michael Schmitz
2000-08-17  7:38   ` keyboard Giuliano Pochini

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=XFMail.000817093717.pochini@shiny.it \
    --to=pochini@shiny.it \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=schmitz@opal.biophys.uni-duesseldorf.de \
    /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;
as well as URLs for NNTP newsgroup(s).