Sprinter/mame
2
0
Fork 0
mirror of https://github.com/holub/mame synced 2025-05-20 20:58:51 +03:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #5455 from tyfighter/master

Browse Source 
wd33c9x - clarify hardware reset
This commit is contained in:
R. Belmont 2019-08-10 07:59:25 -04:00 committed by GitHub
commit 5cdfb33855
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
src/devices/machine/wd33c9x.cpp
View File

@ -415,6 +415,8 @@ void wd33c9x_base_device::device_start()
void wd33c9x_base_device::device_reset()
{
// This is a hardware reset. Software reset is handled
// under COMMAND_CC_RESET.
scsi_bus->ctrl_w(scsi_refid, 0, S_ALL);
scsi_bus->ctrl_wait(scsi_refid, S_SEL|S_BSY|S_RST, S_ALL);
m_addr = 0;
@ -433,6 +435,10 @@ void wd33c9x_base_device::device_reset()
m_irq_cb(CLEAR_LINE);
m_drq_cb(CLEAR_LINE);
m_drq_state = false;
// Hardware reset triggers a SCSI_STATUS_RESET interrupt.
irq_fifo_push(SCSI_STATUS_RESET);
update_irq();
}
@ -668,13 +674,7 @@ WRITE_LINE_MEMBER(wd33c9x_base_device::reset_w)
{
if (state) {
LOGMASKED(LOG_LINES, "Reset via MR line\n");
// FIXME: hardware reset is not the same as software reset, and
// wd33c93a behaves differently to wd33c93
device_reset();
// hardware reset produces an interrupt
m_regs[AUXILIARY_STATUS] |= AUXILIARY_STATUS_INT;
m_irq_cb(ASSERT_LINE);
}
}