mirror of https://github.com/PCSX2/pcsx2.git
IOP Sync problems should be fixed now (yeah I said that 2 revisions ago too, I know). But this time I knew what to look for! spu2ghz stretch stats don't seem to crap out now. ;)
git-svn-id: http://pcsx2-playground.googlecode.com/svn/trunk@258 a6443dda-0b58-4228-96e9-037be469359c
This commit is contained in:
parent
c4ceb8c826
commit
1bd9f54c9b
|
@ -161,16 +161,13 @@ static void _psxTestInterrupts() {
|
||||||
PSX_TESTINT(21, usbInterrupt);
|
PSX_TESTINT(21, usbInterrupt);
|
||||||
}
|
}
|
||||||
|
|
||||||
|
#define IOP_WAIT_CYCLE 256 // was (and is again!) 64
|
||||||
// Can't safely lower the IOP wait cycle counter (yet).
|
|
||||||
// 128 might be a safe value but until I know what's cuasing it to
|
|
||||||
// suck at higher values I'll err on the side of caution.
|
|
||||||
|
|
||||||
#define IOP_WAIT_CYCLE 64 // was (and is again!) 64
|
|
||||||
|
|
||||||
void psxBranchTest()
|
void psxBranchTest()
|
||||||
{
|
{
|
||||||
g_psxNextBranchCycle = psxRegs.cycle + IOP_WAIT_CYCLE;
|
// g_psxNextBranchCycle is initialized for us by iPsxBranchTest.
|
||||||
|
g_psxNextBranchCycle = psxRegs.cycle;
|
||||||
|
if( EEsCycle >= 0 ) g_psxNextBranchCycle += IOP_WAIT_CYCLE;
|
||||||
|
|
||||||
if ((int)(psxRegs.cycle - psxNextsCounter) >= psxNextCounter)
|
if ((int)(psxRegs.cycle - psxNextsCounter) >= psxNextCounter)
|
||||||
psxRcntUpdate();
|
psxRcntUpdate();
|
||||||
|
|
|
@ -994,7 +994,7 @@ static void iPsxBranchTest(u32 newpc, u32 cpuBranch)
|
||||||
|
|
||||||
// check if we've caught up with the EE
|
// check if we've caught up with the EE
|
||||||
SUB32ItoM((uptr)&EEsCycle, s_psxBlockCycles*PSXCYCLE_MULT*8); // 8 EE clocks for every IOP clock.
|
SUB32ItoM((uptr)&EEsCycle, s_psxBlockCycles*PSXCYCLE_MULT*8); // 8 EE clocks for every IOP clock.
|
||||||
j8Ptr[2] = JG8(0);
|
j8Ptr[2] = JGE8(0);
|
||||||
|
|
||||||
// Break the Block-execute Loop here.
|
// Break the Block-execute Loop here.
|
||||||
// (but not without running another branch test! And do it regardless
|
// (but not without running another branch test! And do it regardless
|
||||||
|
|
Loading…
Reference in New Issue