From owner-freebsd-hardware Tue Jul 2 10:25:11 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA23934 for hardware-outgoing; Tue, 2 Jul 1996 10:25:11 -0700 (PDT) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA23921 for ; Tue, 2 Jul 1996 10:25:07 -0700 (PDT) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0ubAhe-000x08C; Tue, 2 Jul 96 12:01 PDT Received: from cc:Mail by ccgate.infoworld.com id AA836328145; Tue, 02 Jul 96 10:32:07 PST Date: Tue, 02 Jul 96 10:32:07 PST From: "Brett Glass" Message-Id: <9606028363.AA836328145@ccgate.infoworld.com> To: Bruce Evans , bde@zeta.org.au, hdalog@zipnet.net, msmith@atrad.adelaide.edu.au Cc: Kevin_Swanson@BLaCKSMITH.com, chuckr@glue.umd.edu, freebsd-hardware@FreeBSD.org, jparnas@jparnas.cybercom.net Subject: Re: muliport boards - building a PPP dialup server Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > If the UART's fifo is larger than about 128, then the pseudo-dma buffers > won't be able to take all the input. Flow control may fix the problem in > practice (just like it does for a modem with a bug buffer connected to a > UART with a small fifo). This brings up a problem I'd forgotten about: slow modem response to flow control signals. Often, the modem's internal firmware gives flow control such a low priority that several hundred characters can escape before a dropped "Clear to Send" signal is recognized. A UART with a big FIFO can help, especially if the UART does not have automatic flow control. --Brett