Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!network.ucsd.edu!swrinde!gatech!concert!sas!mozart.unx.sas.com!torpid.unx.sas.com!sastdr From: sastdr@torpid.unx.sas.com (Thomas David Rivers) Newsgroups: comp.unix.bsd Subject: Re: COM driver and X11 Keywords: COM X11 Message-ID: <Br2tDy.81s@unx.sas.com> Date: 8 Jul 92 15:22:46 GMT References: <cproto.710554678@marsh> Sender: news@unx.sas.com (Noter of Newsworthy Events) Organization: SAS Institute Inc. Lines: 22 Nntp-Posting-Host: torpid.unx.sas.com I also experience silo overflows; many of them went away with the process-level fixes (there is a bug where a driver sets the process-level high, and it never gets lowered, so *everything* runs at that level from then on.) Even with these fixes, I still get silo overflows at 9600 baud on a 20 MHZ 386 w/ 16550s. Implementing the COM driver as two "parts" is a good idea (it's what FAS does on SYS V). Be aware, however, that Chris (cgd@agate.berekley.edu) has a new version of the driver which implements bi-directional behaviour. You should base any of your work on his source. Let me know if you need a copy. - Dave Rivers - (work: sastdr@unx.sas.com) (home: rivers@ponds.uucp) <- preferred address -- UPDATE ALL INFORMATION AND POD INTO COSMOS - Federal Express