9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Building a Raspberry Pi image / Keyboard support
Date: Tue,  1 Jul 2014 23:32:50 -0700	[thread overview]
Message-ID: <20140702063250.206C0B827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Tue, 01 Jul 2014 23:01:53 PDT." <CA+MHcSqomR9EsBfYTaLRSJvo48DDBPGoMCnXF35h3ZBxFKiZMA@mail.gmail.com>

On Tue, 01 Jul 2014 23:01:53 PDT Anant Narayanan <anant@kix.in> 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.



  reply	other threads:[~2014-07-02  6:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02  6:01 Anant Narayanan
2014-07-02  6:32 ` Bakul Shah [this message]
2014-07-04 23:45   ` Anant Narayanan
2014-07-05  0:58     ` kokamoto
2014-07-05  7:01       ` Steve Simon
2014-07-06  1:15         ` kokamoto
2014-07-06  5:59           ` Shane Morris
2014-07-07  4:58           ` kokamoto
2014-07-07  5:58             ` kokamoto
2014-07-07 16:02             ` erik quanstrom
2014-07-07 23:12               ` kokamoto
2014-07-08  0:20                 ` erik quanstrom
2014-07-08 23:35           ` kokamoto
2014-07-05  8:20     ` Charles Forsyth
2014-07-05  9:01     ` Bakul Shah
2014-07-05 13:13     ` Ramakrishnan Muthukrishnan
2014-07-05 23:44       ` Anant Narayanan
2014-07-07 16:09         ` erik quanstrom
2014-07-07  9:30 Richard Miller
2014-07-07 13:26 ` kokamoto
2014-07-07  9:30 Richard Miller

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=20140702063250.206C0B827@mail.bitblocks.com \
    --to=bakul@bitblocks.com \
    --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).