Re: [hatari-devel] Error in SetClock / ReadClock

[ Thread Index | Date Index | More Archives ]


Happy new year from my side, too!

Am Thu, 03 Jan 2013 00:19:23 +0100
schrieb Nicolas Pomarède <npomarede@xxxxxxxxxxxx>:
> Hopefully, 2013 will be the year when IKBD gets fixed once and for
> all :)

I am pretty sure it will :-)

> I made an error while changing the ACIA/IKBD serial interface,
> because I assumed the IKBD's ROM would not handle receiving a new
> command while already sending the packet of the current command.
> That's why in the case of Zombi the getclok command was ignored at
> one point when the IKBD had some automatic mouse events to report.

Confirmed, Zombi is working fine now.

> In Hatari, we have a 1024 byte output buffer, this is much more than
> the real IKBD's one. It should not give any problem to store more
> bytes. Only in the case where the buffer is full, we can see a longer
> latency when pressing 'fire' during the title screen in Fokker for
> example. This is because we need to flush 1024/3 joystick reports
> before sending the 3 byte packet where fire button is pressed.

Is there a good reason to keep this big output buffer? I think we
might just have used this in the past to workaround other bugs that
should be fixed now. Have you tried to change it to the same size as the
real IKBD output buffer?

> I tested Downfall, Fokker, Zombi and Captain Blood with those 
> modifications, everything seems fine (I think XCONTROL should work
> too).

I justed tested XCONTROL, and it is working fine now. Thanks!


Mail converted by MHonArc 2.6.19+