Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!sun-barr!texsun!texbell!uhnix1!sugar!karl
From: karl@sugar.hackercorp.com (Karl Lehenbauer)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Blitter Operation
Summary: floppy drive implications for precision realtime tasks?
Message-ID: <3854@sugar.hackercorp.com>
Date: 23 May 89 01:19:46 GMT
References: <8905132203.AA27784@postgres.Berkeley.EDU> <17209@usc.edu> <6542@ardent.UUCP>
Organization: Sugar Land Unix - Houston
Lines: 15

In article <6542@ardent.UUCP>, rap@rap.ardent.com (Rob Peck) writes:
> As I remember it, the blitter is quite capable of using EVERY cycle.
> It only takes a back seat if it senses that some other DMA is pending.
> The 68000 gets locked out of most cycles when the blitter is running,
> though the blitter "stutter-stops" to give the 68000 occasional access,
> then immediately grabs the bus again after single cycles are granted.

Could this explain why my SMUS player "stutter-plays" anytime floppy
activity is going on, but not during hard disk activity?  That the
blitter is used to decode the data read off the floppy and the blitter
locks the CPU out for a relatively long time (a few ms would be enough)?

-- 
-- uunet!sugar!karl  | "Nobody hipped me to that, dude." -- Pee Wee
-- Usenet BBS (713) 438-5018