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
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
|
.\" Copyright 1989 AT&T
.\" Copyright (C) 1999, Sun Microsystems, Inc. All Rights Reserved
.\" Copyright (c) 2017, Joyent, Inc.
.\" The contents of this file are subject to the terms of the
.\" Common Development and Distribution License (the "License").
.\" You may not use this file except in compliance with the License.
.\"
.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
.\" or http://www.opensolaris.org/os/licensing.
.\" See the License for the specific language governing permissions
.\" and limitations under the License.
.\"
.\" When distributing Covered Code, include this CDDL HEADER in each
.\" file and include the License file at usr/src/OPENSOLARIS.LICENSE.
.\" If applicable, add the following below this CDDL HEADER, with the
.\" fields enclosed by brackets "[]" replaced with your own identifying
.\" information: Portions Copyright [yyyy] [name of copyright owner]
.Dd October 29, 2017
.Dt TERMIOX 4I
.Os
.Sh NAME
.Nm termiox
.Nd extended general terminal interface
.Sh DESCRIPTION
The extended general terminal interface supplements the
.Xr termio 4I
general terminal interface by adding support for asynchronous hardware flow
control, isochronous flow control and clock modes, and local implementations of
additional asynchronous features.
Some systems may not support all of these
capabilities because of either hardware or software limitations.
Other systems may not permit certain functions to be disabled.
In these cases the appropriate bits will be ignored.
See
.In sys/termiox.h
for your system to find out which capabilities are supported.
.Ss "Hardware Flow Control Modes"
Hardware flow control supplements the
.Xr termio 4I
.Dv IXON ,
.Dv IXOFF ,
and
.Dv IXANY
character flow control.
Character flow control occurs when one
device controls the data transfer of another device by the insertion of control
characters in the data stream between devices.
Hardware flow control occurs
when one device controls the data transfer of another device using electrical
control signals on wires (circuits) of the asynchronous interface.
Isochronous
hardware flow control occurs when one device controls the data transfer of
another device by asserting or removing the transmit clock signals of that
device.
Character flow control and hardware flow control may be simultaneously
set.
.Pp
In asynchronous, full duplex applications, the use of the Electronic Industries
Association's EIA-232-D Request To Send (RTS) and Clear To Send (CTS) circuits
is the preferred method of hardware flow control.
An interface to other
hardware flow control methods is included to provide a standard interface to
these existing methods.
.Pp
The EIA-232-D standard specified only unidirectional hardware flow control \(em
the Data Circuit-terminating Equipment or Data Communications Equipment (DCE)
indicates to the Data Terminal Equipment (DTE) to stop transmitting data.
The
.Nm
interface allows both unidirectional and bidirectional hardware
flow control; when bidirectional flow control is enabled, either the DCE or DTE
can indicate to each other to stop transmitting data across the interface.
Note: It is assumed that the asynchronous port is configured as a DTE.
If the
connected device is also a DTE and not a DCE, then DTE to DTE (for example,
terminal or printer connected to computer) hardware flow control is possible by
using a null modem to interconnect the appropriate data and control circuits.
.Ss "Clock Modes"
Isochronous communication is a variation of asynchronous communication whereby
two communicating devices may provide transmit and/or receive clock signals to
one another.
Incoming clock signals can be taken from the baud rate generator
on the local isochronous port controller, from CCITT V\.24 circuit 114,
Transmitter Signal Element Timing - DCE source (EIA-232-D pin 15), or from
CITT V\.24 circuit 115, Receiver Signal Element Timing - DCE source (EIA-232-D
pin 17).
Outgoing clock signals can be sent on CCITT V\.24 circuit 113,
Transmitter Signal Element Timing - DTE source (EIA-232-D pin 24), on CCITT
V\.24 circuit 128, Receiver Signal Element Timing - DTE source (no EIA-232-D
pin), or not sent at all.
.Pp
In terms of clock modes, traditional asynchronous communication is implemented
simply by using the local baud rate generator as the incoming transmit and
receive clock source and not outputting any clock signals.
.Ss "Terminal Parameters"
The parameters that control the behavior of devices providing the
.Nm
interface are specified by the
.Vt termiox
structure defined in the
.In sys/termiox.h
header.
Several
.Xr ioctl 2
system calls that fetch
or change these parameters use this structure:
.Bd -literal -offset 2n
#define NFF 5
struct termiox {
unsigned short x_hflag; /* hardware flow control modes */
unsigned short x_cflag; /* clock modes */
unsigned short x_rflag[NFF]; /* reserved modes */
unsigned short x_sflag; /* spare local modes */
};
.Ed
.Pp
The
.Fa x_hflag
field describes hardware flow control modes:
.Bl -column xxxxxxx xxxxxxx x
.It Dv RTSXOFF Ta 0000001 Ta "Enable RTS hardware flow control on input."
.It Dv CTSXON Ta 0000002 Ta "Enable CTS hardware flow control on output."
.It Dv DTRXOFF Ta 0000004 Ta "Enable DTR hardware flow control on input."
.It Dv CDXON Ta 0000010 Ta "Enable CD hardware flow control on output."
.It Dv ISXOFF Ta 0000020 Ta "Enable isochronous hardware flow control on input."
.El
.Pp
The EIA-232-D DTR and CD circuits are used to establish a connection between
two systems.
The RTS circuit is also used to establish a connection with a modem.
Thus, both DTR and RTS are activated when an asynchronous port is opened.
If DTR is used for hardware flow control, then RTS must be used for
connectivity.
If CD is used for hardware flow control, then CTS must be used
for connectivity.
Thus, RTS and DTR (or CTS and CD) cannot both be used for
hardware flow control at the same time.
Other mutual exclusions may apply, such as the simultaneous setting of the
.Xr termio 4I
.Dv HUPCL
and the
.Vt termiox
.Dv DTRXOFF
bits, which use the DTE ready line for different functions.
.Pp
Variations of different hardware flow control methods may be selected by
setting the appropriate bits.
For example, bidirectional RTS/CTS flow control is selected by setting both the
.Dv RTSXOFF
and
.Dv CTSXON
bits and bidirectional DTR/CTS flow control is selected by setting both the
.Dv DTRXOFF
and
.Dv CTSXON .
Modem control or unidirectional CTS hardware
flow control is selected by setting only the
.Dv CTSXON
bit.
.Pp
As previously mentioned, it is assumed that the local asynchronous port (for
example, computer) is configured as a DTE.
If the connected device (for example, printer) is also a DTE, it is assumed
that the device is connected to the computer's asynchronous port using a null
modem that swaps control circuits (typically RTS and CTS).
The connected DTE drives RTS and the null modem swaps
RTS and CTS so that the remote RTS is received as CTS by the local DTE.
In the case that
.Dv CTSXON
is set for hardware flow control, printer's lowering
of its RTS would cause CTS seen by the computer to be lowered.
Output to the printer is suspended until the printer's raising of its RTS,
which would cause CTS seen by the computer to be raised.
.Pp
If
.Dv RTSXOFF
is set, the Request To Send (RTS) circuit (line) will be
raised, and if the asynchronous port needs to have its input stopped, it will
lower the Request To Send (RTS) line.
If the RTS line is lowered, it is assumed
that the connected device will stop its output until RTS is raised.
.Pp
If
.Dv CTSXON
is set, output will occur only if the Clear To Send (CTS)
circuit (line) is raised by the connected device.
If the CTS line is lowered by
the connected device, output is suspended until CTS is raised.
.Pp
If
.Dv DTRXOFF
is set, the DTE Ready (DTR) circuit (line) will be raised, and
if the asynchronous port needs to have its input stopped, it will lower the DTE
Ready (DTR) line.
If the DTR line is lowered, it is assumed that the connected
device will stop its output until DTR is raised.
.Pp
If
.Dv CDXON
is set, output will occur only if the Received Line Signal
Detector (CD) circuit (line) is raised by the connected device.
If the CD line
is lowered by the connected device, output is suspended until CD is raised.
.Pp
If
.Dv ISXOFF
is set, and if the isochronous port needs to have its input
stopped, it will stop the outgoing clock signal.
It is assumed that the
connected device is using this clock signal to create its output.
Transit and receive clock sources are programmed using the
.Fa x_cflag
fields.
If the port is not programmed for external clock generation,
.Dv ISXOFF
is ignored.
Output isochronous flow control is supported by appropriate clock source
programming using the
.Fa x_cflag
field and enabled at the remote connected device.
.Pp
The
.Fa x_cflag
field specifies the system treatment of clock modes.
.Bl -column xxxxxxxxx xxxxxxxx l
.It Dv XMTCLK Ta 0000007 Ta "Transmit clock source:"
.It Dv XCIBRG Ta 0000000 Ta "Get transmit clock from internal baud rate generator."
.It Dv XCTSET Ta 0000001 Ta "Get transmit clock from transmitter signal element timing (DCE source) lead, CCITT V\.24 circuit 114, EIA-232-D pin 15."
.It Dv XCRSET Ta 0000002 Ta Get transmit clock from receiver signal element timing (DCE source) lead, CCITT V\.4 circuit 115, EIA-232-D pin 17."
.It Dv RCVCLK Ta 0000070 Ta "Receive clock source:"
.It Dv RCIBRG Ta 0000000 Ta "Get receive clock from internal baud rate generator."
.It Dv RCTSET Ta 0000010 Ta "Get receive clock from transmitter signal element timing (DCE source) lead, CCITT V\.24 circuit 114, EIA-232-D pin 15."
.It Dv RCRSET Ta 0000020 Ta "Get receive clock from receiver signal element timing (DCE source) lead, CCITT V\.24 circuit 115, EIA-232-D pin 17."
.It Dv TSETCLK Ta 0000700 Ta "Transmitter signal element timing (DTE source) lead, CCITT V\.24 circuit 113, EIA-232-D pin 24, clock source:"
.It Dv TSETCOFF Ta 0000000 Ta "TSET clock not provided."
.It Dv TSETCRBRG Ta 0000100 Ta "Output receive baud rate generator on circuit 113."
.It Dv TSETCTBRG Ta 0000200 Ta "Output transmit baud rate generator on circuit 113"
.It Dv TSETCTSET Ta 0000300 Ta "Output transmitter signal element timing (DCE source) on circuit 113."
.It Dv TSETCRSET Ta 0000400 Ta "Output receiver signal element timing (DCE source) on circuit 113."
.It Dv RSETCLK Ta 0007000 Ta "Receiver signal element timing (DTE source) lead, CCITT V\.24 circuit 128, no EIA-232-D pin, clock source:"
.It Dv RSETCOFF Ta 0000000 Ta "RSET clock not provided."
.It Dv RSETCRBRG Ta 0001000 Ta "Output receive baud rate generator on circuit 128."
.It Dv RSETCTBRG Ta 0002000 Ta "Output transmit baud rate generator on circuit 128."
.It Dv RSETCTSET Ta 0003000 Ta "Output transmitter signal element timing (DCE source) on circuit 128."
.It Dv RSETCRSET Ta 0004000 Ta "Output receiver signal element timing (DCE) on circuit 128."
.El
.Pp
If the
.Fa XMTCLK
field has a value of
.Dv XCIBRG
the transmit clock is taken from the hardware internal baud rate generator, as
in normal asynchronous transmission.
If
.Fa XMTCLK
=
.Dv XCTSET
the transmit clock is taken from
the Transmitter Signal Element Timing (DCE source) circuit.
If
.Fa XMTCLK
=
.Dv XCRSET
the transmit clock is taken from the Receiver Signal Element
Timing (DCE source) circuit.
.Pp
If the
.Fa RCVCLK
field has a value of
.Dv RCIBRG ,
the receive clock is
taken from the hardware Internal Baud Rate Generator, as in normal asynchronous
transmission.
If
.Fa RCVCLK
=
.Dv RCTSET
the receive clock is taken from
the Transmitter Signal Element Timing (DCE source) circuit.
If
.Fa RCVCLK
=
.Dv RCRSET
the receive clock is taken from the Receiver Signal Element Timing
(DCE source) circuit.
.Pp
If the
.Fa TSETCLK
field has a value of
.Dv TSETCOFF
the Transmitter Signal Element Timing (DTE source) circuit is not driven.
If
.Fa TSETCLK
=
.Dv TSETCRBRG
the Transmitter Signal Element Timing (DTE source) circuit is
driven by the Receive Baud Rate Generator.
If
.Fa TSETCLK
=
.Dv TSETCTBRG
the Transmitter Signal Element Timing (DTE source) circuit is driven by the
Transmit Baud Rate Generator.
If
.Fa TSETCLK
=
.Dv TSETCTSET
the Transmitter Signal Element Timing (DTE source) circuit is driven by the
Transmitter Signal Element Timing (DCE source).
If
.Fa TSETCLK
=
.Dv TSETCRBRG
the Transmitter Signal Element Timing (DTE source) circuit is
driven by the Receiver Signal Element Timing (DCE source).
.Pp
If the
.Fa RSETCLK
field has a value of
.Dv RSETCOFF
the Receiver Signal Element Timing (DTE source) circuit is not driven.
If
.Fa RSETCLK
=
.Dv RSETCRBRG
the Receiver Signal Element Timing (DTE source) circuit is
driven by the Receive Baud Rate Generator.
If
.Fa RSETCLK
=
.Dv RSETCTBRG
the Receiver Signal Element Timing (DTE source) circuit is driven by the
Transmit Baud Rate Generator.
If
.Fa RSETCLK
=
.Dv RSETCTSET
the Receiver
Signal Element Timing (DTE source) circuit is driven by the Transmitter Signal
Element Timing (DCE source).
If
.Fa RSETCLK
=
.Dv RSETCRBRG
the Receiver
Signal Element Timing (DTE source) circuit is driven by the Receiver Signal
Element Timing (DCE source).
.Pp
The
.Fa x_rflag
is reserved for future interface definitions and should not
be used by any implementations.
The
.Fa x_sflag
may be used by local
implementations wishing to customize their terminal interface using the
.Nm
ioctl system calls.
.Sh IOCTLS
The
.Xr ioctl 2
system calls have the form:
.Bd -literal -offset 2n
struct termiox *arg;
ioctl(fildes, command, arg);
.Ed
.Pp
The commands using this form are:
.Bl -tag -width TCSETXW
.It Dv TCGETX
The argument is a pointer to a
.Vt termiox
structure.
The current terminal parameters are fetched and stored into that structure.
.It Dv TCSETX
The argument is a pointer to a
.Vt termiox
structure.
The current terminal parameters are set from the values stored in that structure.
The change is immediate.
.It Dv TCSETXW
The argument is a pointer to a
.Vt termiox
structure.
The current terminal parameters are set from the values stored in that structure.
The change occurs after all characters queued for output have been transmitted.
This form should be used when changing parameters that will affect output.
.It Dv TCSETXF
The argument is a pointer to a
.Vt termiox
structure.
The current terminal parameters are set from the values stored in that structure.
The change occurs
after all characters queued for output have been transmitted; all characters
queued for input are discarded and then the change occurs.
.El
.Sh FILES
.Pa /dev/*
.Sh SEE ALSO
.Xr stty 1 ,
.Xr ioctl 2 ,
.Xr termio 4I
.Sh NOTES
The
.Nm termiox Ns Pq 4I
system call is provided for compatibility with previous
releases and its use is discouraged.
Instead, the
.Xr termio 4I
system call is recommended.
See
.Xr termio 4I
for usage information.
|