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