Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

onewire(4) [netbsd man page]

ONEWIRE(4)						   BSD Kernel Interfaces Manual 						ONEWIRE(4)

NAME
onewire -- 1-Wire bus SYNOPSIS
onewire* at gpioow? option ONEWIREVERBOSE DESCRIPTION
1-Wire bus was originally developed by Dallas Semiconductor for connecting integrated circuits. It is commonly used for connecting devices such as electronic keys, EEPROMs, temperature sensors, real-time clocks, security chips, etc. The onewire driver provides a uniform programming interface layer between 1-Wire master controllers and various 1-Wire slave devices. Each 1-Wire master controller attaches a onewire framework; several slave devices can then be attached to the onewire bus. The driver supports plugging and unplugging slave devices on the fly. SUPPORTED MASTERS
gpioow(4) 1-Wire bus bit-banging through GPIO pin SUPPORTED SLAVES
owtemp(4) temperature family type device SEE ALSO
intro(4) HISTORY
The onewire driver first appeared in OpenBSD 4.0 and NetBSD 4.0. AUTHORS
The onewire driver was written by Alexander Yurchenko <grange@openbsd.org> and ported to NetBSD by Jeff Rizzo <riz@NetBSD.org>. BSD
April 4, 2006 BSD

Check Out this Related Man Page

GPIOIIC(4)						   BSD Kernel Interfaces Manual 						GPIOIIC(4)

NAME
gpioiic -- GPIO I2C controller SYNOPSIS
gpioiic* at gpio? offset 0 mask 0x3 flag 0x0 gpioiic* at gpio? iic* at gpioiic? DESCRIPTION
The gpioiic driver allows bit-banging an I2C bus as a master using two GPIO pins. By default the first pin is used as a serial data (SDA) signal and the second as a serial clock (SCL). If the flag locator is set to 0x01, the order of the SDA and SCL signals is reversed. Both GPIO pins must be able to drive an output and the SDA pin must be also able to read an input. The pins can be specified in the kernel configuration with the offset and the mask locators. The offset and mask can also be specified when gpioiic is attached at runtime using the GPIOATTACH ioctl(2) on the gpio(4) device. Each bit in the mask locator defines one pin; the pin number is calculated as an addition of the bit position and the offset locator. For example, offset 17 and mask 0x5 defines pin numbers 17 and 19. SEE ALSO
gpio(4), iic(4), intro(4) HISTORY
The gpioiic driver first appeared in OpenBSD 3.9 and NetBSD 5.0. AUTHORS
The gpioiic driver was written by Alexander Yurchenko <grange@openbsd.org> and was ported to NetBSD by Marc Balmer <marc@msys.ch>. CAVEATS
A gpioiic device can not be detached from the gpio(4) bus at runtime due to the fact that iic(4) busses can not detach once attached. BSD
October 2, 2011 BSD
Man Page

2 More Discussions You Might Find Interesting

1. Programming

Hi...Need Help

Hi, I am getting a bus error when i run the following code. #include <stdio.h> #include <sys/types.h> #include <sys/ipc.h> #include <sys/sem.h> #include <errno.h> main() { int semid,retval; semid=semget(0x20,1,IPC_CREAT|0666); retval= semctl(semid,0,GETVAL,0); printf("The... (1 Reply)
Discussion started by: jack_2205
1 Replies

2. Shell Programming and Scripting

Reading multiple directories and file from them

Hello I'm making script for Dallas temperature sensors (DS1820). When a sensor is connected, it shows up as a directory in /sys/bus/w1/devices in format 10-xxxxxxx. Inside the directory is a file called w1_slave which holds the temperature in format t=xxxxx. Each sensor has unique... (2 Replies)
Discussion started by: Klipeti
2 Replies