How to get a loadable driver for the alpha RT3572?

I'm running jessie using the

  4.4.77-rockchip-ayufan-136

kernel.

It also has the

  linux-rock64-package

installed which I presume are the build tools.

I have an old alpha RT8187 I borrowed working

I write in nodejs exclusively and on RPI I use this library to control GPIOs
https://github.com/fivdi/pigpio
This module creates bindings to the excellent PIGPIO C library  here https://github.com/joan2937/pigpio
and with it and this i2c bus module https://github.com/fivdi/i2c-bus I can anything on the GPIO bus.

I am sure I can get the PIGPIO C library to compile but will it be compatible with the "Pi2" bus on the Pine64?
If so tada I can use my nodejs code directly from RPI to Pine64 without alteration (well except maybe for some pin number translations as pointed out in other posts????)

If PIGPIO C won't work the same dev has a library that uses EPOLL.
So the EPOLL C should compile but will it work with the PINE64 pi2 bus???
https://github.com/fivdi/epoll

I'd much rather use PIGPIO C library as I have discovered it's much more robust than the EPOLL

What are my options here? 
I understand I can just write sysfs calls directly in nodejs but I've discovered that's not very robust.
One thing I definitely do frequently on the Pi is use pins as interrupts and that is easy with PIGPIO or EPOLL.  As far as I understand if only using sysfs then you have to manually poll the pin state in your code continuously (in nodejs that would be setInterval) looking for a state change (which is really not robust at all).

Can I have the number of the sender, please? I am in China now, and I want to contact the sender, because the official website does not support sending it to China.

I just got my board yesterday and noticed that it can with two large power resistors. Looking at the schematic they would be R373 and R351. They look to be that they would provide a load to the ATX connector/power supply. Is this correct? I'm in using the the barrel connector so I wouldn't need them? Is there any hard soldering them in place even if I don't use an ATX power supply? It doesn't look like it from the schematic.

Thanks for any in-site I'm hoping to get mine fired up with 2 sopines over lunch.

I made an overview of the GPIO header for the nodes while playing with my Clusterboard prototype, maybe it helps others working on this...

   

Maybe someone can verify this against the schematics again...

I have rev 2.2 of the clusterboard and am having a ton of issues. The only image I have been able to get to bring network up is ayafun's xenial minimal, archlinux, armbian and others won't bring network up, but will boot. 

Anyone work through these issues?

Hi,

Having booted a number of different OS on my board - sometimes successfully, sometimes not - I have a tip I want to give to improve chances of your chosen OS booting first time:

*ON FIRST BOOT ENSURE THERE IS NOTHING PLUGGED INTO THE USB PORTS*

This should remove any chance of black screen of death, failure to boot etc. after it had bouted to desktop you can then plug in your USB peripherals. 

Hope that helps some folk!

Hello,

I've noticed that PINE64 plan to provide in a couple of month a board based on the rock chip RK3399. Could you post the pins assignment of the 40 pins connector? I'm particularly interested by I2S0 interface signals (ideally I2S0-SDI0, I2S0-SDO0..3, and clocks), I2C and/or SPI.

Thx

Hi,

I’m using Android 7.1 and have Kodi installed. I also have a linu tv box and have been struggling to get the PVR Add on (VU+) to work. 

I have configured it with my linux box ip etc. but the add on is refusing to start up - I get an error on Kodi launch saying ‘system error - unable to load PVR Manager’  

Anyone got their Linux TV box working with Kodi on Pine 64?

Now you can access PINE H64 page from PINE64 wiki main page.

- released Pine H64 port assignment document

- released Pine H64 schematic

- the Android build original plan to release on this week but got postpone by Chinese New Year. The new schedule release data is February 23.

- the mainline headless Linux build already up and running, thanks to icenowy and xalius