On Thu, Apr 27, 2017 at 4:27 PM, Metelko <[email protected]> wrote: > I used the following udev rule (similar to William Hermans, without the > pinmux/state changes using a new 'gpio' group). > > udev rule: > SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c 'chown -R root:gpio /sys/class/gpio; > chmod -R 770 /sys/class/gpio; chown -R root:gpio > /sys/devices/platform/ocp/4????000.gpio/gpio/; chmod -R 770 > /sys/devices/platform/ocp/4????000.gpio/gpio/'" > > This worked successfully for an image that had the following setup (uname): > Linux bbb-3ed2 4.4.12-ti-rt-r30 #1 SMP PREEMPT RT Thu Jun 9 07:50:04 UTC > 2016 armv7l armv7l armv7l GNU/Linux > > I am now moving to a newer image (uname): Linux bbb-f652 4.9.24-ti-rt-r31 > #1 SMP PREEMPT RT Wed Apr 26 23:38:10 UTC 2017 armv7l armv7l armv7l > GNU/Linux. I see the /sys/class/gpio directory setup with the 'gpio' group > name. But when I export a pin and look at that directory, the ownership of > all the files are root:root. This will not allow me to control the GPIO > from a non-root account. Any idea on what might have changed that would > effect this would be greatly appreciated.
Here's my latest gpio udev rule that i'm pushing thru apt (bb-customizations) package: https://github.com/rcn-ee/repos/blob/master/bb-customizations/suite/jessie/debian/80-gpio-noroot.rules Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYiBjbmZgZ4BdPc%2BYX1r7jvR2KmGcX%2BpeBiHGhtRDYT%3Duw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
