3ab4ce4739
driver, gpiolock(4), is provided as an example how to interface real hardware. A new securemodel, securemodel_keylock, is provided to show how this can be used to tie keylocks to overall system security. This is experimental code. The diff has been on tech-kern for several weeks. Reviewed by many, kauth(9) integration reviewed by Elad Efrat; approved by tonnerre@ and tron@. Thanks to everyone who provided feedback.
27 lines
602 B
Plaintext
27 lines
602 B
Plaintext
# $NetBSD: files.gpio,v 1.8 2009/08/14 21:17:22 mbalmer Exp $
|
|
|
|
define gpio {[offset = -1], [mask = 0]}
|
|
|
|
device gpio: gpio
|
|
attach gpio at gpiobus
|
|
file dev/gpio/gpio.c gpio needs-flag
|
|
|
|
# GPIO simulator
|
|
defpseudodev gpiosim: gpiobus
|
|
file dev/gpio/gpiosim.c gpiosim
|
|
|
|
# I2C bus bit-banging
|
|
device gpioiic: i2cbus, i2c_bitbang
|
|
attach gpioiic at gpio
|
|
file dev/gpio/gpioiic.c gpioiic
|
|
|
|
# 1-Wire bus bit-banging
|
|
device gpioow: onewirebus, onewire_bitbang
|
|
attach gpioow at gpio
|
|
file dev/gpio/gpioow.c gpioow
|
|
|
|
# Keylock
|
|
device gpiolock: gpiobus
|
|
attach gpiolock at gpio
|
|
file dev/gpio/gpiolock.c gpiolock
|