|Re: [hatari-devel] FPU detection, who is wrong?|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
Am Mon, 21 Sep 2015 13:14:06 +0200
schrieb Miro Kropáček <miro.kropacek@xxxxxxxxx>:
> On Tue, Feb 17, 2015 at 10:56 AM, Thomas Huth <th.huth@xxxxxx> wrote:
> > > I have a 68881 in my MegaSTE, for instance.
> > Any chance that you can try to find out the revision value of the
> > 68881 that is put on the stack by the FSAVE instruction?
> Accidentally, I've gotten hold of two MegaSTEs, one with a 68881 and
> another with a 68882 so why not to give it a try?
> Not only it has proved that the current FreeMiNT kernel (since the 31
> of May) is working well with peripheral FPUs now but also a couple of
> interesting numbers:
> - the 68881 indeed reports revision number as 0x3f (and frame size =
Thanks for the test, Miro! As far as I can see, WinUAE (and thus also
Hatari) uses 0x1f as revision number for the 68881 now ...
Question for Toni: Shall we switch to 0x3f instead?