GPIO pin naming

[ohanssen]

When setting up GPIO for PTT Direwolf expects a number. This doesn't work on the Cubieboard where gpio pins are named differently. E.g. GPIO pin 61 is mapped to the device name gpio61_pi13 instead of just gpio61. To activate a pin, one still use just the number. E.g. "echo 61 > /sys/class/gpio/export".

Is it possible to support these boards by configuring using a name instead of just a number, or is there a workaround?

[wb2osz]

This might have been fixed by 58c2707 on the 'dev' branch but I don't have a CubieBoard to verify. See comments in ptt.c for details.
Would someone like to test this and report the results?
Just use the pin number like 61. If the device name like gpio61 is not found, it will look for something like gpio61_*

[wb2osz]

This should be fixed in the “dev” branch. I don’t have a CubieBoard to test it. Can you verify? Thanks. From: LA7ECA, Øyvind Hanssen [mailto:notifications@github.com] Sent: Tuesday, September 29, 2015 4:39 PM To: wb2osz/direwolf Subject: [direwolf] GPIO pin naming (#4) When setting up GPIO for PTT Direwolf expects a number. This doesn't work on the Cubieboard where gpio pins are named differently. E.g. GPIO pin 61 is mapped to the device name gpio61_pi13 instead of just gpio61. To activate a pin, one still use just the number. E.g. "echo 61 > /sys/class/gpio/export". Is it possible to support these boards by configuring using a name instead of just a number, or is there a workaround? — Reply to this email directly or view it on GitHub <#4> . <https://github.com/notifications/beacon/AGMul2niVQGfusTaUbJpXV9kSXgt0oa3ks5o2u5WgaJpZM4GGBtR.gif>

[wb2osz]

This should be fixed in the most recent version. (1.4)

I don’t have a CubieBoard to test it.

Can you verify?

Thanks.