1usbsksp(7D) Devices usbsksp(7D)
2
3
4
6 usbsksp - Keyspan USB to serial converter driver
7
9 #include <fcntl.h>
10
11
12 #include <sys/termio.h>
13
14
15 usbskpsp@unit
16
17
19 The usbsksp driver is a loadable STREAMS and USBA (Solaris USB archi‐
20 tecture) compliant client driver that provides basic asynchronous com‐
21 munication support for Keyspan USB-to-serial converters. The usbsksp
22 driver supports the Keyspan USA19HS, USA49WG and USA49WLC models. By
23 default, the USA19HS and USA49WG models are compatible with the usbsksp
24 driver and no configuration or installation steps are required. (The
25 USA49WG model is a USB 2.0 device comforming to Universal Serial Bus
26 Specification 2.0 and the USB 2.0 host controller is required to sup‐
27 port the USA49WG model. Note that the USA49WG is not compatible with
28 USB 1.1 host controllers). If you use the Keyspan USA49WLC model, you
29 must download and install a firmware package to enable the device to
30 work with the usbsksp driver. See the Keyspan website
31 (http://www.keyspan.com/downloads/sun/) for more information. Serial
32 device streams are built with appropriate modules that are pushed
33 atop the usbsksp driver by the autopush(1M) facility.
34
35
36 The usbsksp module supports the termio(7I) device control functions
37 specified by flags in the c_cflag word of the termios structure, and by
38 the IGNBRK, IGNPAR, PARMRK and INPCK flags in the c_iflag word of the
39 termios structure. All other termio(7I) functions must be performed by
40 STREAMS modules pushed atop the driver. When a device is opened, the
41 ldterm(7M) and ttcompat(7M) STREAMS modules are automatically pushed
42 on top of the stream, providing the standard termio(7I) interface.
43
44
45 Use device logical names /dev/term/[0-9]* to access the serial
46 ports. These names are typically used to provide a logical access point
47 for a dial-in line that is used with a modem.
48
49
50 A special feature (controlled by the minor device number) is available
51 that enables a single tty line to be connected to a modem and used for
52 incoming and outgoing calls. By accessing through device logical name
53 /dev/cua/[0-9]*, you can open a port without the carrier detect signal
54 being asserted, either through hardware or an equivalent software mech‐
55 anism. These devices are commonly known as 'dial-out' lines.
56
57
58 Unlike onboard serial ports, the usbsksp ports cannot serve as a local
59 serial console.
60
62 A dial-in line can be opened only if the corresponding dial-out line is
63 closed. A blocking /dev/term open waits until the /dev/cua line is
64 closed (which drops Data Terminal Ready, after which Carrier Detect
65 usually drops as well) and carrier is detected again. A non-blocking
66 /dev/term open returns an error if the /dev/cua is open.
67
68
69 If the /dev/term line is opened successfully (usually only when car‐
70 rier is recognized on the modem), the corresponding /dev/cua line can‐
71 not be opened. This allows a modem and port to be used for dial-in (by
72 enabling the line for login in /etc/inittab) or dial-out (by tip(1), or
73 uucp(1C)) when no one is logged in on the line.
74
75
76 Device hot-removal is functionally equivalent to a modem disconnect
77 event, as defined in termio(7I).
78
80 The usbsksp driver supports the standard set of termio(7I) ioctl
81 calls.
82
83
84 Input and output line speeds can be set to the following baud rates:
85 0, 50, 75, 110, 134, 150, 200, 300, 600, 1200, 1800, 2400, 4800, 9600,
86 19200, 38400, 57600, 115200, or 230400. Input and output line
87 speeds cannot be set independently. For example, when the output speed
88 is set, the input speed is automatically set to the same speed.
89
91 An open() fails under the following conditions:
92
93 ENXIO The unit being opened does not exist.
94
95
96 EBUSY The /dev/cua (dial-out) device is being opened while the
97 /dev/term (dial-in device) is open, or the dial-in device is
98 being opened with a no-delay open while the dial-out device is
99 open.
100
101
102 EBUSY The unit has been marked as exclusive-use by another process
103 with a TIOCEXCL ioctl() call.
104
105
106 EIO USB device I/O error.
107
108
110 /kernel/drv/usbsksp
111
112 32-bit x86 ELF kernel module.
113
114
115 /kernel/drv/amd64/usbsksp
116
117 64-bit x86 ELF kernel module.
118
119
120 /kernel/drv/sparcv9/usbsksp
121
122 64-bit SPARC ELF kernel module.
123
124
125 /dev/cua/[0-9]*
126
127 dial-out tty lines.
128
129
130 /dev/term/[0-9]*
131
132 dial-in tty lines.
133
134
136 See attributes(5) for descriptions of the following attributes:
137
138
139
140
141 ┌─────────────────────────────┬──────────────────────────────┐
142 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
143 ├─────────────────────────────┼──────────────────────────────┤
144 │Architecture │SPARC, x86, PCI-based systems │
145 ├─────────────────────────────┼──────────────────────────────┤
146 │Availability │SUNWuksp │
147 └─────────────────────────────┴──────────────────────────────┘
148
150 strconf(1), tip(1), uucp(1C), autopush(1M), ioctl(2), open(2),
151 termios(3C), attributes(5), usba(7D), termio(7I), ldterm(7M), ttcom‐
152 pat(7M)
153
155 In addition to being logged, the following messages may appear on the
156 system console. All messages are formatted in the following manner:
157
158 Warning: <device path> (usbsksp<instance num>): Error Message...
159
160
161
162 Device was disconnected while open. Data may have been lost.
163
164 The device has been hot-removed or powered off while it was open
165 and a possible data transfer was in progress. The job may be
166 aborted.
167
168
169 Device is not identical to the previous one on this port. Please dis‐
170 connect and reconnect.
171
172 The device was hot-removed while open. A new device was hot-
173 inserted which is not identical to the original device. Please dis‐
174 connect the device and reconnect the original device to the same
175 port.
176
177
178 Device has been reconnected, but data may have been lost.
179
180 The device that was hot-removed from its USB port has been re-
181 inserted again to the same port. It is available for access but
182 data from a previous transfer may be lost.
183
184
185 Cannot access <device>. Please reconnect.
186
187 This device has been disconnected because a device other than the
188 original one has been inserted. The driver informs you of this fact
189 by displaying the name of the original device.
190
191
192 No valid firmware available for Keyspan usa49wlc usb-to-serial adapter.
193 Please download it from Keyspan website and install it.
194
195 By default, only an empty firmware package is installed for the
196 usa49wlc model. Please download the SUNWukspfw package from
197 Keyspan's web site and install it.
198
199
200
201 The following messages may be logged into the system log. They are for‐
202 matted in the following manner:
203
204 <device path><usbsksp<instance number>): message...
205
206
207
208 Input overrun Data was lost.
209
210
211
212
213SunOS 5.11 23 August 2006 usbsksp(7D)