|[hatari-devel] NVRAM register handling, Hatari vs. Aranym|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
Because I got into debug log warnings about unimplemented NVRAM
registers 6 and 11 when booting Linux, I looked at Aranym's
Aranym has following differences to Hatari NVRAM register reads...
- 6: weekday
- 10: returns whole register value, not just UIP bit
- 11: clock mode bits (12/24h, BIN/BCD, clock set/freeze)
- 13: returns whole register value, not just 0x80
Do you see any problem if I would change things to behave like
(i.e. adding reg 11 mode bits and toggling/returning the NVRAM
registers 10 & 13 directly instead just the relevant bit?)
Neither EmuTOS nor real TOS read registers 6 & 11.
XCONTROL.ACC doesn't use registers 6 & 13.
It uses 11 though, setting it to 0x80, 0x8e and 0x8e.
In Aranym code, 0x80 is the clock set/freeze bit, 0x4 is BCD bit,
0x2 is 12/24h bit, but it doesn't implement 0x8 bit. Any idea
what that bit is for?
Aranym handled register 10 earlier like Hatari did, but Thorsten
changed it in at the same time he implemented register 11 support.
There was no comment why reg 10 was also changed.
Returning just 0x80 (valid RAM/time bit) from reg 13 is Hatari
specific, Aranym has never done that.