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: Mon, 7 Nov 2016 12:21:12 -0500 [thread overview]
Message-ID: <1A7D8BE0-759A-414D-807B-0C939F60A9F2@gmail.com> (raw)
In-Reply-To: <055375DF-1D3F-4F57-BA53-D7F4AEE1C73E@ar.aichi-u.ac.jp>
> On Nov 7, 2016, at 6:44 AM, arisawa <arisawa@ar.aichi-u.ac.jp> wrote:
>
> by the way I said about raspi 1
>> the display size is 1920x1200.
>> when I try to resize a window, the mouse cursor flips and it is difficult to resize.
> This phenomenon was stopped when I connected lan cable.
> I don’t know the reason.
Interesting data point. Thank you. I tend to keep mine plugged into an active Ethernet switch. I'll try without to see if I can narrow down the problem.
>
> I looked the source code and I guess for raspi 1:
> Plan9 BCM pin
> GPIO0 17 11
> GPIO1 18 12
> GPIO2 27 13
> GPIO3 22 15
> GPIO4 23 16
> GPIO5 24 18
> GPIO6 25 18
> GPIO7 4 7
> GPIO8 28 24
> GPIO9 29 21
> GPIO10 30 ?
> GPIO11 31 ?
> SDA 2 3
> SCL 3 5
> CE1 7 26
> CE0 8 24
> MISO 9 21
> MOSI 10 19
> SCLK 11 23
> TxD 14 8
> RxD 15 10
>
> and I tried some experiments.
>
> (a) turn led light on/off that is connected to GPIO0 pin
Cool, good to know that part is working for others.
>
> term% echo function out GPIO0 >ctl
> term% echo 1 > GPIO0
> term% echo 0 > GPIO0
> term%
>
> the result is OK.
>
> (b) read GPIO1 status
>
> term% echo function in GPIO1 >ctl
>
> I expected:
> term% cat GPIO1 # low voltage
> 0
> term%
>
> however I have:
> term% cat GPIO1 # low voltage
> 000000...
>
> I expected:
> term% cat GPIO1 # high voltage
> 1
> term%
>
> however I have:
> term% cat GPIO1
> 111111...
>
> is this a feature or bug?
>
This part is inherited and merged in from original 9front source code. As we discussed before there seems to be no manual page. I'm not sure the intended behaviour and I have not yet tried reading from a gpio pin myself.
So in either case on the read it just repeats forever until interrupted?
Chris
next prev parent reply other threads:[~2016-11-07 17:21 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
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 [this message]
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=1A7D8BE0-759A-414D-807B-0C939F60A9F2@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).