From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Raspberry Pi: won't recognize the USB mouse
Date: Tue, 4 Mar 2014 10:18:17 -0800 [thread overview]
Message-ID: <20140304181817.9A32DB827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Tue, 04 Mar 2014 11:26:31 EST." <2ffa27d7c79801528556705f4cf55346@mikro.quanstro.net>
On Tue, 04 Mar 2014 11:26:31 EST erik quanstrom <quanstro@quanstro.net> wrote:
>
> first, apply the patch to the source, then build all of usb
>
> 9fs sources
> cd /sys/src/cmd/usb/lib
> cp /n/sources/patch/usbshortdesc/dev.c dev.c
> cd ..
> mk install
>
> then, build a new kernel
>
> cd /sys/src/cmd/bcm; mk
>
> i believe you can give it a quick test by doing a hot reboot.
>
> fshalt -r ./9pi
>
> if you'd like to install the new kernel on the flash, then
>
> dossrv
> mount /srv/dos /n/9fat /dev/sdM0/dos
> cd /n/9fat
> cp 9pi 9pi-dist
> cp /sys/src/9/bcm/9pi 9pi-usbfix
> cp 9pi-usbfix 9pi
>
> and reboot. if this doesn't work out, you can rescue yourself
> by using anything that understands fat and replacing 9pi
> with the contents of 9pi-dist.
IIRC Ramakrishnan doesn't have a working 9pi system.
I put 9pi with this patch in contrib/bakul on sources. It was
cross-built on a 386 VM with a pull done this morning + the
above patch. I had to rebuild the host 5c due to rune related
errors so I am not 100% certain this will work (I probably
should've done a full rebuild of the host binaries too).
He should be able to mount the dos partition on another
machine and replace 9pi on it.
next prev parent reply other threads:[~2014-03-04 18:18 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 16:27 Ramakrishnan Muthukrishnan
2014-02-26 17:19 ` Richard Miller
2014-02-27 16:27 ` Ramakrishnan Muthukrishnan
2014-02-27 16:35 ` Ramakrishnan Muthukrishnan
2014-02-27 17:05 ` Ramakrishnan Muthukrishnan
2014-02-27 17:08 ` Lyndon Nerenberg
2014-02-27 17:31 ` Ramakrishnan Muthukrishnan
2014-02-27 18:03 ` Bakul Shah
2014-02-28 11:10 ` Ramakrishnan Muthukrishnan
2014-02-28 11:28 ` Richard Miller
2014-02-28 14:12 ` Ramakrishnan Muthukrishnan
2014-02-28 14:35 ` Bakul Shah
2014-02-28 15:12 ` Ramakrishnan Muthukrishnan
2014-02-28 14:45 ` Anthony Sorace
2014-02-28 15:15 ` Ramakrishnan Muthukrishnan
2014-02-28 16:24 ` Bakul Shah
2014-03-04 14:12 ` Ramakrishnan Muthukrishnan
2014-03-04 14:27 ` erik quanstrom
2014-03-04 15:54 ` Ramakrishnan Muthukrishnan
2014-03-04 16:26 ` erik quanstrom
2014-03-04 18:18 ` Bakul Shah [this message]
2014-03-04 18:26 ` erik quanstrom
2014-03-08 14:56 ` Ramakrishnan Muthukrishnan
2014-03-08 14:59 ` erik quanstrom
2014-03-09 13:25 ` Ramakrishnan Muthukrishnan
2014-03-09 13:46 ` erik quanstrom
2014-03-05 10:57 ` Richard Miller
2014-03-05 10:59 ` Richard Miller
2014-02-27 17:10 ` erik quanstrom
2014-02-27 17:15 ` Steve Simon
2014-02-26 17:22 ` Ramakrishnan Muthukrishnan
2014-02-28 4:31 ` Grant Mather
2014-02-28 9:05 ` erik quanstrom
2014-03-01 5:43 Michael Hansen
2014-03-01 12:09 ` Richard Miller
2014-03-01 12:12 ` erik quanstrom
2014-03-02 10:46 ` Richard Miller
2014-03-02 14:57 ` erik quanstrom
2014-03-02 19:54 ` Richard Miller
2014-03-02 23:22 ` Winston Kodogo
2014-03-03 1:29 ` erik quanstrom
2014-03-03 11:05 ` Richard Miller
2014-03-03 11:24 ` Richard Miller
2014-03-03 13:39 ` erik quanstrom
2014-03-02 1:12 Michael Hansen
2014-03-02 1:39 ` 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=20140304181817.9A32DB827@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).