Re: [hatari-devel] IDE IO register range access commit

[ Thread Index | Date Index | More Archives ]

Afaik, all IDE interfaces for Atari machines are Falcon-compatible w.r.t. to the address range, i.e. 0xF000xx. There are 3rd-party IDE interfaces for the ST (Lightning ST, MonSTer, ...), STe (MonSTer, ...), TT (Thunder) that use this address range. So does the builtin IDE in the ST Book.
Therefore, I agree with Eero that there should be no bus error (i.e. IDE should be emulated) regardless of the machine, and not only on Falcon.
Gesendet: Montag, 21. September 2020 um 15:24 Uhr
Von: "Nicolas Pomarède" <npomarede@xxxxxxxxxxxx>
An: hatari-devel@xxxxxxxxxxxxxxxxxxx
Betreff: Re: [hatari-devel] IDE IO register range access commit
Le 21/09/2020 à 15:16, Eero Tamminen a écrit :
> Hi Nicolas,
> In your IDE IO register range access commit:
> I think your check should be for IDE being enabled:
> (ConfigureParams.Ide[0].bUseDevice || ConfigureParams.Ide[1].bUseDevice))
> Not for Falcon.
> For example, Linux doesn't seem to work with ACSI,
> and Hatari SCSI emulation isn't complete enough,
> so I need to use IDE disk image to test m68k Linux
> with TT emulation.


OK, I can change the test.

> Aren't there also IDE boards for other machines
> than Falcon?

Maybe, I'm not familiar with this. But the point is not really if
there're IDE boards, but what IO memory region they use to be accessed.

The lower 0x40 bytes of 0xF0xxxx are supposed to be enabled only in case
Falcon's IDE.

If a board use different addresses to be accessed, then it's another matter.



Mail converted by MHonArc 2.6.19+