e1534707dd
could still use a little bit of touchup. I don't think there is any misinformation in these, but you never know. FreeBSD has a better MI scsi than we do. Partial fix for misc/2008. The author of that pr is willing to help a bit as well.
69 lines
1.2 KiB
Groff
69 lines
1.2 KiB
Groff
.Dd October 11, 1993
|
|
.Dt UK 4
|
|
.Os NetBSD
|
|
.Sh NAME
|
|
.Nm uk
|
|
.Nd scsi user-level driver
|
|
.Sh SYNOPSIS
|
|
.Nm uk* at scsibus? target ? lun ?
|
|
.Sh DESCRIPTION
|
|
The
|
|
.Nm uk
|
|
driver provides support for a
|
|
process to address devices on the scsi bus for which there is no configured
|
|
driver.
|
|
.\".Pp
|
|
.\"In FreeBSD releases prior to 2.1, the first unknown device
|
|
.\"found will be attached as
|
|
.\".Em uk0
|
|
.\"and the next,
|
|
.\".Em uk1
|
|
.\"etc.
|
|
.\"Beginning in 2.1 it is possible to specify what uk unit a device should
|
|
.\"come on line as; refer to
|
|
.\".Xr scsi 4
|
|
.\"for details on kernel configuration.
|
|
.Pp
|
|
A scsi adapter must also be separately configured into the system
|
|
before this driver makes sense.
|
|
.Pp
|
|
.Sh KERNEL CONFIGURATION
|
|
If an count is given that number of
|
|
.Nm
|
|
devices will be configured into the kernel.
|
|
|
|
.Pp
|
|
.Sh IOCTLS
|
|
The
|
|
.Nm
|
|
driver has no ioctls of its own but rather acts as a medium for the
|
|
generic
|
|
.Xr scsi 4
|
|
ioctls. These are described in
|
|
.Em sys/scsiio.h.
|
|
|
|
|
|
.Sh FILES
|
|
.Bl -tag -width /dev/uk0XXX -compact
|
|
.It Pa /dev/uk[0-255]
|
|
uk{x} is the 'xth'unknown device found.
|
|
.El
|
|
.Sh DIAGNOSTICS
|
|
All
|
|
.Xr scsi 4
|
|
debug ioctls work on
|
|
.Nm
|
|
devices.
|
|
.Sh SEE ALSO
|
|
.Xr sd 4
|
|
.Xr st 4
|
|
.Xr cd 4
|
|
.Xr ch 4
|
|
.Xr su 4
|
|
.Xr scsi 4
|
|
.Sh HISTORY
|
|
The
|
|
.Nm
|
|
driver appeared in 386BSD 0.1
|
|
|