Alec Leamas

hm... After some digging, it seems like one main problem, perhaps the only one, is the lack of gpio line naming. gpiolib is centered around the idea that lines are referenced using names rather than numbers. However, when listing the names they are all empty i. e. "". This makes it impossible to reference any line. This is obviously about boot/dtb. Moreover, while orangepi 5 successfully reuses the rockchip stuff, the actual names are board specific. I have never worked with the dtb/dts stuff. But assigning names to the connections should not be that complicated. Actually, names like "gpio0", "gpio1" etc reflecting physical lines should be fine. Any hint out there where to start?

I have also encountered this using Orange pi 5 and latest Armbian updated as of today. That the "standing" USB port does not work also means that the USB-C port doesn't work -- they are electrically connected. So Mitu's question is also mine: Is this a limitation of the mainstream kernel (6.18.x) - i.e. does this work only with the vendor kernel (6.1.x)? EDIT: typo

Has anyone found a working gpiolib implementation for Armbian on Orange Pi 5? I'm aware of wiringPi and it sort of works. However, being able to use the "real stuff" so to speak would make my life easier.