From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <20140702063250.206C0B827@mail.bitblocks.com> References: <20140702063250.206C0B827@mail.bitblocks.com> From: Anant Narayanan Date: Fri, 4 Jul 2014 16:45:28 -0700 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=14dae9cc9d348c297204fd66b91c Subject: Re: [9fans] Building a Raspberry Pi image / Keyboard support Topicbox-Message-UUID: ffe2166c-ead8-11e9-9d60-3106f5b1d025 --14dae9cc9d348c297204fd66b91c Content-Type: text/plain; charset=UTF-8 That worked great, thank you! I was able to get the keyboard to work as well, but it seems there is a different bug where plugging in both a keyboard and mouse at the same time causes usb/kb to fail. -Anant On Tue, Jul 1, 2014 at 11:32 PM, Bakul Shah wrote: > On Tue, 01 Jul 2014 23:01:53 PDT Anant Narayanan wrote: > > > > 1. I'm trying to get a custom built kernel to boot but not having great > > luck, unfortunately. I got as far as "mk 'CONF=pi'" in /sys/src/9/bcm > > (those are the latest sources, correct?) which generated a 2M kernel > named > > 's9pi'. I added that to the FAT partition on the standard 9pi SD card > image > > and edited config.txt to point to it. Now, when I boot I see a rainbow > > pattern screen -- switching back to the 9pi kernel in config.txt makes it > > boot again. > > mk should've created 9pi and s9pi. Copy 9pi to the fat partition, not > s9pi. > > > What am I doing wrong? > > The RPi boot program doesn't know about plan9 executables. It > will just copy the bits from the kernel file specified in > config.txt at address 0x8000 and jump there. See 9/bcm/words > for some details. > > > 2. A couple of my keyboards don't work with the standard kernel on the SD > > card (the mouse works fine). Is /sys/src/omap/usbehciomap.c the right > place > > for me to start looking into adding support for them? > > This thread may help: > > https://groups.google.com/forum/#!topic/comp.os.plan9/ycok6NTCWCg > > Ideally you shouldn't need more than create a custom kbmap file. > > --14dae9cc9d348c297204fd66b91c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
That worked great, thank you!

I was able to ge= t the keyboard to work as well, but it seems there is a different bug where= plugging in both a keyboard and mouse at the same time causes usb/kb to fa= il.

-Anant


On Tue, Jul 1, 2014 at 11:32 PM, Bakul Shah = <bakul@bitblock= s.com> wrote:
On Tue, 01 Jul 2014 23:01:53= PDT Anant Narayanan <anant@kix.in&g= t; wrote:
>
> 1. I'm trying to get a custom built kernel to boot but not having = great
> luck, unfortunately. I got as far as "mk 'CONF=3Dpi'"= ; in /sys/src/9/bcm
> (those are the latest sources, correct?) which generated a 2M kernel n= amed
> 's9pi'. I added that to the FAT partition on the standard 9pi = SD card image
> and edited config.txt to point to it. Now, when I boot I see a rainbow=
> pattern screen -- switching back to the 9pi kernel in config.txt makes= it
> boot again.

mk should've created 9pi and s9pi. =C2=A0Copy 9pi to the fat part= ition, not s9pi.

> What am I doing wrong?

The RPi boot program doesn't know about plan9 executables. It
will just copy the bits from the kernel file specified in
config.txt at address 0x8000 and jump there. See 9/bcm/words
for some details.

> 2. A couple of my keyboards don't work with the standard kernel on= the SD
> card (the mouse works fine). Is /sys/src/omap/usbehciomap.c the right = place
> for me to start looking into adding support for them?

This thread may help:

https://groups.google.com/forum/#!topic/comp.os.plan9/= ycok6NTCWCg

Ideally you shouldn't need more than create a custom kbmap file.


--14dae9cc9d348c297204fd66b91c--