Re: [hatari-devel] Hatari/TT VME adress space behavior

[Uwe Seimet <Uwe.Seimet@xxxxxxxxx>]

I can not test this right now but only later. But TT and MegaSTE have different VME address regions, haven't they? For the MegaSTE it's Ox00FBxxxxx or something similar. Therefore, your patch may only work for the TT.

Best regards

Uwe

Am 19.07.2025 12:07 schrieb Nicolas Pomarède <npomarede@xxxxxxxxxxxx>:

Le 08/07/2025 à 10:14, Nicolas Pomarède a écrit :
> Le 08/07/2025 à 10:12, Uwe Seimet a écrit :
>> Hi,
>>
>>> although some changes for SCU support can be seen as related to the VME
>>> bus and its registers, Hatari does in fact very little regarding VME
>>> itself, so it's quite possible it doesn't behave similarly to a real TT
>>> as you describe.
>>>
>>> But using reports as yours comparing real TT to emulation, it should be
>>> possible to improve this, especially returning bus error should not be
>>> too difficult (as Hatari doesn't support VME card emulation)
>>
>> Any chance to get this implemented/fixed? After looking at the sources I
>> do not know how to do this, but maybe for somebody who has more
>> insight it
>> is just a minor effort?
>>
>
> Hi
>
> it seems I lost track of this mail after the discussion went on DKIM /
> mails problem.
> I will add this to my todo list
>

Hi

can you try the attached patch on top of the current git devel version
of hatari ?

it should return bus error when accessing $FExxxxxx regions in MegaSTE
and TT mode.

Nicolas