Difference between revisions of "Running an LSI-11 from UNIX V6"

From Computer History Wiki
Jump to: navigation, search
m (+See also)
m (rm bloat)
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
It is relatively easy to run a hardware [[LSI-11]] (or [[PDP-11/23]], [[PDP-11/73]], etc, although this article will use the term 'LSI-11') from a [[PDP-11]] (either real or simulated) running [[UNIX Sixth Edition|Unix V6]].
+
It is relatively easy to run a hardware [[LSI-11]] (or [[PDP-11/23]], [[PDP-11/73]], etc, although this article will use the term 'LSI-11' for all of them) from a [[PDP-11]] (either real or simulated) running [[UNIX Sixth Edition|Unix V6]].
  
 
If one connects the LSI-11's [[asynchronous serial line]] console to a serial line on the Unix V6 machine (either real or simulated), a program ('ttytalk', see below) exists to allow a user logged into the Unix machine to talk to the console, load programs into it, etc.
 
If one connects the LSI-11's [[asynchronous serial line]] console to a serial line on the Unix V6 machine (either real or simulated), a program ('ttytalk', see below) exists to allow a user logged into the Unix machine to talk to the console, load programs into it, etc.
  
One issue is that Unix V6 does not allow 8-bit output on serial lines; this capability is needed to load binary files into the LSI-11. A small change to the shared serial line driver, dmr/tty.c, allows this.
+
One issue with doing so on Unix 'vanilla' V6 is that it insists on sending a [[parity]] bit on all output characters to a serial line, and there is no way to disable that. Also, the user-called top end of the serial line [[device driver]] output code inserts bytes with the high bit set into the output queue, to indicate the inter-character delays needed after some characters (e.g. 'carriage return') to support many of the [[printing terminal]]s of the day. Finally, probably to support all the above, it explicitly does not allow 8-bit output on serial lines; this capability is needed to load binary files into the LSI-11. Several small change to the shared serial line driver, dmr/tty.c, fix these issues.
  
 
Since the mode word in stty/gtty is already full, one has to extend the device interface to support setting and clearing 8-bit output support. One can either add ioctl() or do an upward-compatible extension to stty/gtty (see external link below); the code below takes the latter tack.
 
Since the mode word in stty/gtty is already full, one has to extend the device interface to support setting and clearing 8-bit output support. One can either add ioctl() or do an upward-compatible extension to stty/gtty (see external link below); the code below takes the latter tack.
  
The same interface is used to send a BREAK down the serial line to the console (used to halt the machine, e.g. when it is in a tight loop).
+
The same interface is used to send a BREAK down the serial line to the LSI-11's console (used to halt the machine, e.g. when it is in a tight loop).
  
 
The current code is somewhat inelegant, since the generic code to recognize the extended interface is currently in the serial line driver (dl.c), and not in the stty() system call code (since moving it there would mean adding entries in cdevsw[], and it was desired to minimize the number of modules that were changed).
 
The current code is somewhat inelegant, since the generic code to recognize the extended interface is currently in the serial line driver (dl.c), and not in the stty() system call code (since moving it there would mean adding entries in cdevsw[], and it was desired to minimize the number of modules that were changed).
Line 26: Line 26:
 
==External links==
 
==External links==
  
*[http://www.chiappa.net/~jnc/tech/newtty.txt Extended TTY Modes, and User Interface]
+
*[http://ana-3.lcs.mit.edu/~jnc/tech/unix/newtty.txt Extended TTY Modes, and User Interface]
*[http://ana-3.lcs.mit.edu/~jnc/tech/unix/tty.c tty.c]
+
*[http://ana-3.lcs.mit.edu/~jnc/tech/unix/sys/tty.h tty.h]
*[http://ana-3.lcs.mit.edu/~jnc/tech/unix/dl.c dl.c]
+
*[http://ana-3.lcs.mit.edu/~jnc/tech/unix/sys/tty.c tty.c]
 +
*[http://ana-3.lcs.mit.edu/~jnc/tech/unix/sys/dl.c dl.c]
 
*[http://ana-3.lcs.mit.edu/~jnc/tech/unix/ttytalk.c ttytalk.c]
 
*[http://ana-3.lcs.mit.edu/~jnc/tech/unix/ttytalk.c ttytalk.c]
 
{{PDP-11}}
 
  
 
[[Category: UNIX Practical Guides‎]]
 
[[Category: UNIX Practical Guides‎]]

Latest revision as of 17:25, 2 July 2023

It is relatively easy to run a hardware LSI-11 (or PDP-11/23, PDP-11/73, etc, although this article will use the term 'LSI-11' for all of them) from a PDP-11 (either real or simulated) running Unix V6.

If one connects the LSI-11's asynchronous serial line console to a serial line on the Unix V6 machine (either real or simulated), a program ('ttytalk', see below) exists to allow a user logged into the Unix machine to talk to the console, load programs into it, etc.

One issue with doing so on Unix 'vanilla' V6 is that it insists on sending a parity bit on all output characters to a serial line, and there is no way to disable that. Also, the user-called top end of the serial line device driver output code inserts bytes with the high bit set into the output queue, to indicate the inter-character delays needed after some characters (e.g. 'carriage return') to support many of the printing terminals of the day. Finally, probably to support all the above, it explicitly does not allow 8-bit output on serial lines; this capability is needed to load binary files into the LSI-11. Several small change to the shared serial line driver, dmr/tty.c, fix these issues.

Since the mode word in stty/gtty is already full, one has to extend the device interface to support setting and clearing 8-bit output support. One can either add ioctl() or do an upward-compatible extension to stty/gtty (see external link below); the code below takes the latter tack.

The same interface is used to send a BREAK down the serial line to the LSI-11's console (used to halt the machine, e.g. when it is in a tight loop).

The current code is somewhat inelegant, since the generic code to recognize the extended interface is currently in the serial line driver (dl.c), and not in the stty() system call code (since moving it there would mean adding entries in cdevsw[], and it was desired to minimize the number of modules that were changed).

See also

External links