Re: [hatari-devel] emutos-ram and GEMDOS drive emulation

[ Thread Index | Date Index | More lists.tuxfamily.org/hatari-devel Archives ]

To: hatari-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [hatari-devel] emutos-ram and GEMDOS drive emulation
From: Vincent Rivière <vincent.riviere@xxxxxxxxxxx>
Date: Mon, 7 Mar 2016 20:48:19 +0100
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=ErR31UXJ9kkko3QpNhSaXGqfApl84Ny7Nq5u4lEZl2k=; b=h9nc2DkE8hzfjv1VOLp3H5pLBFJ2vilx9sgbXOh02m2XRCUT3JF4WGgkwa51VyZtLL S240gFrgdMFNNmkx4oF9pyZ2kuVS46MoVLcElP9ClcjRwDdmcFHpaTNZUZrttyH/7okO Mmkln++8kRYfiKggvkmvgdNE6FRGvJc/EPpI03DUNCIjsR8tIDrkOpVoaOqqin1OOaVg do1w5Mj82ewRgJ87p+yNJRADoNTXxUHL+VHoPiuJHJpUWk1VwBiAQAmVLjR8UTvkVZxz OdLrc7+Ai0sy2tOQwKc6ShKD67OVbUKcv7lA6e1ThmffMIa7R8V/tQ3MBRZ5AaV/cDwK DAqQ==

On 07/03/2016 20:22, Eero Tamminen wrote:

[1] One reason why additional invocations are currently prevented
could be that invalid opcode may get triggered also by something
else (than cartridge code),

Similar example: When doing such traps, WinUAE checks that the originatingPC comes from the right ROM area. Hatari could do the same, and enable that$a trap only if it is originating from the cartridge, AND the actual mountedcartridge is Hatari's one.


--
Vincent Rivière

References:
- [hatari-devel] emutos-ram and GEMDOS drive emulation
  - From: Vincent Rivière
- Re: [hatari-devel] emutos-ram and GEMDOS drive emulation
  - From: Eero Tamminen

Messages sorted by: [ date | thread ]
Prev by Date: Re: [hatari-devel] emutos-ram and GEMDOS drive emulation
Next by Date: [hatari-devel] Compiler warnings
Previous by thread: Re: [hatari-devel] emutos-ram and GEMDOS drive emulation
Next by thread: Re: [hatari-devel] emutos-ram and GEMDOS drive emulation

Mail converted by MHonArc 2.6.19+

http://listengine.tuxfamily.org/