From: Sean Hinchee <henesy.dev@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan9-bcm GPIO control raspberry pi
Date: Fri, 16 May 2014 22:12:59 -0500 [thread overview]
Message-ID: <CADmmOS8_EWu3OCjXudV1WE6Vr1Ak4PLS=-ROQivFvsr7JfMK-A@mail.gmail.com> (raw)
In-Reply-To: <CAJSxfmKUHUQCHib3W+94x7Nyq881dQeGUcjccX+n9v32Dtw90Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 333 bytes --]
Ok, it ran when bound to /sys/src/9/bcm. Flawless success. @cinap_lenrek,
the folder was the source for the bcm kernel thing I linked above, it's
built to support GPIO afaik, I'd like to play with GPIO whilst I learn
plan9 on this pi.
If I may ask, what is the reason that it ran when bound to bcm, permissions
or something?
[-- Attachment #2: Type: text/html, Size: 380 bytes --]
prev parent reply other threads:[~2014-05-17 3:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 20:33 Sean Hinchee
2014-05-16 20:40 ` cinap_lenrek
2014-05-16 20:46 ` Skip Tavakkolian
2014-05-17 3:12 ` Sean Hinchee [this message]
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='CADmmOS8_EWu3OCjXudV1WE6Vr1Ak4PLS=-ROQivFvsr7JfMK-A@mail.gmail.com' \
--to=henesy.dev@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).