Return to BSD News archive
Xref: sserve comp.os.386bsd.development:1724 comp.sys.ibm.pc.hardware.chips:1961 comp.periphs:4951 Newsgroups: comp.os.386bsd.development,comp.sys.ibm.pc.hardware.chips,comp.periphs From: fred@genesis.demon.co.uk (Lawrence Kirby) Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!decwrl!nic.hookup.net!swrinde!cs.utexas.edu!howland.reston.ans.net!pipex!demon!dis.demon.co.uk!genesis.demon.co.uk!fred Subject: Re: The DMA problem again! References: <jmonroyCJxHBH.2x0@netcom.com> <1994Jan22.120513.8484@cc.usu.edu> <jmonroyCK4tFo.3Jx@netcom.com> <CK5AoL.6LL@ucdavis.edu> Organization: none Reply-To: fred@genesis.demon.co.uk X-Newsreader: Demon Internet Simple News v1.27 Lines: 18 Date: Mon, 24 Jan 1994 23:43:19 +0000 Message-ID: <759454999snz@genesis.demon.co.uk> Sender: usenet@demon.co.uk In article <CK5AoL.6LL@ucdavis.edu> fzshenau@dale.ucdavis.edu "Greg Shenaut" writes: . . >Now the _probability_ of this kind of delay occuring as a result of a >refresh cycle is much lower due to the low frequency of refresh cycles, >but I think that it may be _possible_. It depends how long a refresh cycle can tie up the bus. It seems to be a general thing that bus master controllers stop interfering with floppy transfers when you reduce the bus-on time to about 7us or less. I would have thought a refresh cycle would be much shorter than this. ----------------------------------------- Lawrence Kirby | fred@genesis.demon.co.uk Wilts, England | 70734.126@compuserve.com -----------------------------------------