From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Question re source trees
Date: Thu, 29 Sep 2016 09:08:27 +0100 [thread overview]
Message-ID: <f57cde56d94b1b5863e85910a1a1fef7@hamnavoe.com> (raw)
In-Reply-To: <CAPd04b6Z_aWzRYYoeVJJX=UfJTBpphtHmCPZieQJXizCpL4q6w@mail.gmail.com>
> I was wondering whether the changes made
> by Mr. Miller for supporting the Raspberry Pi were getting folded
> back into a source tree available via means other than those with
> an active plan9 system (I see references to /n/sources/contrib/miller
> which I assume is a 9fs mount).
You can also use a web browser to access /n/sources; it's mapped to
http://plan9.bell-labs.com/sources (when the server isn't down).
Source for all the raspberry pi kernel changes is kept up to date in
http://plan9.bell-labs.com/sources/contrib/miller/9/bcm
> ... I couldn't find anything discussing whether other
> hardware was supported (e.g., the built-in wifi on the Pi 3).
The Broadcom 43430 wifi chip on the pi3 turns out to be functionally
almost the same as the 4330, for which I had written a driver some
time ago for another platform. The client who commissioned that work
has generously agreed to its release, so 9piwifi support will appear
shortly. (The driver is working but WPA authentication needs a few
tweaks.)
I can also supply bluetooth code for the pi3 if anyone is interested.
next prev parent reply other threads:[~2016-09-29 8:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 7:15 James A. Robinson
2016-09-29 8:08 ` Richard Miller [this message]
2016-09-29 8:12 ` Kurt H Maier
2016-09-29 10:54 ` Richard Miller
2016-10-28 21:30 ` Kurt H Maier
2016-09-29 11:55 ` Ole-Hjalmar Kristensen
2016-09-29 13:22 ` James A. Robinson
2016-10-02 17:42 ` [9fans] plan9.bell-labs.com hates AppleWebKit? James A. Robinson
2016-10-03 2:01 ` sl
2016-10-04 12:59 ` arisawa
2016-10-05 19:01 ` Sergey Zhilkin
2016-10-31 10:23 [9fans] Question re source trees Richard Miller
2016-10-31 16:06 ` Kurt H Maier
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=f57cde56d94b1b5863e85910a1a1fef7@hamnavoe.com \
--to=9fans@hamnavoe.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).