Aren/NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add a little waffle about `inaccessible' devices.

Browse Source
This commit is contained in:
ad 2001-03-20 13:08:43 +00:00
parent 2b5d9695ea
commit fac6acf4f0
1 changed files with 14 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
share/man/man4/iopsp.4
View File

@ -1,4 +1,4 @@
.\" $NetBSD: iopsp.4,v 1.2 2000/12/11 13:11:59 ad Exp $
.\" $NetBSD: iopsp.4,v 1.3 2001/03/20 13:08:43 ad Exp $
.\"
.\" Copyright (c) 2000 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -49,14 +49,24 @@ The
driver provides support for I2O SCSI bus adapter ports and child
peripherals.
.Pp
I2O adapters present each child peripheral attached to a bus adapter port
as an individual device.
In order to present the appearance of a bus, the
IOPs present each child peripheral attached to a bus adapter port as an
individual device. In order to present the appearance of a bus, the
.Nm
driver groups child peripherals by controlling port.
.Pp
On IOPs containing a SCSI port and block or tape driver modules, some SCSI
devices may not be directly accessible. For each inaccessible device, a
message will be displayed during configuration. For example:
.Bd -literal
iopsp0: target 0,0 (tid 70): in use by tid 47
.Ed
.Pp
Such devices will usually be indirectly accessible as block devices, either
individually or as part of an array.
.Sh SEE ALSO
.Xr intro 4 ,
.Xr iop 4 ,
.Xr ld 4 ,
.Xr scsi 4
.Sh AUTHOR
The