Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

gpib(4) [debian man page]

GPIB(4) 						   BSD Kernel Interfaces Manual 						   GPIB(4)

NAME
gpib -- General-Purpose Instrument Bus (GPIB) driver SYNOPSIS
Either of the pcii(4) or tnt4882(4) drivers use this driver as the backend. DESCRIPTION
The gpib driver provides support for driving an IEEE-488 bus, also called IEC-625 (or just "IEC bus"), or HP-IB (Hewlett Packard Instrument Bus), or GPIB (General Purpose Instrument Bus). The device can become either a listener, talker, controller, and in particular a master con- troller on the bus. FILES
/dev/gpibNib Main device node to access the driver. /dev/gpibNl Listen-only entry to the driver. When opening, an instrument can send data to this device on the bus in an unaddressed mode, for example hard-copy printer data. SEE ALSO
gpib(3), pcii(4), tnt4882(4) HISTORY
The gpib driver was written by Poul-Henning Kamp, and first appeared in FreeBSD 5.4. AUTHORS
This manual page was written by Jorg Wunsch. BSD
January 24, 2010 BSD

Check Out this Related Man Page

FIREWIRE(4)						   BSD Kernel Interfaces Manual 					       FIREWIRE(4)

NAME
firewire -- IEEE1394 High-performance Serial Bus SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: device firewire Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): firewire_load="YES" DESCRIPTION
FreeBSD provides machine-independent bus support and raw drivers for firewire interfaces. The firewire driver consists of two layers: the controller and the bus layer. The controller attaches to a physical bus (like pci(4)). The firewire bus attaches to the controller. Additional drivers can be attached to the bus. Up to 63 devices, including the host itself, can be attached to a firewire bus. The root node is dynamically assigned with a PHY device function. Also, the other firewire bus specific parameters, e.g., node ID, cycle master, isochronous resource manager and bus manager, are dynamically assigned, after bus reset is initiated. On the firewire bus, every device is identified by an EUI 64 address. FILES
/dev/fw0.0 /dev/fwmem0.0 SEE ALSO
fwe(4), fwip(4), fwohci(4), pci(4), sbp(4), eui64(5), fwcontrol(8), kldload(8), sysctl(8) HISTORY
The firewire driver first appeared in FreeBSD 5.0. AUTHORS
The firewire driver was written by Katsushi Kobayashi and Hidetoshi Shimokawa for the FreeBSD project. BUGS
See fwohci(4) for security notes. BSD
April 1, 2006 BSD
Man Page