1.\" Copyright (c) 1998, Nicolas Souchu
2.\" All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\" notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\" notice, this list of conditions and the following disclaimer in the
11.\" documentation and/or other materials provided with the distribution.
12.\"
13.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
14.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
15.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
16.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
17.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
18.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
19.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
20.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
21.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
22.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
23.\" SUCH DAMAGE.
24.\"
25.\" $FreeBSD: head/share/man/man4/smbus.4 57676 2000-03-01 14:50:24Z sheldonh $
26.\"
27.Dd August 10, 1998
28.Dt SMBUS 4
29.Os FreeBSD
30.Sh NAME
31.Nm smbus
32.Nd
33System Management Bus
34.Sh SYNOPSIS
35.Cd "device smbus"
36.Pp
37.Cd "device iicsmb"
38.Cd "device bktr"
39.Sh DESCRIPTION
40The
41.Em smbus
42system provides a uniform, modular and architecture-independent
43system for the implementation of drivers to control various SMB devices
44and to utilize different SMB controllers (I2C, PIIX4, Brooktree848, vm86...).
45.Sh System Management Bus
46The
47.Em System Management Bus
48is a two-wire interface through which simple power-related chips can communicate
49with rest of the system.
50It uses I2C as its backbone (see
51.Xr iicbus 4 ).
52
53A system using SMB passes messages to and from devices instead of tripping
54individual control lines.
55
56With the SMBus, a device can provide manufacturer information, tell the
57system what its model/part number is, save its state for a suspend event,
58report different types of errors, accept control parameters, and return its
59status.
60
61The SMBus may share the same host device and physical bus as ACCESS bus
62components provided that an appropriate electrical bridge is provided
63between the internal SMB devices and external ACCESS bus devices.
64.Sh SEE ALSO
65.Xr bktr 4 ,
66.Xr iicbus 4 ,
67.Xr iicsmb 4 ,
68.Xr smb 4
69.Sh HISTORY
70The
71.Nm
72manual page first appeared in
73.Fx 3.0 .
74.Sh AUTHORS
75This
76manual page was written by
77.An Nicolas Souchu .
2.\" All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\" notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\" notice, this list of conditions and the following disclaimer in the
11.\" documentation and/or other materials provided with the distribution.
12.\"
13.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
14.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
15.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
16.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
17.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
18.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
19.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
20.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
21.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
22.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
23.\" SUCH DAMAGE.
24.\"
25.\" $FreeBSD: head/share/man/man4/smbus.4 57676 2000-03-01 14:50:24Z sheldonh $
26.\"
27.Dd August 10, 1998
28.Dt SMBUS 4
29.Os FreeBSD
30.Sh NAME
31.Nm smbus
32.Nd
33System Management Bus
34.Sh SYNOPSIS
35.Cd "device smbus"
36.Pp
37.Cd "device iicsmb"
38.Cd "device bktr"
39.Sh DESCRIPTION
40The
41.Em smbus
42system provides a uniform, modular and architecture-independent
43system for the implementation of drivers to control various SMB devices
44and to utilize different SMB controllers (I2C, PIIX4, Brooktree848, vm86...).
45.Sh System Management Bus
46The
47.Em System Management Bus
48is a two-wire interface through which simple power-related chips can communicate
49with rest of the system.
50It uses I2C as its backbone (see
51.Xr iicbus 4 ).
52
53A system using SMB passes messages to and from devices instead of tripping
54individual control lines.
55
56With the SMBus, a device can provide manufacturer information, tell the
57system what its model/part number is, save its state for a suspend event,
58report different types of errors, accept control parameters, and return its
59status.
60
61The SMBus may share the same host device and physical bus as ACCESS bus
62components provided that an appropriate electrical bridge is provided
63between the internal SMB devices and external ACCESS bus devices.
64.Sh SEE ALSO
65.Xr bktr 4 ,
66.Xr iicbus 4 ,
67.Xr iicsmb 4 ,
68.Xr smb 4
69.Sh HISTORY
70The
71.Nm
72manual page first appeared in
73.Fx 3.0 .
74.Sh AUTHORS
75This
76manual page was written by
77.An Nicolas Souchu .