summaryrefslogtreecommitdiffstatshomepage
diff options
context:
space:
mode:
-rw-r--r--src/mess/drivers/ti99_4x.c4
-rw-r--r--src/mess/machine/ti99/videowrp.c4
2 files changed, 7 insertions, 1 deletions
diff --git a/src/mess/drivers/ti99_4x.c b/src/mess/drivers/ti99_4x.c
index f0dd558779d..4b3bf30791a 100644
--- a/src/mess/drivers/ti99_4x.c
+++ b/src/mess/drivers/ti99_4x.c
@@ -647,6 +647,10 @@ INPUT_CHANGED_MEMBER( ti99_4x_state::load_interrupt )
Links to external devices
***********************************************************/
+// FIXME: The sound chip is one of the devices that may operate the ready line
+// at some later time and thus mess up the READY handling (raises the READY
+// line without bothering about the rest). We need to do a proper AND here.
+
/*
We may have lots of devices pulling down this line; so we should use a AND
gate to do it right. On the other hand, when READY is down, there is just
diff --git a/src/mess/machine/ti99/videowrp.c b/src/mess/machine/ti99/videowrp.c
index 5a17ee06f67..eaa5e6b2fc7 100644
--- a/src/mess/machine/ti99/videowrp.c
+++ b/src/mess/machine/ti99/videowrp.c
@@ -211,7 +211,9 @@ void ti_sound_system_device::device_start(void)
WRITE_LINE_MEMBER( ti_sound_system_device::sound_ready )
{
- m_console_ready(state);
+ // Need to disable this until READY handling is properly implemented in the sound chip
+ // and in the console (otherwise external speech like in Parsec will be interrupted)
+ //m_console_ready(state);
}
MACHINE_CONFIG_FRAGMENT( sn94624 )