From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 port to Raspberry Pi 3 Model B (ARM64)?
Date: Mon, 29 Feb 2016 12:33:43 -0800 [thread overview]
Message-ID: <20160229203343.495CCB82A@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Mon, 29 Feb 2016 20:28:04 GMT." <f0675cf2d5ba2278af34e4e7f67cbf9f@hamnavoe.com>
On Mon, 29 Feb 2016 20:28:04 GMT Richard Miller <9fans@hamnavoe.com> wrote:
> > Now that RPI3 is generally available, I'm wondering if there are any
> > efforts underway to port Plan 9 to it.
>
> "Underway" might be a bit ambitious since it was only announced today.
> I've ordered one to have a play with.
>
> > I would like to help in any way I
> > can.
>
> Finding a programming manual for the BCM43438 wifi/bluetooth chip would
> be a good start.
>
> Incidentally I can confirm that the Raspberry Pi Zero runs Plan 9 happily.
In theory one should be able to run the standard 9pi image on
pi3.
10-12 years ago FreeBSD had "project Evil" for an NDIS shim
layer that allowed use of windows network drivers on FreeBSD.
Has anyone considered writing a shim that allows use of a
FreeBSD driver with plan9?
next prev parent reply other threads:[~2016-02-29 20:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 20:06 Skip Tavakkolian
2016-02-29 20:28 ` Richard Miller
2016-02-29 20:33 ` Bakul Shah [this message]
2016-02-29 21:46 ` erik quanstrom
2016-03-01 10:04 ` Mark Lee Smith
2016-03-01 11:04 ` Aram Hăvărneanu
2016-03-03 14:50 ` Richard Miller
2016-03-03 15:28 ` Charles Forsyth
2016-03-03 15:31 ` Charles Forsyth
2016-03-03 15:37 ` Richard Miller
2016-03-03 16:14 ` Charles Forsyth
2016-09-07 23:54 ` James A. Robinson
2016-03-02 6:49 ` Ramakrishnan Muthukrishnan
2016-03-02 9:10 ` Richard Miller
2016-03-02 9:22 ` Ramakrishnan Muthukrishnan
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=20160229203343.495CCB82A@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).