Deleted Added
full compact
scsi.4 (117011) scsi.4 (131026)
1.\" Copyright (c) 1996
2.\" Julian Elischer <julian@FreeBSD.org>. 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 unchanged lines hidden (view full) ---

18.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
19.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
20.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
21.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
22.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
23.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
24.\" SUCH DAMAGE.
25.\"
1.\" Copyright (c) 1996
2.\" Julian Elischer <julian@FreeBSD.org>. 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 unchanged lines hidden (view full) ---

18.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
19.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
20.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
21.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
22.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
23.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
24.\" SUCH DAMAGE.
25.\"
26.\" $FreeBSD: head/share/man/man4/scsi.4 117011 2003-06-28 23:53:39Z ru $
26.\" $FreeBSD: head/share/man/man4/scsi.4 131026 2004-06-24 04:05:08Z scottl $
27.Dd October 15, 1998
28.Dt SCSI 4
29.Os
30.Sh NAME
31.Nm SCSI ,
32.Nm CAM
33.Nd CAM SCSI subsystem
34.Sh SYNOPSIS

--- 119 unchanged lines hidden (view full) ---

154will suffice for any number of disk drivers.
155.Pp
156The devices are either
157.Em wired
158so they appear as a particular device unit or
159.Em counted
160so that they appear as the next available unused unit.
161.Pp
27.Dd October 15, 1998
28.Dt SCSI 4
29.Os
30.Sh NAME
31.Nm SCSI ,
32.Nm CAM
33.Nd CAM SCSI subsystem
34.Sh SYNOPSIS

--- 119 unchanged lines hidden (view full) ---

154will suffice for any number of disk drivers.
155.Pp
156The devices are either
157.Em wired
158so they appear as a particular device unit or
159.Em counted
160so that they appear as the next available unused unit.
161.Pp
162To configure a driver in the kernel without wiring down the device use a
163config line similar to
164.Cd "device ch0"
165to include the changer driver.
162Units are wired down by setting kernel environment hints.
163This is usually done either interactively from the loader, or automatically via the
164.Pa /boot/device.hints
165file. The basic syntax is:
166.Bd -literal -offset indent
167hint.device.unit.property="value"
168.Ed
166.Pp
169.Pp
167To wire down a unit use a config line similar to
168.Cd "device ch1 at scbus0 target 4 unit 0"
169to assign changer 1 as the changer with SCSI ID 4,
170SCSI logical unit 0 on SCSI bus 0.
171Individual scbuses can be wired down to specific controllers with
172a config line similar to
173.Cd "device scbus0 at ahc0"
174which assigns scsi bus 0 to the first unit using the ahc driver.
175For controllers supporting more than one bus,
176the particular bus can be specified as in
177.Cd "device scbus3 at ahc1 bus 1"
178which assigns scbus 1 to the second bus probed on the ahc1 device.
170Individual scsi bus numbers can be wired down to specific controllers with
171a config line similar to the following:
172.Bd -literal -offset indent
173hint.scbus.0.at="ahd1"
174.Ed
179.Pp
175.Pp
176This assigns scsi bus number 0 to the
177.Em ahd1
178driver instance.
179For controllers supporting more than one bus, a particular bus can be assigned
180as follows:
181.Bd -literal -offset indent
182hint.scbus.0.at="ahc1"
183hint.scbus.0.bus="1"
184.Ed
185.Pp
186This assigns scsi bus 0 to the bus 1 instance on
187.Em ahc0 .
188Peripheral drivers can be wired to a specific bus, target, and lun as so:
189.Bd -literal -offset indent
190hint.da.0.at="scbus0"
191hint.da.0.target="0"
192hint.da.0.unit="0"
193.Ed
194.Pp
195This assigns
196.Em da0
197to target 0, unit (lun) 0 of scbus 0.
198Omitting the target or unit hints will instruct CAM to treat them as wildcards
199and use the first respective counted instances.
200These examples can be combined together to allow a peripheral device to be
201wired to any particular controller, bus, target, and/or unit instance.
202.Pp
180When you have a mixture of wired down and counted devices then the
181counting begins with the first non-wired down unit for a particular
182type.
183That is, if you have a disk wired down as
184.Em "device da1" ,
185then the first non-wired disk shall come on line as
186.Em da2 .
187.Sh ADAPTERS

--- 116 unchanged lines hidden ---
203When you have a mixture of wired down and counted devices then the
204counting begins with the first non-wired down unit for a particular
205type.
206That is, if you have a disk wired down as
207.Em "device da1" ,
208then the first non-wired disk shall come on line as
209.Em da2 .
210.Sh ADAPTERS

--- 116 unchanged lines hidden ---