Re: gpioctl on beaglebone black

2014-07-01 Thread patrick keshishian
On 6/30/14, Matthieu Herrb wrote: > On Mon, Jun 30, 2014 at 06:04:11PM -0700, patrick keshishian wrote: >> This prevents one to write a simple one-wire protocol >> using the gpio ioctl interface, where a data pin needs to >> switch directions between in and out. Which is where >> I'm stuck ATM. >

Re: gpioctl on beaglebone black

2014-06-30 Thread Matthieu Herrb
On Mon, Jun 30, 2014 at 06:04:11PM -0700, patrick keshishian wrote: > Hi, yea, more on this > > Your argument about not knowing all the pins on all the > different platforms, etc. I can see the point there, but(!) ... > > This prevents one to write a simple one-wire protocol > using the gpio

Re: gpioctl on beaglebone black

2014-06-30 Thread patrick keshishian
Hi, yea, more on this On 6/29/14, Matthieu Herrb wrote: > On Sun, Jun 29, 2014 at 12:31:16AM -0700, patrick keshishian wrote: >> On 6/29/14, Benjamin Baier wrote: >> > You can set the default securelevel in /etc/rc.securelevel. >> > The "logic behind that" is described in securelevel(7). >>

Re: gpioctl on beaglebone black

2014-06-29 Thread patrick keshishian
On 6/29/14, Matthieu Herrb wrote: > On Sun, Jun 29, 2014 at 12:31:16AM -0700, patrick keshishian wrote: >> On 6/29/14, Benjamin Baier wrote: >> > You can set the default securelevel in /etc/rc.securelevel. >> > The "logic behind that" is described in securelevel(7). >> >> locking down pins when/i

Re: gpioctl on beaglebone black

2014-06-29 Thread Matthieu Herrb
On Sun, Jun 29, 2014 at 12:31:16AM -0700, patrick keshishian wrote: > On 6/29/14, Benjamin Baier wrote: > > You can set the default securelevel in /etc/rc.securelevel. > > The "logic behind that" is described in securelevel(7). > > locking down pins when/if another device driver is attached > to

Re: gpioctl on beaglebone black

2014-06-29 Thread patrick keshishian
On 6/29/14, Benjamin Baier wrote: > You can set the default securelevel in /etc/rc.securelevel. > The "logic behind that" is described in securelevel(7). locking down pins when/if another device driver is attached to them makes sense, but locking down idle pins ... i'm not too sure. especially si

Re: gpioctl on beaglebone black

2014-06-29 Thread Benjamin Baier
You can set the default securelevel in /etc/rc.securelevel. The "logic behind that" is described in securelevel(7). On 06/29/14 06:18, patrick keshishian wrote: On 6/27/14, Raphael Graf wrote: On 06/27/14 06:58, patrick keshishian wrote: The direction of the pin has to be configured at secure

Re: gpioctl on beaglebone black

2014-06-28 Thread patrick keshishian
On 6/27/14, Raphael Graf wrote: > On 06/27/14 06:58, patrick keshishian wrote: > > The direction of the pin has to be configured at securelevel 0. > You can put something like the following line in /etc/rc.securelevel: > gpioctl gpio1 23 set out > > Then you should be able to toggle the pin: > # g

Re: gpioctl on beaglebone black

2014-06-27 Thread Raphael Graf
On 06/27/14 06:58, patrick keshishian wrote: Hello, I'm trying to play with the GPIO on bbb. I must be misunderstanding how this is supposed to (expected) to work. I've been looking through the gpioctl (gpio) manuals, but i'm still confused, and could use a pointer. here is a demo: # gpioctl

gpioctl on beaglebone black

2014-06-26 Thread patrick keshishian
Hello, I'm trying to play with the GPIO on bbb. I must be misunderstanding how this is supposed to (expected) to work. I've been looking through the gpioctl (gpio) manuals, but i'm still confused, and could use a pointer. here is a demo: # gpioctl gpio1 7 pin 7: state 1 # gpioctl gpio1 7 off p