From owner-freebsd-hackers  Thu Jun 26 19:06:52 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id TAA27875
          for hackers-outgoing; Thu, 26 Jun 1997 19:06:52 -0700 (PDT)
Received: from spoon.beta.com (root@[199.165.180.33])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA27840
          for <hackers@freebsd.org>; Thu, 26 Jun 1997 19:06:32 -0700 (PDT)
Received: from spoon.beta.com (mcgovern@localhost [127.0.0.1])
	by spoon.beta.com (8.8.5/8.8.5) with ESMTP id WAA15211
	for <hackers@freebsd.org>; Thu, 26 Jun 1997 22:06:29 -0400 (EDT)
Message-Id: <199706270206.WAA15211@spoon.beta.com>
To: hackers@freebsd.org
Subject: XON/XOFF intrusion...
Date: Thu, 26 Jun 1997 22:06:28 -0400
From: "Brian J. McGovern" <mcgovern@spoon.beta.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I'm having a problem with a driver where XON and XOFFs are being introduced
to the data stream, even when I have IXON, IXOFF, and IXANY turned off
in c_iflag. I'm trying to track down the introduction of the spurious data,
and I just wanted to know if ttyblock() is the only function that will do this,
or if there are others that might behave this way. This way, I can look for 
calls to ttyblock() and see on what conditions it gets called. 

I know (through programming and printf()s) that c_iflag has the above
mentioned bits off, and that ((tp->t_rawq + tp->t_canq) < (TTYHOG / 2)).

If anyone who is familiar with this code has any comments or suggestions, I'd
appreciate it :)
	-Brian