From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Date: Fri, 16 May 2014 15:33:27 -0500 Message-ID: From: Sean Hinchee To: 9fans@9fans.net Content-Type: multipart/alternative; boundary=20cf303ea3866b8ea104f98a53c7 Subject: [9fans] plan9-bcm GPIO control raspberry pi Topicbox-Message-UUID: e6e25942-ead8-11e9-9d60-3106f5b1d025 --20cf303ea3866b8ea104f98a53c7 Content-Type: text/plain; charset=UTF-8 So I ran across this ( https://github.com/elewarr/plan9-bcm ) awhile back and decided it would be fun to try to stick it on my pi running 9front. Problem is I'm either too new to this, or am missing something really basic when I'm trying to compile the kernel. Normally iirc one just has to run "mk install" and things tend to come together, but I'm getting an error "No recipe to make 'fpi.5' in director /sys/src/9/9-bcm" I realize that the 5 corresponds to the ARM arch and I assume it is supposed to be made automatically, I'm not sure if tehre's some documentation somewhere on this I missed or if I should just dig through the source to find out what it is/should be. Thoughts? --20cf303ea3866b8ea104f98a53c7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
So I ran across this ( https://github.com/elewarr/plan9-bcm ) awhile back and decided it would be fun to try to stick it on my pi run= ning 9front. Problem is I'm either too new to this, or am missing somet= hing really basic when I'm trying to compile the kernel. Normally iirc = one just has to run "mk install" and things tend to come together= , but I'm getting an error "No recipe to make 'fpi.5' in d= irector /sys/src/9/9-bcm"

I realize that the 5 corresponds to the A= RM arch and I assume it is supposed to be made automatically, I'm not s= ure if tehre's some documentation somewhere on this I missed or if I sh= ould just dig through the source to find out what it is/should be.

Thoughts?


--20cf303ea3866b8ea104f98a53c7-- From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Fri, 16 May 2014 22:40:30 +0200 From: cinap_lenrek@felloff.net To: 9fans@9fans.net In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] plan9-bcm GPIO control raspberry pi Topicbox-Message-UUID: e6e608da-ead8-11e9-9d60-3106f5b1d025 just did a mk in /sys/src/9/bcm and it builds just fine. what is "/sys/src/9/9-bcm"? -- cinap From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Fri, 16 May 2014 13:46:25 -0700 Message-ID: From: Skip Tavakkolian To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=047d7bb04814cf7f1304f98a8188 Subject: Re: [9fans] plan9-bcm GPIO control raspberry pi Topicbox-Message-UUID: e6f510dc-ead8-11e9-9d60-3106f5b1d025 --047d7bb04814cf7f1304f98a8188 Content-Type: text/plain; charset=UTF-8 i'm guessing that plan9-bcm source directory should be bound -- bind(1) -- to /sys/src/9/9-bcm (or even /sys/src/9/bcm). On Fri, May 16, 2014 at 1:33 PM, Sean Hinchee wrote: > So I ran across this ( https://github.com/elewarr/plan9-bcm ) awhile back > and decided it would be fun to try to stick it on my pi running 9front. > Problem is I'm either too new to this, or am missing something really basic > when I'm trying to compile the kernel. Normally iirc one just has to run > "mk install" and things tend to come together, but I'm getting an error "No > recipe to make 'fpi.5' in director /sys/src/9/9-bcm" > > I realize that the 5 corresponds to the ARM arch and I assume it is > supposed to be made automatically, I'm not sure if tehre's some > documentation somewhere on this I missed or if I should just dig through > the source to find out what it is/should be. > > Thoughts? > > > --047d7bb04814cf7f1304f98a8188 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
i'm guessing that plan9-bcm source directory should be= bound -- bind(1) -- to /sys/src/9/9-bcm (or even /sys/src/9/bcm).

=


O= n Fri, May 16, 2014 at 1:33 PM, Sean Hinchee <henesy.dev@gmail.com= > wrote:
So I ran across this (= h= ttps://github.com/elewarr/plan9-bcm ) awhile back and decided it would = be fun to try to stick it on my pi running 9front. Problem is I'm eithe= r too new to this, or am missing something really basic when I'm trying= to compile the kernel. Normally iirc one just has to run "mk install&= quot; and things tend to come together, but I'm getting an error "= No recipe to make 'fpi.5' in director /sys/src/9/9-bcm"

I realize that the 5 corresponds to the ARM arch and= I assume it is supposed to be made automatically, I'm not sure if tehr= e's some documentation somewhere on this I missed or if I should just d= ig through the source to find out what it is/should be.

Thoughts?



--047d7bb04814cf7f1304f98a8188-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Fri, 16 May 2014 22:12:59 -0500 Message-ID: From: Sean Hinchee To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=047d7b3a9c0e4a7df404f98fe8a8 Subject: Re: [9fans] plan9-bcm GPIO control raspberry pi Topicbox-Message-UUID: e6f94f1c-ead8-11e9-9d60-3106f5b1d025 --047d7b3a9c0e4a7df404f98fe8a8 Content-Type: text/plain; charset=UTF-8 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? --047d7b3a9c0e4a7df404f98fe8a8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Ok, it ran when bound to /sys/src/9/bcm. Flawless suc= cess. @cinap_lenrek, the folder was the source for the bcm kernel thing I l= inked above, it's built to support GPIO afaik, I'd like to play wit= h GPIO whilst I learn plan9 on this pi.

If I may ask, what is the reason that it ran when bound to bcm, p= ermissions or something?
--047d7b3a9c0e4a7df404f98fe8a8--