Driver for the Telestrat integrated serial controller and the Atmos with a
- serial add-on.
- Note that, because of 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 flow control because of a full buffer.
+ serial add-on. Supports up to 19200 baud, requires hardware flow control
+ (RTS/CTS) and does interrupt driven receives. Note that, because of 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 flow control because of a full buffer.
diff --git a/doc/c128.sgml b/doc/c128.sgml
index 8c62b6ad1..60306814c 100644
--- a/doc/c128.sgml
+++ b/doc/c128.sgml
@@ -324,9 +324,9 @@ The default drivers,
- Driver for the SwiftLink cartridge. Supports up to 38400 BPS, hardware flow
- control (RTS/CTS), and interrupt-driven receives. Note that, because of the
- peculiarities of the 6551 chip, together with the use of the NMI, transmits
+ Driver for the SwiftLink cartridge. Supports up to 38400 baud, requires hardware
+ flow control (RTS/CTS) and does interrupt driven receives. Note that, because of
+ 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
flow control because of a full buffer.
diff --git a/doc/c64.sgml b/doc/c64.sgml
index 7e00f3b93..de37ed4b7 100644
--- a/doc/c64.sgml
+++ b/doc/c64.sgml
@@ -410,9 +410,9 @@ The default drivers,
- Driver for the SwiftLink cartridge. Supports up to 38400 BPS, hardware flow
- control (RTS/CTS), and interrupt-driven receives. Note that, because of the
- peculiarities of the 6551 chip, together with the use of the NMI, transmits
+ Driver for the SwiftLink cartridge. Supports up to 38400 baud, requires hardware
+ flow control (RTS/CTS) and does interrupt driven receives. Note that, because of
+ 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
flow control because of a full buffer.
diff --git a/doc/cbm510.sgml b/doc/cbm510.sgml
index c208f3ead..86bed7607 100644
--- a/doc/cbm510.sgml
+++ b/doc/cbm510.sgml
@@ -231,10 +231,10 @@ The default drivers,
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.
- Note that, because of the peculiarities of the 6551 chip, transmits are not
- interrupt driven; and, the transceiver blocks if the receiver asserts flow
- control because of a full buffer.
+ 19200 baud, requires hardware flow control (RTS/CTS) and does interrupt driven
+ receives. Note that, because of the peculiarities of the 6551 chip, transmits
+ are not interrupt driven; and, the transceiver blocks if the receiver asserts
+ flow control because of a full buffer.
diff --git a/doc/cbm610.sgml b/doc/cbm610.sgml
index 37a445dd1..d86950abc 100644
--- a/doc/cbm610.sgml
+++ b/doc/cbm610.sgml
@@ -212,10 +212,10 @@ No mouse drivers are currently available for the Commodore 610.
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.
- Note that, because of the peculiarities of the 6551 chip, transmits are not
- interrupt driven; and, the transceiver blocks if the receiver asserts flow
- control because of a full buffer.
+ 19200 baud, requires hardware flow control (RTS/CTS) and does interrupt driven
+ receives. Note that, because of the peculiarities of the 6551 chip, transmits
+ are not interrupt driven; and, the transceiver blocks if the receiver asserts
+ flow control because of a full buffer.
diff --git a/doc/plus4.sgml b/doc/plus4.sgml
index 645de5161..79a2597d0 100644
--- a/doc/plus4.sgml
+++ b/doc/plus4.sgml
@@ -195,10 +195,10 @@ No mouse drivers are currently available for the Plus/4.
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
- that because of the peculiarities of the 6551 chip transmits are not
- interrupt driven, and the transceiver blocks if the receiver asserts flow
- control because of a full buffer.
+ baud, requires hardware flow control (RTS/CTS) and does interrupt driven
+ receives. Note that because of the peculiarities of the 6551 chip transmits
+ are not interrupt driven, and the transceiver blocks if the receiver asserts
+ flow control because of a full buffer.
You need an adapter to use the builtin port, since the output levels
available at the user port don't follow the RS232 standard.