Date: Tue, 4 Mar 1997 10:14:58 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: msmith@atrad.adelaide.edu.au (Michael Smith) Cc: terry@lambert.org, msmith@atrad.adelaide.edu.au, hackers@FreeBSD.org, jrb@cs.pdx.edu Subject: Re: [driver testing] Odd network behaviour? Message-ID: <199703041714.KAA09946@phaeton.artisoft.com> In-Reply-To: <199703040020.KAA08716@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Mar 4, 97 10:50:03 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > Kurt Mahon, who wrote the driver for the 82586 for USL, claimed that > > the USL driver copied the data twice; apparently, the interrupt was > > issued when data was available, rather than when it had made it into > > card memory? > > This is a most extremely bizarre claim. AFAIK, the '586 doesn't issue > an interrupt until the DMA into the host memory has completed, which has to > happen as the frame arrives as (again from memory) it doesn't have a very > big internal FIFO. > > *grumble* Well, you'll note the quetion mark... that's the reasoning I remember being given. I also rememeber SVR4.0.2 running fine on the cards on the 6386/33E's, but failing to work for 386BSD (up through FreeBSD). Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703041714.KAA09946>