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: Tue, 30 Apr 2013 14:59:20 +0200 [thread overview]
Message-ID: <995e72ceea8bc9e7ff5650b2b1c8e640@mpx2.rz.ruhr-uni-bochum.de> (raw)
In-Reply-To: <20130428210702.E4949B827@mail.bitblocks.com>
Hi,
Am 2013-04-28 23:07, schrieb Bakul Shah:
> On 28 Apr 2013 22:01:17 +0200 "Holger Sebert"
> <Holger.Sebert@ruhr-uni-bochum.de> wrote:
>> I did a quick hack on kbd.c and could make the "<,>,|" key
>> work. Awesome! Thank you all for your help.
>
> What was the fix?
The relevant section from kbd.c is
if(kbscan->esc1){
c = kbtabesc1[c];
kbscan->esc1 = 0;
} else if(kbscan->esc2){
kbscan->esc2--;
return;
} else if /* ... */
The logic that is implemented here implies that
sequences of the form "e0 xx" cannot be combined
with a modifier like Shift or AltGr.
Since "<,>,|" is the only key on my keyboard for
which this is relevant, I simply changed the first
line to
if(kbscan->esc1 && c != 0x58){
/*...*/
This way, the sequence "e0 58" is actually interpreted
as "58", so that Shift and AltGr again work.
Of course, this is not a clean solution at all. But at
least it does not change the semantics of the kbmap-file.
>
>> In the 'bcm' directory some modules refer to 'omap' although
>> they apparently mean 'port', like this:
>>
>> #include "../omap/random.c"
>>
>> which should be
>>
>> #include "../port/random.c"
>
> Files from ../port are automatically picked up so you don't
> need files in bcm that just include ../port/something.
>
>> Furthermore, I noticed that the build system would build _all_
>> of the kernel each time I invoke 'mk', even though only little
>> or nothing has changed. Is this the way it is intended to be?
>
> Looks like your source files have a modification time newer
> than the current time (as seen on your machine). Either
> manually set date/time on boot (if not connected to the net)
> or set
> TIMESYNCARGS=(-n pool.ntp.org)
> in /rc/bin/termrc.local. Pick a public ntpserver near you
> instead of pool.ntp.org.
Oh yes, did not think about the missing RTC on the Pi. Thanks
for the solution!
Best,
Holger
next prev parent reply other threads:[~2013-04-30 12:59 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
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 [this message]
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=995e72ceea8bc9e7ff5650b2b1c8e640@mpx2.rz.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).