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: Wed, 24 Apr 2013 21:25:13 +0200	[thread overview]
Message-ID: <51783199.5080909@ruhr-uni-bochum.de> (raw)
In-Reply-To: <20130420231810.B50B7B82A@mail.bitblocks.com>

Hi,

Am 21.04.13 01:18, schrieb Bakul Shah:
> On 20 Apr 2013 22:08:00 +0200 "Holger Sebert" <Holger.Sebert@ruhr-uni-bochum.de> wrote:
>> This phenomenon does not exist on a x86-based
>> installation of Plan 9, so it seems specific
>> to the Raspberry Pi.
>
> Strange.... Is the x86 installation on real hardware or under
> a VM? If the latter, the underlying OS may be doing the right
> thing for you. In any case, you can try to find out what
> scancodes are reported and create your own kbmap file.
>
> % echo kbargs -dd > /dev/usbdctl
> Remove and replug your keyboard and watch what happens when
> you press your "< | >" key.
>
> When I do this I get a constant stream of
>
> kbd mod 0: kc 0 kc 0 kc 0 kc 0 kc 0 kc 0
> kbd mod 0: kc 0 kc 0 kc 0 kc 0 kc 0 kc 0
> kbd mod 0: kc 0 kc 0 kc 0 kc 0 kc 0 kc 0
>
> which is probably due to my el-cheapo keyboard
> but may be this will behave better for you.
>

I have tried it out: The driver says
"sc: e0 56" when pressing the "<"-key.
This is nice! However, I have no idea how
to put this (extended?) scan code into
the kbmap-file. The naive try:

0 0xe056 '<

resulted in "cat: write error copying lib/kbmap/de:
bad arg in system call".

Any idea?

Best,
Holger



  reply	other threads:[~2013-04-24 19:25 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 [this message]
2013-04-24 20:56         ` Bakul Shah
2013-04-25 20:38           ` Holger Sebert
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=51783199.5080909@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).