Be explicit about hardware flow control (RTS/CTS) being the only supported option.

This commit is contained in:
Oliver Schmidt 2021-09-26 12:09:50 +02:00
parent 52e4387929
commit 28b1687aaf
9 changed files with 30 additions and 29 deletions

View File

@ -428,8 +428,8 @@ The names in the parentheses denote the symbols to be used for static linking of
<tag><tt/a2.ssc.ser (a2_ssc_ser)/</tag> <tag><tt/a2.ssc.ser (a2_ssc_ser)/</tag>
Driver for the Apple&nbsp;II Super Serial Card. Supports up to 19200 baud, Driver for the Apple&nbsp;II Super Serial Card. Supports up to 19200 baud,
hardware flow control (RTS/CTS) and interrupt driven receives. Note requires hardware flow control (RTS/CTS) and does interrupt driven receives.
that because of the peculiarities of the 6551 chip transmits are not Note that because of the peculiarities of the 6551 chip transmits are not
interrupt driven, and the transceiver blocks if the receiver asserts interrupt driven, and the transceiver blocks if the receiver asserts
flow control because of a full buffer. flow control because of a full buffer.

View File

@ -428,8 +428,8 @@ The names in the parentheses denote the symbols to be used for static linking of
<tag><tt/a2e.ssc.ser (a2e_ssc_ser)/</tag> <tag><tt/a2e.ssc.ser (a2e_ssc_ser)/</tag>
Driver for the Apple&nbsp;II Super Serial Card. Supports up to 19200 baud, Driver for the Apple&nbsp;II Super Serial Card. Supports up to 19200 baud,
hardware flow control (RTS/CTS) and interrupt driven receives. Note requires hardware flow control (RTS/CTS) and does interrupt driven receives.
that because of the peculiarities of the 6551 chip transmits are not Note that because of the peculiarities of the 6551 chip transmits are not
interrupt driven, and the transceiver blocks if the receiver asserts interrupt driven, and the transceiver blocks if the receiver asserts
flow control because of a full buffer. flow control because of a full buffer.

View File

@ -675,9 +675,9 @@ The default callbacks definition (<tt/mouse_def_callbacks/) is an alias for the
<sect1>RS232 device drivers<p> <sect1>RS232 device drivers<p>
Currently there is one RS232 driver. It uses the R: device (therefore Currently there is one RS232 driver. It supports up to 9600 baud, requires hardware flow control
an R: driver needs to be installed) and was tested with the 850 (RTS/CTS) and uses the R: device (therefore an R: driver needs to be installed). It was tested
interface module. with the 850 interface module.
<table> <table>
<tabular ca="rr"> <tabular ca="rr">

View File

@ -176,10 +176,11 @@ No mouse drivers are currently available for the Atmos.
<tag><tt/atmos-acia.ser (atmos_acia_ser)/</tag> <tag><tt/atmos-acia.ser (atmos_acia_ser)/</tag>
Driver for the Telestrat integrated serial controller and the Atmos with a Driver for the Telestrat integrated serial controller and the Atmos with a
serial add-on. serial add-on. Supports up to 19200 baud, requires hardware flow control
Note that, because of the peculiarities of the 6551 chip, together with the (RTS/CTS) and does interrupt driven receives. Note that, because of the
use of the NMI, transmits are not interrupt driven; and, the transceiver peculiarities of the 6551 chip, together with the use of the NMI, transmits
blocks if the receiver asserts flow control because of a full buffer. are not interrupt driven; and, the transceiver blocks if the receiver
asserts flow control because of a full buffer.
</descrip><p> </descrip><p>

View File

@ -324,9 +324,9 @@ The default drivers, <tt/mouse_stddrv (mouse_static_stddrv)/, point to <tt/c128-
<descrip> <descrip>
<tag><tt/c128-swlink.ser (c128_swlink_ser)/</tag> <tag><tt/c128-swlink.ser (c128_swlink_ser)/</tag>
Driver for the SwiftLink cartridge. Supports up to 38400 BPS, hardware flow Driver for the SwiftLink cartridge. Supports up to 38400 baud, requires hardware
control (RTS/CTS), and interrupt-driven receives. Note that, because of the flow control (RTS/CTS) and does interrupt driven receives. Note that, because of
peculiarities of the 6551 chip, together with the use of the NMI, transmits the peculiarities of the 6551 chip, together with the use of the NMI, transmits
are not interrupt driven; and, the transceiver blocks if the receiver asserts are not interrupt driven; and, the transceiver blocks if the receiver asserts
flow control because of a full buffer. flow control because of a full buffer.

