blob: 1af02ff90fc4f2e966dff2912349669ebe79bd91 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
|
.\" $Id$
.Dd October 11, 1993
.Dt UK 4
.Os FreeBSD
.Sh NAME
.Nm uk
.Nd scsi user-level driver
.Sh SYNOPSIS
.Nm device uk
.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 it's 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
|