12-25-2017, 02:14 PM
unfortunately the Pi driver does not have its source available so it will be more of a driver writing project vs a port. The code I linked to was just a package for using with an arduino. The fortunate part is that it does have the communication protocol.
I was more asking for a jumping off point, but I think I am getting there. I have written software using a uart before, but always for a mcu or simple data transfer. From what I have gathered linux actually takes the heavy lifting from the interrupt handler away and we can simply use the scan command which will suspend until the interrupt is thrown and wake the process back up.
I am a bit confused about the differences between each uart on the pine and not sure which one would be best suited. That being said I am miles away from actually connecting the keyboard at the moment.
I am currently working with armbian. Is there anything special that needs to be done to enable a uart on the Pine?
I was more asking for a jumping off point, but I think I am getting there. I have written software using a uart before, but always for a mcu or simple data transfer. From what I have gathered linux actually takes the heavy lifting from the interrupt handler away and we can simply use the scan command which will suspend until the interrupt is thrown and wake the process back up.
I am a bit confused about the differences between each uart on the pine and not sure which one would be best suited. That being said I am miles away from actually connecting the keyboard at the moment.
I am currently working with armbian. Is there anything special that needs to be done to enable a uart on the Pine?