From: Chris McGee <newton688@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9front on raspberry pi
Date: Wed, 2 Nov 2016 07:15:44 -0400 [thread overview]
Message-ID: <EA9A5C7C-9913-46B8-969E-3D85AF7213B7@gmail.com> (raw)
In-Reply-To: <23C522F1-984A-4060-951D-513A329F7A29@quintile.net>
The GPIO doesn't have a manual page as far as I know. The implementation came from what is in 9front mainline and is in #G. I agree that it would be good to have a manual page for it there.
mDNS is running as bcast9p process and is written in Go. It's based on a Go library and uses udp multicast support for plan 9 that is only in latest git master branch, slated for Go 1.8.
Go SDK in this image is 1.7.3 though. It should be reasonably stable.
Chris
> On Nov 2, 2016, at 3:57 AM, Steve Simon <steve@quintile.net> wrote:
>
> hi,
>
> this is interesting.
>
> can you tell me what the gpio file system looks like (pointer to man page?). also, is the mDNS client the go one discussed recently or a c implementation?
>
> i have never go'ed and have been thinking about writing a upnp renderer for plan9 for years...
>
> -Steve
>
>
>> On 2 Nov 2016, at 07:48, arisawa <arisawa@ar.aichi-u.ac.jp> wrote:
>>
>> I’ve tried both pi1 and pi2.
>> both devices successfully boot up.
>>
>> my impression only in primitive usage is:
>> pi2 is fine. thanks Chris!
>> pi1 is a bit unsteady on usb device. usb keyboard is sometimes accidentally detached.
>>
>>
>>> 2016/11/02 14:05、arisawa <arisawa@ar.aichi-u.ac.jp> のメール:
>>>
>>> thanks, i will try.
>>>
>>> is this for pi1 or pi2 or both?
>>>
>>>> 2016/11/02 10:35、Chris McGee <newton688@gmail.com> のメール:
>>>>
>>>> Hi All,
>>>>
>>>> I have released an experimental 9front raspberry pi image that I use for my cluster.
>>>> https://github.com/sirnewton01/rpi-9front/releases/tag/nov-2016
>>>>
>>>> Highlights:
>>>> -Latest 9front release 2016-10-27
>>>> -Merged in Richard Millar’s kernel from a couple of months ago
>>>> -Retains 9front GPIO filesystem structure
>>>> -Link local ipv4 address on boot (low likelihood of collisions)
>>>> -Discovery of other nodes using multicast DNS through the ‘find9p’ command
>>>> -9fs mount other nodes on the network
>>>> -Go 1.7.3
>>>> -Git script (works with github and google source repos)
>>>>
>>>> Cheers,
>>>> Chris
>>>
>>>
>>
>
>
next prev parent reply other threads:[~2016-11-02 11:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 1:35 Chris McGee
2016-11-02 5:05 ` arisawa
2016-11-02 7:48 ` arisawa
2016-11-02 7:57 ` Steve Simon
2016-11-02 10:47 ` arisawa
2016-11-02 11:17 ` Chris McGee
2016-11-02 12:05 ` arisawa
2016-11-02 13:14 ` Chris McGee
2016-11-02 13:34 ` Steve Simon
2016-11-02 11:18 ` arisawa
2016-11-02 13:31 ` Steve Simon
2016-11-02 11:15 ` Chris McGee [this message]
2016-11-04 0:55 ` arisawa
2016-11-06 23:29 ` Chris McGee
2016-11-07 11:44 ` arisawa
2016-11-07 17:21 ` Chris McGee
2016-11-02 11:09 ` Chris McGee
2016-11-03 0:01 ` Chris McGee
-- strict thread matches above, loose matches on Subject: below --
2016-09-11 17:30 Chris McGee
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=EA9A5C7C-9913-46B8-969E-3D85AF7213B7@gmail.com \
--to=newton688@gmail.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).