🚀 go-pugleaf

Organization: Portal Communications Company
Summary: Looking for Suggestions for Flow Control for dp 2.3 on SunOS 4.1.3
Keywords: Dialup-PPP (dp 2.3) Flow Control on SunOS 4.1.3
ReplyTo: pete@west.darkside.com guest@shell.portal.com


Any suggestions on setting up dp 2.3 for SunOS 4.1.3 (currently without the
U1 Update) with a ZyXel U-1496E+?  Last year I was using a Supra V32Bis modem
and was having some problems with a previous release of dp. I was trying to
use hardware flow control and may have had problems with the Modem getting 
ahead of the zs driver and overflowing the silo or ring buffer. 

I just started playing around with this and tried software flow control 
while waiting for the PoP to exchange packets. I'm using the zs table hack 
to get 76.8k baud DTE rate to the modem. I believe im currently getting zs0 
silo overflows, so maybe 76.8k isn't a great idea without the U1 update. 

Can I just modify a few zs*.o files to get the RTS/CTS problems fixed?  
I looded at the 4.4BSD zs.c code but it wasn't clear why the RTS stuff 
wasn't working ok.  I heard from a Hacker that there is a small bug 
in the zs driver and that he hacked it to work correctly.  I wonder if 
this is part of the the U1 update for the zs driver.  

Also, I don't have Answerbook online or the manuals, I've forgotten the 
(RTSCTS) uucp hack to make the modem use Hardware FLow Control instead 
of software flow control. I recall it being (CRTSCTS) being in your 
UUCP {Dialers or Systems} files; that the setting of the boot
rom parameters on the SS1 (and the SS1+ I assume) are being ignored by the 
kernel. It seems the 4.4BSD code is concerned only with Output Flow Control:

        /*
         * Output hardware flow control on the chip is horrendous: if
         * carrier detect drops, the receiver is disabled.  Hence we
         * can only do this when the carrier is on.
         */ 

whereas I recall that the problems with the zs driver are with Input 
Flow Control. That if the modem get agead of the zs driver that the 
driver doens't stop the modem by deasserting RTS. Seems it should have 
been called "Clear to Receive". 

-pete