- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Load the complete ROM1 - 4MB #6719
Conversation
why is loading a 4mb block so important? what breaks if you don't do that? The sizes you said don't work are the sizes of those ROMS as reported by the PS2. |
The issue is that EROM is stored at different locations across models. On FATs it is stored at 0x40000 (early) or 0x80000 (late) relative to ROM1 base. On SLIMs there are multiple copies stored in ROM1, for PAL, USA, JP, and the proper location is determined dynamically. It's hard to guess the proper address for every bios without additional information. |
okay, but we can't decrypt the EROM anyways, so it doesn't really matter too much. |
if the only issue is the storage location, then the better idea would to be to map it correctly like we do with NVM files depending on the BIOS revision, then it's not a problem. |
It may offer time to users to extract their BIOS in the expected format for when the decryption will be possible 😄 |
I assume this is the result of a conversation I had in a discord server with someone else.
I'm against this as I don't see the point in this. Even if you really need the erom in it's proper place, let's not break compatibility with the old dumper, and now, the new dumper that was just released. You've failed to provide a good reason to do this. |
I think it would be better to keep compatibility with the broken, old layout alongside the new layout. |
The underdumped BIOSes will continue to work exactly the same how they work today. The EROM was only loaded so far, but it was not even mapped to PS2 memory, it was completely unused. |
If that's true, why didn't you open with that? Not being mapped at all is a much more valid reason than "This thing we can't use is in the wrong place" However it looks like it was mapped to EROM to me? |
Line 805 in 5e87f6d pcsx2/pcsx2/x86/ix86-32/iR5900-32.cpp Line 616 in 5e87f6d |
Okay I see what you mean. |
well, it would be nice if you provided a solution for all existing bios dumps, if an .erom file is detected then map that to the correct space in memory. You can check the BIOS version and adjust the mapped location manually. I don't agree with not supporting existing roms and rom dumpers to force your own ideal on to everyone. |
Woudl you like to try F0bes/biosdrain#10 along with your PR? Also if you could make your commit names somewhat match our standard that would be cool (an appropriate prefix, like BIOS: or something..) |
EROM is part of ROM1, its exact location vary and can't be predicted
Rebased and prefixed. I tested F0bes/biosdrain#10 on a 90k and it extracts a bios compatible with this PR, having the expected results (both alone and combined with #4274). After these changes, the bios files may be checked against redump database - eventually automatically. |
Alright, thanks :) |
Description of Changes
won't workis not recommended: