Repository navigation
Conversation
…veDataGetProgress The entry took the float* parameter from the OpenOrbis headers and shadPS4, said the PS5 module may differ, and planned to map the value to sceSaveDataBackup's copy. Firmware 13.42's libSceSaveData.sprx confirms the float*, checks the library context and state before a null pointer, and reads the value from a save-data service request, so that mapping would be a host model. AI-assisted: yes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Hi BunnyFl, could you qualify the new validation-order sentence with the internal status and connection checks from your trace? The helper returns |
|
Other open pull requests touch the same code. Merging one will break the other, or both implement the same thing. If this one builds on them, list them in Depends on.
Some comparisons could not be completed because a pull request conflicts with the base branch. Review these shared files manually before concluding that there is no overlap.
|
… order The null-pointer result comes from the helper at 0x1d6c0 after its own status and connection checks, and only a successful service reply supplies the float, so say that instead of a definite two-step order. AI-assisted: yes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
@oneandonlydean Thanks, done in AI-assisted: yes (Claude Code) |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ogress-firmware # Conflicts: # docs/dev/debt/libSceSaveData.native.md
What
The
sceSaveDataGetProgressentry indocs/dev/debt/libSceSaveData.native.md, merged with #15077, says three things that firmware 13.42 settles otherwise:float*parameter from the OpenOrbis headers and shadPS4 and says "the PS5 module may differ";sceSaveDataBackup's own copy, as shadPS4 does;The entry now says what firmware 13.42's
libSceSaveData.sprxdoes. The export staysNotImplemented_nid_no_patch; no code changes.Source: firmware 13.42
libSceSaveData.sprx(sha2561d214285f188f1c0821a611a08345833dd379cee547d5834e64228cde906a567), exportANmSWUiyyGQat0x39af0. Read from disassembly only, not measured on a console:So the value comes from the save-data service, and mapping it to the library's backup copy would be a host model rather than the console's behaviour. I left out
0x809F8002and the0x1d480error path from the entry, since neither is traced to a caller-visible meaning.docs/dev/debt/libSceSaveData.native.md(760 characters).Tested
py -3 tools/check_conventions.py --base upstream/main: all checks pass.py -3 tools/pr_overlap.py --branch docs/savedata-getprogress-firmware: it lists feat(libSceSaveData): initialize through sceSaveDataInitialize2 #12625, feat(libSceSaveData): implement sceSaveDataCheckBackupData, sceSaveDataRestoreBackupData and sceSaveDataUmountWithBackup #12748, feat(libSceSaveData): deliver backup completions to a registered event callback #13551, fix(libSceSaveData): keep sceSaveDataGetMountedSaveDataCount unimplemented #14150, docs(debt): separate entries with blank lines and drop derived export totals #14212 and feat(libSceSaveData): answer the save point, client priority and debug thread id calls as firmware 13.42 does #14908 as sharing the debt file without a comparison. I read each diff: none implements or rewrites this entry. feat(libSceSaveData): initialize through sceSaveDataInitialize2 #12625 adds an older copy of it, and the others only carry it as context.Checklist
main; no other open PR implements the same functions🤖 Generated with Claude Code