Re: L68K: Re: Afterburner and Linux

From: Frank Naumann <fnaumann_at_prinz-atm.cs.Uni-Magdeburg.DE>
Date: Mon, 8 Jun 1998 12:29:14 +0200 (MESZ)

Hi Doug!

> No, because there is absolutely no reason you would want your registers to
> be cacheable - they are *always* noncacheable. Cacheable registers = totally
> inoperable Falcon. The TK makes all hardware registers non-cacheable by
> default. They are also serialized, to ensure write-sequences are not
> interfered
> with.

Ok, fine. If thought some registers are cacheablke by default.

> >Yes, but I have problems with XHDI if caches are on. XHDI doesn't work
> >correctly (some operations, XHDosLimits for example) if the data cache is
> >on.
> DMASNOOP will mark all STRam from itself upwards, so if it doesn't help,
> then the program must be using STRam allocated BEFORE DMASNOOP
> was executed. That means it's ram allocated by an earlier program - which
> in turn means it's probably a FRB or something installed very early in the
> boot sequence.

Yes, that's clear.
> Look for an XFRB cookie. If it exists, try to remove it and reboot. See if
> the _FRB

I don't have an XFRB cookie.

> cookie installed by the TK will work on it's own. That uses non-cacheable
> and should therefore be safe. So long as XHDI recognises and uses it after
> TK
> is installed. You may have to re-run XHDI after TK to get it to 'see' the
> buffer.

So the problem is, that I auto boot with HDDriver.
And the problem isn't solved bye:

Auto folder:



A solution for me is, to auto boot with AHDI (for example) and run HDDriver
after DMASNOOP in the Auto folder?


Mausnet:  Frank Naumann _at_ L2                 
Received on ma. juni 08 1998 - 18:35:00 CEST

This archive was generated by hypermail 2.3.0 : ti. nov. 03 2015 - 20:07:54 CET