Hi Doug!
Thank you for your response :-)
> >Yes, I agree. I chatted with Uwe Seimet and he mean something like that
> >(I don't know exactly). This is also the problem why logging SCSI-drives
> >at bootup only works with data cache off.
>
>
> It seems that whatever HDDriver is doing during SCSI logging, the problem
> is simply due to the CPU cacheing stale data.
>
> That means it's either hardware registers being cached - which should not
> be possible so long as they lie in the usual address space for hardware
Can this configured by TK?
> (the top 1mb or so of the address space), or HDDriver is using DMA to get
> information from the SCSI device, and the DMA operation is taking place
> in some area of cacheable ST-ram. I think the latter is likely. In which
> case,
> HDDriver should deal with it by making sure the caches are off during the
> logging process.
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.
Auto-Folder:
TK
DMASNOOP
HDDRIVER
doesn't help. If data cache is on (after boot) and I use XHDosLimits
something goes *very* wrong.
Tschuess
...Frank
--
ATARI FALCON 040
--------------------------------------
Internet: fnaumann_at_cs.uni-magdeburg.de
Mausnet: Frank Naumann _at_ L2
Received on ma. juni 08 1998 - 18:34:00 CEST