ay8910: Rename write handler, as it's not that most common setup

This commit is contained in:
Dirk Best 2017-03-05 18:55:30 +01:00
parent 74a20c57bd
commit 7a2c159724
3 changed files with 7 additions and 6 deletions

View File

@ -1119,7 +1119,8 @@ WRITE8_MEMBER( ay8910_device::data_w )
#endif
}
WRITE8_MEMBER( ay8910_device::write )
// here, BC1 is hooked up to A0 on the host and BC2 is hooked up to A1
WRITE8_MEMBER( ay8910_device::write_bc1_bc2 )
{
switch (offset & 3)
{

View File

@ -1,4 +1,4 @@
// license:BSD-3-Clause
// license:BSD-3-Clause
// copyright-holders:Couriersud
#pragma once
@ -127,7 +127,7 @@ public:
DECLARE_WRITE8_MEMBER( address_data_w );
// bc1=a0, bc2=a1
virtual DECLARE_WRITE8_MEMBER(write);
DECLARE_WRITE8_MEMBER(write_bc1_bc2);
void set_volume(int channel,int volume);
void ay_set_clock(int clock);
@ -230,7 +230,7 @@ public:
/* AY8914 handlers needed due to different register map */
DECLARE_READ8_MEMBER( read );
virtual DECLARE_WRITE8_MEMBER( write ) override;
DECLARE_WRITE8_MEMBER( write );
};
extern const device_type AY8914;

View File

@ -128,7 +128,7 @@ static ADDRESS_MAP_START( sub_map, AS_PROGRAM, 8, popper_state )
AM_RANGE(0x0000, 0x1fff) AM_ROM
AM_RANGE(0x2000, 0x7fff) AM_NOP
AM_RANGE(0x8000, 0x8003) AM_MIRROR(0x1ffc) AM_WRITE(ay1_w)
AM_RANGE(0xa000, 0xa003) AM_MIRROR(0x1ffc) AM_DEVWRITE("ay2", ay8910_device, write)
AM_RANGE(0xa000, 0xa003) AM_MIRROR(0x1ffc) AM_DEVWRITE("ay2", ay8910_device, write_bc1_bc2)
AM_RANGE(0xc000, 0xdfff) AM_RAM AM_SHARE("ram")
AM_RANGE(0xe000, 0xffff) AM_NOP
ADDRESS_MAP_END
@ -380,7 +380,7 @@ WRITE8_MEMBER( popper_state::ay1_w )
m_ay[1]->reset();
}
m_ay[0]->write(space, offset, data);
m_ay[0]->write_bc1_bc2(space, offset, data);
}