From: "Holger Sebert" <Holger.Sebert@ruhr-uni-bochum.de>
To: 9fans@9fans.net
Subject: Re: [9fans] German USB keyboard on Raspberry Pi
Date: Sun, 28 Apr 2013 22:01:17 +0200 [thread overview]
Message-ID: <517D800D.6040507@ruhr-uni-bochum.de> (raw)
In-Reply-To: <343d813c2c86074a7f58233b90dcc9af@coraid.com>
Hi,
I did a quick hack on kbd.c and could make the "<,>,|" key
work. Awesome! Thank you all for your help.
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"
Although it was easy to fix, I wonder where this inconsistency
in the source tree came from. Did I miss an update or 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?
Best,
Holger
Am 25.04.13 22:41, schrieb erik quanstrom:
>> 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.
>
> unfortunately. you need to rebuild all of usb (or at least usbd), then your kernel
> for the changes to always take effect.
>
> - erik
>
next prev parent reply other threads:[~2013-04-28 20:01 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 [this message]
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=517D800D.6040507@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).