diff options
author | AJR <ajrhacker@users.noreply.github.com> | 2018-05-18 13:32:56 -0400 |
---|---|---|
committer | AJR <ajrhacker@users.noreply.github.com> | 2018-05-18 13:40:29 -0400 |
commit | 0ba652e723036746aa1b1ac665411bee83771654 (patch) | |
tree | ba3cf42c70bf33ad22c07ad85b9d41f863a373e7 /src/mame/drivers/pcw16.cpp | |
parent | e5dc17a4881d2b9ce4573b42d825cb6456bf529c (diff) |
diexec: Interrupt API changes (nw)
- PULSE_LINE is no longer a value. Existing uses have been changed to pulse_input_line with attotime::zero as the second argument.
- Formerly only INPUT_LINE_NMI and INPUT_LINE_RESET were allowed with PULSE_LINE. INPUT_LINE_NMI no longer receives special handling; instead, CPU devices must specify which of their input lines are edge-triggered and thus may be used with zero-width pulses by overriding the execute_input_edge_triggered predicate. INPUT_LINE_RESET is still special-cased, however.
- execute_default_irq_vector now allows a different default vector to be specified for each input line. This added flexibility may or may not prove useful.
Diffstat (limited to 'src/mame/drivers/pcw16.cpp')
-rw-r--r-- | src/mame/drivers/pcw16.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/mame/drivers/pcw16.cpp b/src/mame/drivers/pcw16.cpp index 50cf454a176..558d1742888 100644 --- a/src/mame/drivers/pcw16.cpp +++ b/src/mame/drivers/pcw16.cpp @@ -750,7 +750,7 @@ void pcw16_state::trigger_fdc_int() { /* I'll pulse it because if I used hold-line I'm not sure it would clear - to be checked */ - m_maincpu->set_input_line(INPUT_LINE_NMI, PULSE_LINE); + m_maincpu->pulse_input_line(INPUT_LINE_NMI, attotime::zero); } } } |