Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!headwall.Stanford.EDU!nntp.Stanford.EDU!leland.Stanford.EDU!yergeau From: yergeau@leland.Stanford.EDU (Dan Yergeau) Subject: Re: [Q] com1: silo owerflow and slip Message-ID: <1993Aug19.204243.25814@leland.Stanford.EDU> Sender: news@leland.Stanford.EDU (Mr News) Organization: DSG, Stanford University, CA 94305, USA References: <1993Aug19.135931.165@ebc.ee> <250bki$r9m@pdq.coe.montana.edu> Date: Thu, 19 Aug 93 20:42:43 GMT Lines: 20 In article <250bki$r9m@pdq.coe.montana.edu>, osyjm@cs.montana.edu (Jaye Mathisen) writes: |> It is odd that you're having problems at 9600 baud, I would'nt have guessed |> you'd have trouble on a 486 with 9600 baud. I used to have silo overflow problems with the stock com driver on a 486/33 with 16450's at 9600. They were very isolated, but just a couple can confuse even the best communication protocol. Haven't had a single serial communications problem since I went sio. Great job to everyone who was involved! Yes, I know that I should be using 16550As, but my UARTs aren't socketed (part of a integrated Multi-IO controller), and I haven't found an inexpensive (<$20) serial board with at least 1 16550A on it. -- Dan Yergeau You are in a twisty little passage yergeau@gloworm.Stanford.EDU of standards, all conflicting. #include <std.disclaimer>