*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->FreeBSD man pages -> iicbus (4)              



NAME    [Toc]    [Back]

     iicbus -- I2C bus system

SYNOPSIS    [Toc]    [Back]

     device iicbus
     device iicbb

     device iic
     device ic
     device iicsmb

DESCRIPTION    [Toc]    [Back]

     The iicbus system provides a uniform, modular and architecture-independent
 system for the implementation of drivers to control various I2C
     devices and to utilize different I2C controllers.

I2C    [Toc]    [Back]

     I2C is an acronym for Inter Integrated Circuit bus.  The I2C bus was
     developed in the early 1980's by Philips semiconductors.  It's purpose
     was to provide an easy way to connect a CPU to peripheral chips in a TVset.

     The BUS physically consists of 2 active wires and a ground connection.
     The active wires, SDA and SCL, are both bidirectional.  Where SDA is the
     Serial DAta line and SCL is the Serial CLock line.

     Every component hooked up to the bus has its own unique address whether
     it is a CPU, LCD driver, memory, or complex function chip.  Each of these
     chips can act as a receiver and/or transmitter depending on its functionality.
  Obviously an LCD driver is only a receiver, while a memory or I/O
     chip can both be transmitter and receiver.  Furthermore there may be one
     or more BUS MASTERs.

     The BUS MASTER is the chip issuing the commands on the BUS.  In the I2C
     protocol specification it is stated that the IC that initiates a data
     transfer on the bus is considered the BUS MASTER.	At that time all the
     others are regarded to as the BUS SLAVEs.	As mentioned before, the IC
     bus is a Multi-MASTER BUS.  This means that more than one IC capable of
     initiating data transfer can be connected to it.

DEVICES    [Toc]    [Back]

     Some I2C device drivers are available:

     Devices	       Description
     iic	       general i/o operation
     ic 	       network IP interface
     iicsmb	       I2C to SMB software bridge

INTERFACES    [Toc]    [Back]

     The I2C protocol may be implemented by hardware or software.  Software
     interfaces rely on very simple hardware, usually two lines twiddled by 2
     registers.  Hardware interfaces are more intelligent and receive 8-bit
     characters they write to the bus according to the I2C protocol.

     I2C interfaces may act on the bus as slave devices, allowing spontaneous
     bidirectional communications, thanks to the multi-master capabilities of
     the I2C protocol.

     Some I2C interfaces are available:

     Interface		  Description
     pcf		  Philips PCF8584 master/slave interface
     iicbb		  generic bit-banging master-only driver
     lpbb		  parallel port specific bit-banging interface
     bktr		  Brooktree848 video chipset, hardware and software
			  master-only interface

SEE ALSO    [Toc]    [Back]

     iicbb(4), lpbb(4), pcf(4)

HISTORY    [Toc]    [Back]

     The iicbus manual page first appeared in FreeBSD 3.0.

AUTHORS    [Toc]    [Back]

     This manual page was written by Nicolas Souchu.

FreeBSD 5.2.1			August 6, 1998			 FreeBSD 5.2.1
[ Back ]
 Similar pages
Name OS Title
msgmni HP-UX maximum number of system-wide System V IPC message queues (IDs) allowed
sizer Tru64 Displays information about the system or kernel, or creates a system configuration file
dxsysinfo Tru64 Monitors system information such as CPU activity, memory, swap space, and file system usage
endprdfent HP-UX manipulate system default database entry for a trusted system
shmmni HP-UX number of System V shared memory segment identifiers in the system
getprdfnam HP-UX manipulate system default database entry for a trusted system
getprdfent HP-UX manipulate system default database entry for a trusted system
putprdfnam HP-UX manipulate system default database entry for a trusted system
setprdfent HP-UX manipulate system default database entry for a trusted system
uucp Tru64 Copies files from one system to another (UNIX-toUNIX system copy)
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service