Minor cleanups, ACCESSING_BITS cleanups, Fix spacing, Reduce unused, Cleanup blocken okibank
Demote Shanghai III with MACHINE_IMPERFECT_GRAPHICS related to MT #01002
* new machine marked as NOT WORKING
Stakes Winner / Stakes Winner - GI Kinzen Seiha e no Michi (early development board) [ResO]
(SRAM content on board was dead, so most of the porgram is either lost or never existed)
- added Japan NEO-MVH MV1C BIOS [Razoola]
* labels are just v3 in position v3 etc. no 088a (nw)
This change makes the MC146818/DS128x devices use the regular ASSERT_LINE/CLEAR_LINE protocol like almost all other devices, removing an unexpected surprise. The devices are fairly widely used, so I've tried to review all of those references and check if they're affected. A surprising number of systems appear to have the interrupt hooked up, but were not accounting for the inversion, so this change might possibly correct some behaviour.
The following were modified to remove workarounds:
* src/devices/machine/cs4031: removed inversion
* src/devices/machine/wd7600: removed inversion
* src/mame/drivers/apollo: hooked up interrupt
* src/mame/drivers/micronic: removed inversion
* src/mame/drivers/octopus: removed inversion
* src/mame/machine/apollo: removed timer workaround
* src/mame/machine/at: removed inversion
* src/mame/machine/interpro_ioga: removed inversion
The behaviour of the following might change:
* src/devices/bus/econet/e01.cpp
* src/devices/bus/electron/cart/click.cpp
* src/devices/bus/lpci/southbridge.cpp
* src/devices/machine/fdc37c93x.cpp
* src/devices/machine/sis85c496.cpp
* src/mame/drivers/at.cpp
* src/mame/drivers/calchase.cpp
* src/mame/drivers/hotstuff.cpp
* src/mame/drivers/hx20.cpp
* src/mame/drivers/mbee.cpp
* src/mame/drivers/mtouchxl.cpp
* src/mame/drivers/pc1512.cpp
* src/mame/drivers/pcat_dyn.cpp
* src/mame/drivers/pcd.cpp
* src/mame/drivers/qx10.cpp
* src/mame/drivers/su2000.cpp
* src/mame/machine/pcshare.cpp
This makes these commands useful and consistent with dump in a virtual memory environment. One minor issue is what to do with save for an unmapped memory address: the approach taken here is to write the space.unmap() value, which seems the least harmful. On load, unmapped addresses are not written to, meaning that save/load with a constant address map work as expected.
* hp9k_3xx: simplify machine configs
add one hp9k3xx section that defines all the hardware that
is common between the /300 models.
Signed-off-by: Sven Schnelle <svens@stackframe.org>
* hp9k_3xx: make hp9k300 protected
Signed-off-by: Sven Schnelle <svens@stackframe.org>
* topcat: fix register accesses
* nereid: mask register address bits
* topcat: don't override contents before window move
depending on the direction of the window move, we must start
at the other end with move, otherwise we overwrite the data
before it is moved.
Signed-off-by: Sven Schnelle <svens@stackframe.org>
* topcat: Fix cursor handling
Old cursor handling hat a few problems:
- Changed VRAM contents which doesn't happen on real hardware
- Destroyed Image content on the line where the cursor is show
- Window mover copied the cursor
Signed-off-by: Sven Schnelle <svens@stackframe.org>
* fix spacing
Signed-off-by: Sven Schnelle <svens@stackframe.org>
In divide by 8 mode the value computed in compute_counter()
is wrong because the function doesn't divide the clock before
the calculation.
Signed-off-by: Sven Schnelle <svens@stackframe.org>
New Working Machine Added
------------------------------------------------------------
Megatouch 7 Encore Edition (9255-90-01 RO0, Standard version) [Brian Troha, The Dumping Union]