View File

@ -410,9 +410,9 @@ The default drivers, <tt/mouse_stddrv (mouse_static_stddrv)/, point to <tt/c64-1
<descrip> <descrip>
<tag><tt/c64-swlink.ser (c64_swlink_ser)/</tag> <tag><tt/c64-swlink.ser (c64_swlink_ser)/</tag>
Driver for the SwiftLink cartridge. Supports up to 38400 BPS, hardware flow Driver for the SwiftLink cartridge. Supports up to 38400 baud, requires hardware
control (RTS/CTS), and interrupt-driven receives. Note that, because of the flow control (RTS/CTS) and does interrupt driven receives. Note that, because of
peculiarities of the 6551 chip, together with the use of the NMI, transmits the peculiarities of the 6551 chip, together with the use of the NMI, transmits
are not interrupt driven; and, the transceiver blocks if the receiver asserts are not interrupt driven; and, the transceiver blocks if the receiver asserts
flow control because of a full buffer. flow control because of a full buffer.

View File

@ -231,10 +231,10 @@ The default drivers, <tt/mouse_stddrv (mouse_static_stddrv)/, point to <tt/cbm51
<tag><tt/cbm510-std.ser (cbm510_std_ser)/</tag> <tag><tt/cbm510-std.ser (cbm510_std_ser)/</tag>
Driver for the 6551 ACIA chip built into the Commodore 510. Supports up to Driver for the 6551 ACIA chip built into the Commodore 510. Supports up to
19200 BPS, hardware flow control (RTS/CTS), and interrupt-driven receives. 19200 baud, requires hardware flow control (RTS/CTS) and does interrupt driven
Note that, because of the peculiarities of the 6551 chip, transmits are not receives. Note that, because of the peculiarities of the 6551 chip, transmits
interrupt driven; and, the transceiver blocks if the receiver asserts flow are not interrupt driven; and, the transceiver blocks if the receiver asserts
control because of a full buffer. flow control because of a full buffer.
</descrip><p> </descrip><p>

View File

@ -212,10 +212,10 @@ No mouse drivers are currently available for the Commodore 610.
<tag><tt/cbm610-std.ser (cbm610_std_ser)/</tag> <tag><tt/cbm610-std.ser (cbm610_std_ser)/</tag>
Driver for the 6551 ACIA chip built into the Commodore 610. Supports up to Driver for the 6551 ACIA chip built into the Commodore 610. Supports up to
19200 BPS, hardware flow control (RTS/CTS), and interrupt-driven receives. 19200 baud, requires hardware flow control (RTS/CTS) and does interrupt driven
Note that, because of the peculiarities of the 6551 chip, transmits are not receives. Note that, because of the peculiarities of the 6551 chip, transmits
interrupt driven; and, the transceiver blocks if the receiver asserts flow are not interrupt driven; and, the transceiver blocks if the receiver asserts
control because of a full buffer. flow control because of a full buffer.
</descrip><p> </descrip><p>

View File

@ -195,10 +195,10 @@ No mouse drivers are currently available for the Plus/4.
<tag><tt/plus4-stdser.ser (plus4_stdser_ser)/</tag> <tag><tt/plus4-stdser.ser (plus4_stdser_ser)/</tag>
Driver for the 6551 ACIA chip built into the Plus/4. Supports up to 19200 Driver for the 6551 ACIA chip built into the Plus/4. Supports up to 19200
baud, hardware flow control (RTS/CTS) and interrupt driven receives. Note baud, requires hardware flow control (RTS/CTS) and does interrupt driven
that because of the peculiarities of the 6551 chip transmits are not receives. Note that because of the peculiarities of the 6551 chip transmits
interrupt driven, and the transceiver blocks if the receiver asserts flow are not interrupt driven, and the transceiver blocks if the receiver asserts
control because of a full buffer. flow control because of a full buffer.
You need an adapter to use the builtin port, since the output levels You need an adapter to use the builtin port, since the output levels
available at the user port don't follow the RS232 standard. available at the user port don't follow the RS232 standard.