Update serial status

diff --git a/notes/Reqs.txt b/notes/Reqs.txt
index 6d24aefe43368797e5fb26d123bc7ec8bb635ea9..19d6d4658e03115f4d8aae39c5d5eda4635df8f8 100644 (file)
--- a/notes/Reqs.txt
+++ b/notes/Reqs.txt
@@ -4,9 +4,9 @@ Single-board computer running full GNU/Linux (any with USB / GPIO should work).
 
 Dedicated Ethernet port for that SBC; connect over SSH the usual way. (Our code doesn't need to worry about authentication nor encryption).
 
-Serial ports. Lots and lots of serial ports. For a standard server, just wire up to the serial port for interfacing. For the half-broken coreboot on the D16s, wire serial port RX to the D16's TX (for early boot log) but port TX to the RX pin of a serial->USB HID adaptor (so we pretend to be a keyboard).
+Serial ports. Lots and lots of serial ports. 
 
-To manage an entire fleet by the same board, external USB->serial multiplexing adaptors can be used, so we can have e.g. 5 serial ports (5 servers) on the same port .
+To manage an entire fleet by the same board, external USB->serial multiplexing adaptors can be used, so we can have e.g. 5 serial ports (5 servers) on the same port.
 
 For power output and similar tasks, connect like a switch using the board GPIO. For a small number of servers, we can wire up directly to the board GPIO; for a larger number, I imagine USB->GPIO adaptors exist.