#
471aeecf |
| 06-Apr-2022 |
naddy <naddy@openbsd.org> |
constify struct cfattach
|
#
0b1c7607 |
| 03-Jul-2011 |
matthew <matthew@openbsd.org> |
Remove config_activate() and DVACT_ACTIVATE. PCMCIA's the only thing that's ever used it, and it's long since been changed to use DVACT_{QUIESCE,SUSPEND,RESUME} instead.
ok deraadt@, dlg@; miod@ al
Remove config_activate() and DVACT_ACTIVATE. PCMCIA's the only thing that's ever used it, and it's long since been changed to use DVACT_{QUIESCE,SUSPEND,RESUME} instead.
ok deraadt@, dlg@; miod@ also agreed with this idea when I brought it up a few weeks ago
show more ...
|
#
e78728c7 |
| 13-Oct-2009 |
pirofti <pirofti@openbsd.org> |
Get rid of devact enum, substitute it with an int and coresponding defines.
This is needed for the addition of further suspend/resume actions.
Okay deraadt@, marco@.
|
#
fca40c6a |
| 24-Nov-2008 |
mbalmer <mbalmer@openbsd.org> |
- Add two new ioctls to gpio(4), GPIOATTACH and GPIODETACH, to allow to attach and detach devices on a gpiobus at runtime. The offset and mask locators in kernel config files can still be used for s
- Add two new ioctls to gpio(4), GPIOATTACH and GPIODETACH, to allow to attach 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
show more ...
|
#
07aaebcc |
| 23-Jun-2006 |
miod <miod@openbsd.org> |
In a drivers activate() entry point, if on DVACT_DEACTIVATE it does something, then it MUST return zero on DVACT_ACTIVATE, not EOPNOTSUPP; this very popular bug has been cut and pasted a lot of times
In a drivers activate() entry point, if on DVACT_DEACTIVATE it does something, then it MUST return zero on DVACT_ACTIVATE, not EOPNOTSUPP; this very popular bug has been cut and pasted a lot of times... ok deraadt@ mickey@
show more ...
|
#
f8c248a6 |
| 04-Mar-2006 |
grange <grange@openbsd.org> |
Dallas 1-Wire bus support. Includes the following drivers:
gpioow(4) 1-Wire bus bit-banging through GPIO pin onewire(4) 1-Wire bus driver owid(4) 1-Wire ID family type device owtemp(4) 1-Wire tempe
Dallas 1-Wire bus support. Includes the following drivers:
gpioow(4) 1-Wire bus bit-banging through GPIO pin onewire(4) 1-Wire bus driver owid(4) 1-Wire ID family type device owtemp(4) 1-Wire temperature family type device
Drivers for RS-232 and USB bus masters will follow.
ok deraadt@
show more ...
|