History log of /openbsd-src/usr.sbin/gpioctl/gpioctl.c (Results 1 – 17 of 17)
Revision Date Author Comments
# 8978cb65 26-Dec-2015 mmcc <mmcc@openbsd.org>

bzero -> memset. No binary change.

ok tb@


# 3af2d23d 04-Oct-2011 jmc <jmc@openbsd.org>

- sync usage() and SYNOPSIS
- document "flag", for I2C devices
- "pin" is not optional

ok matthieu


# 7d434456 03-Oct-2011 matthieu <matthieu@openbsd.org>

Add a 'flag' locator to gpioiic(4), and define a first flag
value to swap the SDA and SCL pins assigment during attach.
Mostly from work with mbalmer@NetBSD.
ok miod@


# ff634cd4 03-Dec-2008 stevesk <stevesk@openbsd.org>

delete unused prototype, from lint; ok mbalmer@


# 89a69f69 30-Nov-2008 mbalmer <mbalmer@openbsd.org>

Fix output.


# 29712188 29-Nov-2008 mbalmer <mbalmer@openbsd.org>

Allow the words "on", "off", or "toggle" to be used instead of the
numerical values when writing to a pin; fix an error message.


# b4828597 26-Nov-2008 mbalmer <mbalmer@openbsd.org>

Reorder variables, add my copyright.


# 2e6ed72b 26-Nov-2008 mbalmer <mbalmer@openbsd.org>

Use the new gpio(4) semantics and change the command line syntax to a
more readable and straightforward format. Note that there is no longer
a default GPIO device, but it has to be sepcified on the

Use the new gpio(4) semantics and change the command line syntax to a
more readable and straightforward format. Note that there is no longer
a default GPIO device, but it has to be sepcified on the command line
always (and as Theo mentioned, newfs also does not default to /dev/sd0a...)

You must do a 'make includesi' in /usr/src before building this command or
before your next system build.

ok uwe@

show more ...


# 212d975f 24-Nov-2008 jmc <jmc@openbsd.org>

- tweak previous
- kill .Tn


# b9a1499c 24-Nov-2008 mbalmer <mbalmer@openbsd.org>

Add and document -A and -D options to attach or detach devices at
runtime to a gpio bus.

ok uwe, drahn


# c6dcffec 17-Nov-2007 mbalmer <mbalmer@openbsd.org>

GPIO pins can be programmed to invert input or output on some devices.
Introduce new flags, GPIO_PIN_INVIN and GPIO_PIN_INVOUT, for this.

ok grange


# 017db7a3 17-Nov-2007 mbalmer <mbalmer@openbsd.org>

pull-down (GPIO_PIN_PULLDOWN) is a valid flags for some GPIO devices,
e.g. the AMD Geode C5536 GPIO.

ok grange


# edf9ea1a 18-Mar-2007 deraadt <deraadt@openbsd.org>

use strtonum() to avoid out of range values, way simpler than the
12-line song and dance that standard functions need; bret.lambert@gmail


# 5bcb752f 17-Nov-2005 grange <grange@openbsd.org>

Unbreak; noticed by evol@online.ptt.ru.


# 2a642902 16-Nov-2005 deraadt <deraadt@openbsd.org>

no need for -h, any illegal option is fine


# 210ae517 08-Aug-2004 deraadt <deraadt@openbsd.org>

spacing


# 48e05255 03-Jun-2004 grange <grange@openbsd.org>

gpioctl -- program to control GPIO devices.
The gpioctl program allows to manipulate GPIO devices pins

Quick start for the Soekris net4801 users:
# gpioctl -c 20 out pp
# gpioctl 20 1
This will turn

gpioctl -- program to control GPIO devices.
The gpioctl program allows to manipulate GPIO devices pins

Quick start for the Soekris net4801 users:
# gpioctl -c 20 out pp
# gpioctl 20 1
This will turn on the red error led.
If you want to use JP5 I/O pins, just use the /dev/gpio1 device.

Quick start for the PC Engines WRAP.1C users:
# gpioctl 40
This will read the state of the button (0 means pressed).

# gpioctl -c 2 pp out
This will turn the first led on, to turn off write 1 to the pin,
it's reversed. For the second and the third leds use pins 3 and 18.

ok deraadt@

show more ...