summaryrefslogtreecommitdiffstatshomepage
path: root/src/mame/machine
diff options
context:
space:
mode:
Diffstat (limited to 'src/mame/machine')
-rw-r--r--src/mame/machine/atarigen.c6
-rw-r--r--src/mame/machine/slapstic.c10
2 files changed, 8 insertions, 8 deletions
diff --git a/src/mame/machine/atarigen.c b/src/mame/machine/atarigen.c
index 1790c1fe9ee..512b3f5606b 100644
--- a/src/mame/machine/atarigen.c
+++ b/src/mame/machine/atarigen.c
@@ -511,8 +511,8 @@ static void slapstic_postload(void)
static OPBASE_HANDLER( atarigen_slapstic_setopbase )
{
/* if we jump to an address in the slapstic region, tweak the slapstic
- at that address and return ~0; this will cause us to be called on
- subsequent fetches as well */
+ at that address and return ~0; this will cause us to be called on
+ subsequent fetches as well */
address &= ~atarigen_slapstic_mirror;
if (address >= atarigen_slapstic_base && address < atarigen_slapstic_base + 0x8000)
{
@@ -557,7 +557,7 @@ void atarigen_slapstic_init(int cpunum, offs_t base, offs_t mirror, int chipnum)
/* ensure we recopy memory for the bank */
atarigen_slapstic_bank = 0xff;
-
+
/* install an opcode base handler if we are a 68000 or variant */
atarigen_slapstic_base = base;
atarigen_slapstic_mirror = mirror;
diff --git a/src/mame/machine/slapstic.c b/src/mame/machine/slapstic.c
index af2722d7456..669fb2eecf0 100644
--- a/src/mame/machine/slapstic.c
+++ b/src/mame/machine/slapstic.c
@@ -871,11 +871,11 @@ int slapstic_bank(void)
static int alt2_kludge(offs_t offset)
{
/* Of the 3 alternate addresses, only the middle one needs to actually hit
- in the slapstic region; the first and third ones can be anywhere in the
- address space. For this reason, the read/write handlers usually only
- see the 2nd access. For the 68000-based games, we do the following
- kludge to examine the opcode that is executing and look for the 1st
- and 3rd accesses. */
+ in the slapstic region; the first and third ones can be anywhere in the
+ address space. For this reason, the read/write handlers usually only
+ see the 2nd access. For the 68000-based games, we do the following
+ kludge to examine the opcode that is executing and look for the 1st
+ and 3rd accesses. */
if (access_68k)
{