9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Holger Sebert" <Holger.Sebert@ruhr-uni-bochum.de>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] German USB keyboard on Raspberry Pi
Date: Thu, 25 Apr 2013 22:38:38 +0200	[thread overview]
Message-ID: <5179944E.2080109@ruhr-uni-bochum.de> (raw)
In-Reply-To: <20130424205602.D6E59B82A@mail.bitblocks.com>

Hi,

Am 24.04.13 22:56, schrieb Bakul Shah:
> On 24 Apr 2013 21:25:13 +0200 "Holger Sebert" <Holger.Sebert@ruhr-uni-bochum.de> wrote:
>>
>> I have tried it out: The driver says
>> "sc: e0 56" when pressing the "<"-key.
>
> This means a two char sequence: e0, 0x56 is stuffed into the
> kernel device kbin. Ultimately thsi will map to the value in
> kbtabesc1[0x56]. Now kbtabesc1 is table 2 in a kbmap so we are
> looking for an entry that starts with
> 	2	86	...	# 86 == 0x56
> In /sys/lib/kbmap/de I see
> 	2       86      0
> This explains why you don't see anything.  What you want to do
> is to copy this file to, say, de2 and replace the above with
> 	2	86	'<
> And then put the following in $home/lib/profile
> 	cat /sys/lib/kbmap/de2 > /dev/kbmap
> Probably under 'case terminal'.

Thanks alot! This gets the '<'-key going.

I have tried to put the key-with-modifier (Shift and AltGr)
chars into the kbmap but with no result. "3 86 '>" and "4 86 '|"
get all ignored.

I looked into kbd.c and it seems the driver does not support
modified states of extended scan codes of the form "e0 ??".

A hack would probably be possible, but maybe I am overlooking
something?

If not, how do I recompile and install the kbd-module on the
Raspberry Pi? I changed kbd.c for testing purposes and
executed "mk install" in the directory /sys/src/9/. Although
the build succeeded the changes did not seem to be incorporated.

Sorry for drifting off topic here ...

Best,
Holger




  reply	other threads:[~2013-04-25 20:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-20 16:31 Holger Sebert
2013-04-20 19:14 ` Bakul Shah
2013-04-20 20:08   ` Holger Sebert
2013-04-20 23:18     ` Bakul Shah
2013-04-24 19:25       ` Holger Sebert
2013-04-24 20:56         ` Bakul Shah
2013-04-25 20:38           ` Holger Sebert [this message]
2013-04-25 20:41             ` erik quanstrom
2013-04-28 20:01               ` Holger Sebert
2013-04-28 21:07                 ` Bakul Shah
2013-04-30 12:59                   ` Holger Sebert
2013-04-28 21:14                 ` Richard Miller
2013-04-30 13:05                   ` Holger Sebert
2013-04-30 14:16                     ` Richard Miller
2013-05-03 12:30                 ` arisawa
2013-04-26  7:07             ` Yaroslav
2013-04-26 12:02               ` erik quanstrom
2013-04-26 12:34                 ` Richard Miller
2013-04-26 12:36                   ` erik quanstrom

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=5179944E.2080109@ruhr-uni-bochum.de \
    --to=holger.sebert@ruhr-uni-bochum.de \
    --cc=9fans@9fans.net \
    /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).