Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!apple!voder!pyramid!cbmvax!steveb
From: steveb@cbmvax.commodore.com (Steve Beats)
Newsgroups: comp.sys.amiga.tech
Subject: Re: 2630 Data Cache
Message-ID: <10158@cbmvax.commodore.com>
Date: 14 Mar 90 10:29:21 GMT
References: <345@hawk.isc-br.com> <10121@cbmvax.commodore.com>
Reply-To: steveb@cbmvax (Steve Beats)
Organization: Commodore, West Chester, PA
Lines: 21

In article <10121@cbmvax.commodore.com> daveh@cbmvax (Dave Haynie) writes:
>Flushing of the cache to support DMA belongs in the device driver.  If
>that's what's tripping up Blink, its not a Blink problem.  Under 1.3,
>there's no standard way of doing cache flush, so most device drivers
>(including those from Commodore) don't do this.

Ahem, actually Dave, the A2091 does flush the data and instruction caches
if an 030 is present in the system.  It`s a bit drastic but there is no
system supported way of finding out exactly what memory areas are cached,
so the whole lot has to go.  I don`t think there`s any way of determining
what`s been cached, even in hardware, is there ?

	Steve


-- 
  _________________
 / __	    __	   \	Commodore/Amiga Inc.	|       This space left
( (__'	   |__)	    )	Email:	cbmvax!steveb	|        intentionally
( ,__)teve |__)eats )	BIX:	sbeats		|           blank!
 \_________________/	PHONE:	(215) 431-9100	| 01144 482 824141 (UK phone)