Neofar is working on a new version of the PSP API Browser.
This time with multi-version support (1.00 - 2.01).
http://pspdev.ofcode.com/api2.0/index.php
PSP API Project 2.0 (Multiversion)
IMHO: the manually maintained "database" format has outlived its usefulness. Manually maintaining the format is labor intensive and error prone.
The structure of the database is limiting.Only the database owners can add more modules or NIDs, and as pointed out the list is far behind. Also the modules listed and how they are organized are not useful IMHO (ie. there is a clear distinction between USER and system APIs - but you wouldn't know it looking at the database)
For more complete and useful APIs, the PSPSDK headers contain full API info for those APIs that people commonly use.
----
My suggestion is to replace the database format with a simple text list of NID names that have been found and confirmed (and if there is NID collision, two names).
With that input, a relatively simple PRX dumping program can automatically generate a full and complete listing of all exports, perhaps in STUB_ format.
That would be everything useful that is in the database now, up-to-date, accurate and complete - no chance of human error
The structure of the database is limiting.Only the database owners can add more modules or NIDs, and as pointed out the list is far behind. Also the modules listed and how they are organized are not useful IMHO (ie. there is a clear distinction between USER and system APIs - but you wouldn't know it looking at the database)
For more complete and useful APIs, the PSPSDK headers contain full API info for those APIs that people commonly use.
----
My suggestion is to replace the database format with a simple text list of NID names that have been found and confirmed (and if there is NID collision, two names).
With that input, a relatively simple PRX dumping program can automatically generate a full and complete listing of all exports, perhaps in STUB_ format.
That would be everything useful that is in the database now, up-to-date, accurate and complete - no chance of human error
I believe you mean: lots of function names are missing for known NIDs. ;)mrbrown wrote:many NIDs are missing...
We're running a 9 person project for distributed cracking utility utilizing PCs available on my university. I hope to see some reasonable results in 6 weeks (it's more of a project management experiment than development project, but our goal is to find possible names for all NIDs).
Why nobody using the real PSP source to fill parameters ???
Someone could document the functions for some API with the source files from Sony's SDK.... Like libmpeg.h :
[REMOVED]
[REMOVED]