*BSD News Article 18976


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!hp9000.csc.cuhk.hk!saimiri.primate.wisc.edu!sdd.hp.com!math.ohio-state.edu!howland.reston.ans.net!noc.near.net!uunet!mcsun!sun4nl!tuegate.tue.nl!svin09.info.win.tue.nl!wzv.win.tue.nl!gvr.win.tue.nl!guido
From: guido@gvr.win.tue.nl (Guido van Rooij)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: Working bidir support for sio driver?
Date: 28 Jul 1993 20:07:27 GMT
Organization: Eindhoven University of Technology, The Netherlands
Lines: 55
Message-ID: <236m9v$orh@wzv.win.tue.nl>
References: <1993Jul27.045051.215@k8lt.ampr.org>
NNTP-Posting-Host: gvr.win.tue.nl

glg@k8lt.ampr.org (Gary L. Grebus) writes:

>Does anyone have patches that fix the patchkit 0.2.4 sio driver to actually
>work in bidirectional mode?  The cgd bidir com driver worked reliably
>at patchkit 0.2.2.  Since that driver didn't seem to work at pk 0.2.4,
>I've tried to use the "official" driver, without much success.  The problems
>include:
>	
>    No ports at all seen with an AST/4 board installed (Wilko Bulte's patch
>    fixed this, but why is the probe routine less robust than it
>    used to be?)
>	
Simply because the probing is done for siungle port cards only. I ported
bidir support in it + the multiport things. I sent out the patches to a 
numbre of ppl and did not hear anything back. So I assumed it was okay.
(don't flame please....)
It will be fixed soon.

>    DTR not dropped long enough when a dialout closes the port. I've been
>    able to work around this.
It will be fixed soon.

>    When dialout closes the port, the pending open seems to complete
>    (getty goes from sleeping on comdcd to ttyin).
This is the same bug: DTR should be held down long enough for the modem
to disconnect ( and thus drop the carrier).

>    Driver seems to sometimes miss modem state changes (getty sleeping
>    on comdcd even though the modem has raised carrier detect).
???? Please be more specific. This is something I havent seen before.

>    The line (or getty) intermittantly gets into a state such that a dialin
>    gets a garbled login message (like wrong baud rate/parity etc).
>    Killing /restarting getty doesn't help.  Trying different parity,
>    character size, stop bits doesn't help either.
Also unknown to me.

>    Serial mouse no longer works (appears totally dead).  
Is it recognised on boot? 

>I've been attempting to fix some of this, without much success.  Anybody
>have any ideas before I roll back to a previous patchkit level?
In a few days I'll post some patches. You'd beter wait untill then.

>	/gary
>-- 
>Gary L. Grebus, 16 North Mason Rd., Brookline, NH  03033-2452
>Home:  glg@k8lt.ampr.org  (decvax!balrog!glg)
>Work:  grebus@isis1.enet.dec.com
>Ham Packet: K8LT @ WA1PHY.MA
-- 
Guido van Rooij                 |  Internet: guido@gvr.win.tue.nl
Bisschopsmolen 16               |  Phone:    ++31.40.461433
5612 DS Eindhoven               |  ((12+144+20)+3*sqrt(4))/7 
The Netherlands                 |    +(5*11)=9^2+0