On 01/04/2017 04:09 AM, Peter Robinson wrote:
I do understand that to debug my configuration I would need to collect
more data.
My question was more about current user's experiences. Does interaction
with GPIO is expected to work.
Which is needed step before jumping into problem solving. If GPIO is
not expected to work yet, then debugging case is pointless.
I'm not aware of any reason it shouldn't. I don't have direct access
to a working RPi ATM but the lsgpio tool (built in the 4.9
kernel-tools package) gave me a list of GPIOs the last time I tested
it, I've not had time to dig deeper although it's on my todo list.
A potential problem with the various gpio packages designed specifically
for the Pi, is that they tend not to use the standard kernel sysfs
interface for accessing gpios.
They think that is too slow, and access hardware registers directly by
mmap'ing /dev/mem (or the the non-standard /dev/gpiomem)
The memory range used differs by model, so they either use information
in the device-tree or /proc/cpuinfo to detect that.
And I recall the physical pin to gpio number mapping also differs by
model/revision, so even packages that do use the standard sysfs
interface may look at cpuinfo, and could be confused by the Fedora
kernel reporting BCM2835 for a Pi 2
Yours sincerely,
Floris Bos
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
