On Wed, Oct 07, 2015 at 01:09:58PM +0200, Bo Berglund wrote:
> On Wed, 07 Oct 2015 10:05:03 +0200, Jonas Maebe
> wrote:
> >Bo Berglund wrote on Wed, 07 Oct 2015:
> >
> >> How can one control the GPIO outputs on a Raspberry Pi2 without
> >> needing the program to run as root? I am using Raspbian Wh
Henry Vermaak wrote:
On Wed, Oct 07, 2015 at 01:09:58PM +0200, Bo Berglund wrote:
On Wed, 07 Oct 2015 10:05:03 +0200, Jonas Maebe
wrote:
Bo Berglund wrote on Wed, 07 Oct 2015:
How can one control the GPIO outputs on a Raspberry Pi2 without
needing the program to run as root? I am using Raspb
On Thu, 08 Oct 2015 13:15:10 +, Mark Morgan Lloyd
wrote:
>> You access the GPIOs via the kernel's sysfs interface. The files are
>> all under /sys/class/gpio. I'd be pretty amazed if your distro doesn't
>> already have a udev rule to set a certain group for those files. You
>> probably jus
Bo Berglund wrote:
On Thu, 08 Oct 2015 13:15:10 +, Mark Morgan Lloyd
wrote:
You access the GPIOs via the kernel's sysfs interface. The files are
all under /sys/class/gpio. I'd be pretty amazed if your distro doesn't
already have a udev rule to set a certain group for those files. You
pr
On Thu, 08 Oct 2015 19:48:54 +, Mark Morgan Lloyd
wrote:
>Do not, under any circumstances, try to fiddle with the permission of
>those files/directories. Instead, add the gpio group to your normal user
>(as I have already said).
>
>Jonas has already asked us to discuss this elsewhere, i.e.
Bo Berglund wrote:
On Thu, 08 Oct 2015 19:48:54 +, Mark Morgan Lloyd
wrote:
Do not, under any circumstances, try to fiddle with the permission of
those files/directories. Instead, add the gpio group to your normal user
(as I have already said).
Jonas has already asked us to discuss this
