Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site watcgl.UUCP
Path: utzoo!watmath!watcgl!dmmartindale
From: dmmartindale@watcgl.UUCP (Dave Martindale)
Newsgroups: net.unix,net.periphs
Subject: Re: LaserJet printercap for BSD 4.2?
Message-ID: <522@watcgl.UUCP>
Date: Wed, 21-Nov-84 11:52:46 EST
Article-I.D.: watcgl.522
Posted: Wed Nov 21 11:52:46 1984
Date-Received: Thu, 22-Nov-84 05:25:33 EST
References: <477@sdcsvax.UUCP> <1165@umcp-cs.UUCP> <254@bragvax.UUCP>
Organization: U of Waterloo, Ontario
Lines: 17

> In article <1165@umcp-cs.UUCP> chris@umcp-cs.UUCP (Chris Torek) writes:
> >Sigh.  You can't *get* an 8 bit data path *and* flow control in
> >standard 4.2BSD.  If you have some wizards lying around (``Heeeerrre,
> >wizard!  Good boy!  Here's your CPU crunchon snack'') you can hack in a
> >``lightly browned'' mode to do this.
> 
> Did they really take "litout" out of the 4.2BSD tty driver?

Depends on what you want.  You can get a full 8-bit path on OUTPUT with
flow control just by setting LITOUT.  You can get a full 8-bit path with
flow control on INPUT if you hack the driver a bit to support TANDEM
even in RAW mode.  But you cannot get an 8 bit data path in BOTH directions
with flow control at all, ever.  The problem is fundamental: if you
receive an XON or XOFF, how do you decide if it is part of the data or
a flow control instruction from the other machine?  You just cannot
transmit flow-control instructions along with all-256-codes-valid data
on the same wire without some sort of additional encoding being done.