that means ps2sdk maybe need a big update?Beware that the OPL modes have not remained the same over the years. Mode 1 used to be Alt Storage location, as OPL used to have a really big EE core.
Mode 7 was once something else too, but I forgot what.
OPL also had worse performance before v0.9.3, due to it making really small reads. So any game bug that is related to faulty critical region protection may have seemingly better compatibility with older commits.
Some of the commits somewhere between the r700~800 were severely bugged (starting with that commit with the accidental "changes.txt" in the commit log). Sometimes due to the size of the changes that I was trying to complete, lack of skills and sometimes just a lack of clarity of what I wanted to do. I used to be a fan of mega-commits, thinking that there would be some penalty for having significantly more, but smaller commits.
For this game, I did look at how it did reading during the last weekend, by statically analyzing the code (didn't run it). It seems to use sceCdRead() and sceCdSync() where appropriate; most calls to sceCdRead() are followed by sceCdSync(). There is a command-queuing system, which seems to (but not confirmed) to automatically insert a command for sceCdSync() after each command for sceCdRead(). All calls to sceCdRead() are conducted with infinite retry attempts.
The game appears to be single-threaded, other than the Sony threads that are used for the kernel patches. It does not seem to use the libcdvd callback mechanism.
It also uses streaming, but I didn't really check the code for that because streaming is usually used for things that can be streamed - like audio and video. It also has a sound driver, but I did not check that either, since we're not looking for a freeze or bad audio.
It was also made with a late SDK release, which should already have the more major kernel bugs patched out.
Commits are uniquely identified by the hash. Commit revisions may not remain the same, between repositories.
The use of commit revisions have gone back long in time. Back when OPL's repository used to be hosted on Bitbucket.
Since commit hashes cannot really indicate what came before/after, you can also mention the commit revision... if you can determine that... along with the hash. But Github has no function for indicating that.



