Re: [hatari-devel] 68040/68060, external FPU? |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] 68040/68060, external FPU?
- From: Thomas Huth <th.huth@xxxxxxxxx>
- Date: Sun, 13 Jul 2025 11:22:11 +0000
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=posteo.de; s=2017; t=1752405732; bh=LTAG6qMsU6c/Td+QeWFrTK0Zt534EJhXBJBiO64VGCw=; h=Date:From:To:Subject:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding:From; b=lVWosIw25SCtsLNtOOmxeLDgD3Hk1AJU2CQYjE6aO3E6BXY4NYQjxcSYHkX7UnSYR bCPdgpZxaW9T8soEbg2XH3NzcmybVyD9Y55QV5e45nfHmLOUuabSpS3syaX7NGhh6l kfcJn41fcZEhtQJR9wQK1cvPCfWJzZ2mBVl4ruclBbLS5SOMe6uLHZ3RrvU/tdfTe+ ZTsKxO50amjuWOBzMLKCc9jsCOqDHPJPK/eHmSG+ZHi6p54HQMe4MvILaQ+FS32f09 SdhjNtpp9W5nHCMvkqGXI0JGCEfIaKNZvqi3bKXAP5lUtLfx06U4ZOLD+6RsAR+g+L z/fItyno88Lqw==
Am Wed, 9 Jul 2025 13:26:44 +0200
schrieb Uwe Seimet <Uwe.Seimet@xxxxxxxxx>:
> > it all depends if we speak of FPU as a logic part of the setup, ie sthg
> > that can do floating point or as a real stand alone HW component.
> >
> > In all cases, the cpu core from WinUAE can have the following values for
> > fpu_model : 68881, 68882, 68040 and 68060.
> >
> > and in M68000_CheckCpuSettings() we already warn if user chooses fpu
> > internal for cpu <= 030. Maybe a similar warning would be needed if
> > user chooses fpu 68881/82 (ie not internal) on cpu >= 040.
>
> Either that, or enable/disable invalid items in the dialog as soon as the
> user selects a CPU. Preventing the user from selecting invalid settings
> is better than later saying "sorry, your selection is invalid, please try
> again".
I've checked the Motorola user manuals for the 68040 and 68060, and it
indeed sounds like the 68LC040 and 68LC060 cannot deal with external FPUs
anymore. So I now reworked the code in M68000_CheckCpuSettings() to switch
to the internal FPU in that case instead (since that's the closest config
to what the user selected).
It's not as good as disabling the entries in the GUI actively, but
considering that we have multiple GUIs (SDL, macOS, Python), and CLI and
config file to change these options, having this in a central place in
M68000_CheckCpuSettings() is still the best maintainable way.
Thomas