Re: [RFC 09/10] hw/mos6522: Avoid using discrepant QEMU clock values

On Wed, 25 Aug 2021, Mark Cave-Ayland wrote: > On 24/08/2021 11:09, Finn Thain wrote: > > > mos6522_read() and mos6522_write() may call various functions to determine > > timer irq state, timer counter value and QEMUTimer deadline. All called > > functions must use the same value for the present

Re: [RFC 09/10] hw/mos6522: Avoid using discrepant QEMU clock values

On Tue, 24 Aug 2021, Philippe Mathieu-Daudé wrote: > On 8/24/21 12:09 PM, Finn Thain wrote: > > mos6522_read() and mos6522_write() may call various functions to determine > > timer irq state, timer counter value and QEMUTimer deadline. All called > > functions must use the same value for the pre

Re: [RFC 09/10] hw/mos6522: Avoid using discrepant QEMU clock values

On 24/08/2021 11:09, Finn Thain wrote: mos6522_read() and mos6522_write() may call various functions to determine timer irq state, timer counter value and QEMUTimer deadline. All called functions must use the same value for the present time. Signed-off-by: Finn Thain --- hw/misc/mos6522.c |

Re: [RFC 09/10] hw/mos6522: Avoid using discrepant QEMU clock values

On 8/24/21 12:09 PM, Finn Thain wrote: > mos6522_read() and mos6522_write() may call various functions to determine > timer irq state, timer counter value and QEMUTimer deadline. All called > functions must use the same value for the present time. > > Signed-off-by: Finn Thain > --- > hw/misc/mo

[RFC 09/10] hw/mos6522: Avoid using discrepant QEMU clock values

mos6522_read() and mos6522_write() may call various functions to determine timer irq state, timer counter value and QEMUTimer deadline. All called functions must use the same value for the present time. Signed-off-by: Finn Thain --- hw/misc/mos6522.c | 51 +---