mirror of
https://github.com/holub/mame
synced 2025-04-22 00:11:58 +03:00
There is no reset input, so resetting the status of the variable tracking the external signal makes no sense. However we should probably restart the timer on all resets (instead of just at start/watchdog timeout), to avoid a watchdog reset if you press F3 at the wrong time (nw)
This commit is contained in:
parent
fa05df5922
commit
0bbb5496ba
@ -42,7 +42,6 @@ mb3773_device::mb3773_device( const machine_config &mconfig, const char *tag, de
|
||||
void mb3773_device::device_start()
|
||||
{
|
||||
m_watchdog_timer = timer_alloc();
|
||||
reset_timer();
|
||||
|
||||
save_item( NAME(m_ck) );
|
||||
}
|
||||
@ -54,7 +53,7 @@ void mb3773_device::device_start()
|
||||
|
||||
void mb3773_device::device_reset()
|
||||
{
|
||||
m_ck = 0;
|
||||
reset_timer();
|
||||
}
|
||||
|
||||
void mb3773_device::device_timer(emu_timer &timer, device_timer_id id, int param, void *ptr)
|
||||
@ -66,8 +65,6 @@ void mb3773_device::device_timer(emu_timer &timer, device_timer_id id, int param
|
||||
#else
|
||||
machine().schedule_soft_reset();
|
||||
#endif
|
||||
|
||||
reset_timer();
|
||||
}
|
||||
|
||||
void mb3773_device::reset_timer()
|
||||
|
Loading…
Reference in New Issue
Block a user