From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <275c3465707d98d4c1f88f81b40670fd@quintile.net> <20140508183622.E368BB827@mail.bitblocks.com> Date: Fri, 9 May 2014 08:43:57 -0700 Message-ID: From: Skip Tavakkolian To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=089e0115ec143f2bbf04f8f977f9 Subject: Re: [9fans] radio Topicbox-Message-UUID: e4d83f86-ead8-11e9-9d60-3106f5b1d025 --089e0115ec143f2bbf04f8f977f9 Content-Type: text/plain; charset=UTF-8 FYI, another item on my todo list is porting the RF24 library to plan9-bcm. i use nrf24l01+ devices between arduinos and a pi (in Go on linux) for temp/humidity telemetry. the device uses the SPI interface. on a somewhat related note, is anyone building support for Go on Plan 9/ARM? On Fri, May 9, 2014 at 7:11 AM, Krystian Lewandowski wrote: > I was working on GPIO under Plan9 - very simple thing but also supports > edge-raising/falling events. I had simple C code to print what pin > triggered an event. I'll try to push this simple test to github during > weekend. Though i'm not sure how it can be integrated - is events counting > enough? > > Krystian > https://github.com/elewarr/plan9-bcm > > 2014-05-08 20:36 GMT+02:00 Bakul Shah : > > On Thu, 08 May 2014 18:58:31 BST "Steve Simon" wrote: >> > I have a hifiberry (http://www.hifiberry.com/) nicely minimalist, >> > though no driver at present - I will await the GSOC project :-) >> >> > I have some itron VFDs from work, 256 x 64 pixel. I like these as >> > the visibility is excellent. The only annoyance is they have >> > a parallel interface and I use up all the PI's GPIOs. >> >> > I also need to interface a rotary encoder for the tuning knob which >> > is also a pain - not complex enough to justify an FPGA, but a bit too >> > much to poll when the PI is doing audio decode as well. >> >> No need for polling. The BCM2835 can handle edge triggered >> interrupts. Or you can use a PAL or CPLD. >> >> > Thinking of adding a PIC or an AVR just for the encoder / VFD interface >> > and talking i2c to it. >> >> > --089e0115ec143f2bbf04f8f977f9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
FYI, another item on my todo list is porting the RF24 libr= ary to plan9-bcm. i use nrf24l01+ devices between arduinos and a pi (in Go = on linux) for temp/humidity telemetry. =C2=A0the device uses the SPI interf= ace.

on a somewhat related note, is anyone building support for G= o on Plan 9/ARM?


<= br>
On Fri, May 9, 2014 at 7:11 AM, Krystian Lewa= ndowski <krystian.lew@gmail.com> wrote:
I was working on GPIO under= Plan9 - very simple thing but also supports edge-raising/falling events. I= had simple C code to print what pin triggered an event. I'll try to pu= sh this simple test to github during weekend. Though i'm not sure how i= t can be integrated - is events=C2=A0counting enough?

Krystian

2014-05-08 20:36 GMT+02:00 Bakul Shah = <bakul@bitblocks.com>:

On Thu, 08 May 2014 18:58:31 BST "Steve Simon&qu= ot; <steve@quint= ile.net> wrote:
> I have a hifiberry (http://www.hifiberry.com/) nicely minimalist,
> though no driver at present - I will await the GSOC project :-)

> I have some itron VFDs from work, 256 x 64 pixel. I like these as
> the visibility is excellent. The only annoyance is they have
> a parallel interface and I use up all the PI's GPIOs.

> I also need to interface a rotary encoder for the tuning knob which > is also a pain - not complex enough to justify an FPGA, but a bit too<= br> > much to poll when the PI is doing audio decode as well.

No need for polling. =C2=A0The BCM2835 can handle edge triggered
interrupts. =C2=A0Or you can use a PAL or CPLD.

> Thinking of adding a PIC or an AVR just for the encoder / VFD interfac= e
> and talking i2c to it.



--089e0115ec143f2bbf04f8f977f9--