Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.bugs.4bsd
Subject: Re: Problems with a dmf-device (BSD4.3)
Message-ID: <13339@smoke.BRL.MIL>
Date: 11 Jul 90 19:49:21 GMT
References: <522@bsiao.UUCP> <13144@cbmvax.commodore.com>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 10

In article <13144@cbmvax.commodore.com> grr@cbmvax (George Robbins) writes:
>This isn't unusual - the dmf32 has a fairly small input buffer (silo) and the
>750 probably can't keep up to incoming bursts.

It ought to be able to, though.  My DZ-11 driver was able to keep up on
a PDP-11/34.  Perhaps the driver is not peeking to see if there is
additional input before resuming from a DMF interrupt?  Note that some
interfaces require time for the silo to "settle" when an incoming byte
is removed, and the driver should be sure to not peek before the
settling time.  This problem seems fixable to me.