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 ioctl interface, where a data pin needs to > switch directions between in and out. Which is where > I'm stuck ATM.
Do you know about gpioow(4) and onewire(4) ? Sure writing kernel drivers for simple one-wire device is a bit of overkill but it's a > > > Nothing prevents you to run permanently at securelevel 0 if you > > need it and can afford the risk. > > so i tried setting securelevel=0 in /etc/rc.securelevel, but(!) ... you need to set 'option INSECURE' in your kernel config for permanent insecure mode. > > [... boot stuff ...] > setting tty flags > pf enabled > starting network > starting early daemons: syslogd pflogd. > starting RPC daemons:. > savecore: no core dump > checking quotas: done. > clearing /tmp > starting pre-securelevel daemons:pin 29: caps: in out pu pd, flags: -> out > checking kern.securelevel: kern.securelevel=0 > . > setting kernel security level: kern.securelevel: 0 -> 0 > creating runtime link editor directory cache. > preserving editor files. > starting network daemons: sshd sendmail sndiod. > starting local daemons: cron. > Sun Jun 29 19:16:46 PDT 2014 > > OpenBSD/armv7 (bone.local) (console) > [ ... login and Welcome message ... ] > > bone $ sysctl kern.securelevel > kern.securelevel=1 > -- Matthieu Herrb
