From: roystonvasey <mik...@ma...> - 2009-11-26 03:00:53
|
Dear List, I want to allow some of the GPIO on a custom board to be accessible by user applications. I have a modified board.c file which sets all the IO up as required. One of my applications manipulates the GPIO based on user interactions. If the application is run as root all is fine but when run as a normal user i'm catching 'permission denied' errors when trying to write to the IO. Is there a way of setting up access rights when the GPIO is created or the sysfs is created? Cheers Mike. -- View this message in context: http://old.nabble.com/GPIO-permissions-tp26523649p26523649.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dave H. <dhy...@gm...> - 2009-11-26 05:24:32
|
Hi Mike, On Wed, Nov 25, 2009 at 6:46 PM, roystonvasey <mik...@ma...> wrote: > > Dear List, > I want to allow some of the GPIO on a custom board to be accessible by user > applications. > I have a modified board.c file which sets all the IO up as required. > One of my applications manipulates the GPIO based on user interactions. > If the application is run as root all is fine but when run as a normal user > i'm catching 'permission denied' errors when trying to write to the IO. > Is there a way of setting up access rights when the GPIO is created or the > sysfs is created? I don't think so. You could use a gpio driver like the one I posted: <http://thread.gmane.org/gmane.linux.distributions.gumstix.general/46930/focus=46938> -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |