Path: utzoo!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!bagate!cbmvax!daveh From: daveh@cbmvax.commodore.com (Dave Haynie) Newsgroups: comp.sys.amiga.hardware Subject: Re: Need info about *DTACK generation Message-ID: <19942@cbmvax.commodore.com> Date: 18 Mar 91 18:13:17 GMT References: Reply-To: daveh@cbmvax.commodore.com (Dave Haynie) Organization: Commodore, West Chester, PA Lines: 31 In article root@apal.UUCP (Andreas Mueller) writes: >1. Where (memory locations) is ADG done? A500, A1000, and A2000 generate DTACK* automatically for every memory region except the chunk devoted to the CIA chips (8520s), which get VPA* instead. The A3000 doesn't automatically generate DTACK* (DSACK*) for any unused memory regions. Since the Zorro II bus always had DTACK* generated for it by the Amiga system logic in older system, automatic DTACK* is thus part of the Zorro II specification, and the A3000 generates it for all valid Zorro II locations. So, for anything you should be concerned about (eg, Zorro II expansion space), DTACK* is automatic in all Amigas. >2. How 'fast' is the *DATCK signal available? (is it delayed, or is it > >= *AS) ? In the 68000 based systems, DTACK* is based strictly on AS* for areas mapped for Zorro II expansion. On the A3000, DTACK* comes out during the S3 state of the Zorro II cycle, so that an expansion card can control or delay it (via OVR* or XRDY) without glitching it. In any case, these are implementation details; no hardware should count on when DTACK* is asserted. >3. Is there any difference in ADG, between the Amiga models (A1000 vs. A2000)? That's pretty much covered up above. >| Andreas Mueller (A1020:) | "Who left his footprints in my computercase?" | -- Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests" {uunet|pyramid|rutgers}!cbmvax!daveh PLINK: hazy BIX: hazy "What works for me might work for you" -Jimmy Buffett