|Re: [hatari-devel] Falcon raster emulation|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Falcon raster emulation
- From: Douglas Little <doug694@xxxxxxxxxxxxxx>
- Date: Thu, 12 Dec 2013 09:59:07 +0000
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=EQOEiKImxzfxU04nRB0DTdoLrXjJAZMm+xZSoqd+Sy8=; b=RbK5r8ohnXtZa3scmmXSqqzzdlSyplsB65CqOWtB2+COLoUpzQi4Xm8oe744rdLY48 ukOwAn6VMVAiF/VIO2+lg2Kp5GJDkIL6D68eNhpwh3ojUEhqPHl05vNMA591krHgAFo0 OyoK81AkExYrbGkLQYsXhdM5pPURm7GuqouOLHcNljJHdRo8HCpWC6NMDYAnfZo22eIa 4bxxgF62mY4BaBiKmw1dDNHzYy1T5t+jUaJRRrjI5g1+G2GbMFBn0pKadLF1sVRoHaBK mfA3K17wsAPsgKySLeSknXkpXo9sxHPjt1/+QJtT9XQCQ78F5slzlsZyAw7bwDssGCrG LyxQ==
Yes I think it would be enough to emulate effects which would still work with different CPU speeds. I don't think many Falcon coders actually depended on exact 16mhz performance of the CPU (since that was nearly impossible anyway with all the strange stuff going on inside the machine - and many machines are accelerated in some way). So just MFP and some Videl state (like palette) effects would cover a lot of useful things.
I think any code which attempts to race the beam with CPU cycles is going to soon fail on a real machine anyway.
The real problem is perhaps interfacing with the CPU core as the 'clock master' when it should probably be a slave to a system clock structure of some kind (which also drives MFP and display timing). The CPU timings are actually much less important in the real world. The actual changes involved and amount of work though - I have no idea... possibly quite a lot!
I think 'limited' scanline-level effects and TT ram are my two top Hatari requests at the moment :)