From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] "gpio device" for Plan 9
Date: Sun, 29 Dec 2013 17:34:19 -0500 [thread overview]
Message-ID: <54bcd5aa745b69e3cf73fbe39ca499bf@brasstown.quanstro.net> (raw)
In-Reply-To: <D14763E3-0449-4C67-B6CD-C36AF9273BE1@gmail.com>
> Using slightly modified (unmodified in most cases) uartmini.c GPIO functions i implemented #G/gpio device:
> Structure is as follows:
> #G/gpio/
> /bcm/ ...
> /board/ ...
> /wpi/ ...
> /OK
>
> - bcm uses board revision specific pin numbering
> - board uses human readable pin addressing (board revision agnostic)
> - wpi uses wiringPi pin assignment (board revision agnostic)
> - OK pin can be used to switch on/off OK LED on the board
>
> Each directory above contains files that are mapped to pins.
> Maybe it is an overkill, i don’t know.
first off, cool!
#G seems fine to me.
it might be just as well to just export only the board wiring, letting
something in the boot-time configuration set this up.
seems worth implementing uartmini (and spi) on top, and allowing group
pin allocation to support this.
- erik
next prev parent reply other threads:[~2013-12-29 22:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 22:04 Krystian Lewandowski
2013-12-29 22:34 ` erik quanstrom [this message]
2013-12-30 7:32 ` Skip Tavakkolian
2013-12-30 22:38 ` Shane Morris
[not found] ` <35A33F66-EF03-4659-ABA1-F25082DBFE41@gmail.com>
2013-12-31 17:46 ` Krystian Lewandowski
2013-12-31 19:18 ` erik quanstrom
2013-12-31 19:37 ` Shane Morris
2013-12-31 19:48 ` Skip Tavakkolian
2013-12-31 19:50 ` erik quanstrom
2013-12-31 20:45 ` Shane Morris
2013-12-31 22:03 ` erik quanstrom
2013-12-31 22:17 ` Shane Morris
2013-12-31 22:52 ` erik quanstrom
2013-12-31 22:57 ` Krystian Lewandowski
2013-12-31 23:16 ` Shane Morris
2013-12-31 23:35 ` Shane Morris
2014-01-01 0:04 ` Krystian Lewandowski
2014-01-01 0:12 ` Shane Morris
2014-01-01 1:12 ` Matthew Veety
2014-01-01 11:38 ` Richard Miller
2014-01-01 22:16 ` erik quanstrom
2014-02-28 23:30 ` Krystian Lewandowski
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=54bcd5aa745b69e3cf73fbe39ca499bf@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--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).