From 62a2455f1d6940114a08331d89ec4f6b61d6f9d0 Mon Sep 17 00:00:00 2001 From: Alyssa Rosenzweig Date: Wed, 4 Jul 2018 11:52:55 -0400 Subject: [PATCH] Update serial status --- notes/Reqs.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/notes/Reqs.txt b/notes/Reqs.txt index 6d24aef..19d6d46 100644 --- 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. -- 2.25.1