From: Martin Costabel <costabel@wanadoo.fr>
To: Gerd Knorr <kraxel@goldbach.in-berlin.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Missing USB keys
Date: Wed, 27 Oct 1999 14:05:24 +0200 [thread overview]
Message-ID: <3816EA84.41450D3C@wanadoo.fr> (raw)
In-Reply-To: Pine.LNX.4.10.9910271114510.1021-100000@macintoy.masq.in-berlin.de
Gerd Knorr wrote:
>
> How can I figure out the correct adb keycodes? Hav'nt such a keyboard...
There are German keymaps in the console-tools rpm, for example
/usr/lib/kbd/keymaps/mac/mac-de-latin1-nodeadkeys.kmap.gz
I guess you would have to compare this with a corresponding German usb
keymap. Don't know where to find one, but I'm sure such keymaps have
been offered on the net.
> > --- drivers/usb/maps/usb.map 1999/04/28 11:52:38 1.1
> > +++ drivers/usb/maps/usb.map 1999/10/26 17:34:42
> > @@ -88,7 +88,7 @@
> > keycode 49 = backslash bar
> ^^^^^^^^^^^^^^^^^^^^
> > -keycode 50 =
> > +keycode 50 = backslash bar
> ^^^^^^^^^^^^^^^^^^^^
>
> Does'nt look like a good idea...
Looks bad, indeed. Works, however, on the B&W G3 where I tried it :-)
It just means that both USB keycodes 49 and 50 will be mapped to the
same ADB keycode. I don't quite remember (have been away from linux for
a month), but I think only one of the two actually exists on a key.
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-10-27 12:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-26 17:47 Problems compiling ppc kernels Mike Panetta
1999-10-26 19:00 ` David Riley
1999-10-26 19:22 ` Neil Russell
1999-10-27 1:23 ` Dan Malek
1999-10-26 20:21 ` Ani Joshi
1999-10-26 20:20 ` Mike Panetta
1999-10-26 21:41 ` Gerd Knorr
1999-10-27 1:45 ` Missing USB keys (Was Re: Problems compiling ppc kernels.) Martin Costabel
1999-10-27 9:24 ` Missing USB keys Gerd Knorr
1999-10-27 12:05 ` Martin Costabel [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-10-27 2:44 bob
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=3816EA84.41450D3C@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=kraxel@goldbach.in-berlin.de \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).