From 55489cae96fc3c280dd05bb98f87095f682ac347 Mon Sep 17 00:00:00 2001 From: Antonio Vivace Date: Fri, 16 Feb 2024 12:19:11 +0100 Subject: [PATCH] Update src/Timer_Obscure_Behaviour.md Co-authored-by: Eldred Habert --- src/Timer_Obscure_Behaviour.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/Timer_Obscure_Behaviour.md b/src/Timer_Obscure_Behaviour.md index ddfb7fd9..ca01966e 100644 --- a/src/Timer_Obscure_Behaviour.md +++ b/src/Timer_Obscure_Behaviour.md @@ -40,7 +40,7 @@ Notice how the bits themselves are connected to the multiplexer and then to the - On monochrome consoles, disabling the timer if the currently selected bit is set, will send a "Timer tick" once. This does not happen on Color models. - On Color models, a write to `TAC` that fulfills the previous bullet's conditions *and* turns the timer on (it was disabled before) may or may not send a "Timer tick". - This depends on a race condition, so it is device-dependent. + The exact behaviour varies between individual consoles. ## Timer overflow behavior