fix homebrew 3d--one issue, at least. one of the vram register writes wasnt storing into the MMU memory (only executing the reconfiguration logic); but devkitpro is reading back from that register in its function vramIsTextureBank() which is used to allocate texture memory. this system of acting upon register writes, and stuffing the values for use later for register reads, is disturbing and bugprone this way... someone should probably look for early returns from MMU writes and make sure none of them are illegitimate.

This commit is contained in:
zeromus 2009-01-02 08:20:37 +00:00
parent c0e351339f
commit 40c3451047
1 changed files with 1 additions and 1 deletions

View File

@ -2404,7 +2404,7 @@ static void FASTCALL _MMU_ARM9_write32(u32 adr, u32 val)
MMU_VRAMmapControl(adr-REG_VRAMCNTA+1, (val >> 8) & 0xFF);
MMU_VRAMmapControl(adr-REG_VRAMCNTA+2, (val >> 16) & 0xFF);
MMU_VRAMmapControl(adr-REG_VRAMCNTA+3, (val >> 24) & 0xFF);
return;
break;
case REG_VRAMCNTE:
MMU_VRAMmapControl(adr-REG_VRAMCNTA, val & 0xFF);
MMU_VRAMmapControl(adr-REG_VRAMCNTA+1, (val >> 8) & 0xFF);