Xref: utzoo comp.unix.internals:2528 comp.unix.programmer:1550 comp.unix.wizards:24823 comp.unix.questions:30308
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!cs.uoregon.edu!ogicse!zephyr.ens.tek.com!tektronix!percy!m2xenix!quagga!proxima!iosys!chris
From: chris@iosys.UUCP (Chris Martinus)
Newsgroups: comp.unix.internals,comp.unix.programmer,comp.unix.wizards,comp.unix.questions
Subject: Re: Hardware flow control for TTY ports under V.3
Message-ID: <899@iosys.UUCP>
Date: 11 Apr 91 14:32:29 GMT
References: <451@frcs.UUCP>
Distribution: comp
Organization: Io Systems (Pty) Ltd
Lines: 21

In article <451@frcs.UUCP>, paul@frcs.UUCP (Paul Nash) writes:
 > I think that I have a problem.  I need to talk from a TTY port on
 > a 386 Unix box (Intel V.3.2) to a device that does hardware flow
 > control.  The output port (currently) uses the FAS drivers, but
 > this software needs to be portable to machines that don't have
 > such luxuries.
 > 
 > When I openthe port, I use a TCSETA ioctl() to play with baud rates,
 > etc.  However, as far as I can tell, whether or not I set CLOCAL
 > (which is the only relevant looking flag that I can find), dropping
 > CTS doesn't halt the port.  What am I doing wrong?  Is there a 
 > hidden flag, or a hidden field in the termio struct, or a hidden
 > ioctl call?  Is there something else entirely that I should use for
 > this?  Is my break-out box broken?

Uuuh...  I dunno about V.3.2 of FAS drivers, but on V.4 if you want 
hardware flow control, use /dev/ttyhXX instead of /dev/ttyXX.  
Does this help at all?
-- 
Chris Martinus
chris@iosys