wireguard-openbsd - WireGuard implementation for the OpenBSD kernel

	Commit message (Collapse)	Author	Age	Files	Lines
*	Add a 'flag' locator to gpioiic(4), and define a first flag	matthieu	2011-10-03	1	-1/+2
\| \| \| \| \| \|	value to swap the SDA and SCL pins assigment during attach. Mostly from work with mbalmer@NetBSD. ok miod@
*	Change the semantics of gpio(4) devices by locking down pin	mbalmer	2008-11-26	1	-1/+7
\| \| \| \| \| \| \| \| \| \| \|	configuration and device attachment/detachment to securelevel 0. GPIO pins can now only be configured at securelevel 0. Once the securelevel is raised, only pins that have been configured and set for securelevel access using the GPIOPINSET ioctl are accessible. This also adds the possibility to give GPIO pins a name. ok uwe@
*	- Add two new ioctls to gpio(4), GPIOATTACH and GPIODETACH, to allow to attach	mbalmer	2008-11-24	1	-1/+7
\| \| \| \| \| \| \| \| \| \| \| \|	and detach devices on a gpiobus at runtime. The offset and mask locators in kernel config files can still be used for static configuration, so this does not break existing custome kernel configs. - Have gpioow(4) unmap the pins it used from the gpiobus during detach Changes to gpioctl(8) will be a separate committ. ok uwe
*	Add gpio_pin_caps() method to provide pin capabilities.	grange	2006-01-14	1	-1/+2
\|
*	Finish framework for attaching kernel drivers to the GPIO pins.	grange	2006-01-05	1	-5/+21
\| \| \| \|	Not used yet.
*	A framework for supporting various General Purpose Input/Output (GPIO)	grange	2004-06-03	1	-0/+63
	devices. Such devices provide a set of pins that you can use to connect for example leds to it. The pins can be accessed either from userland through the /dev/gpio* device files or from the kernel drivers. The latter is necessary for implementing timing-sensitive things like i2c or 1-wire master controller. ok deraadt@