-
Notifications
You must be signed in to change notification settings - Fork 133
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
convert ioplib in a standalone iop library #648
base: master
Are you sure you want to change the base?
Conversation
havent tested it yet if the mx4sio driver works normally after this (although it should?) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea, I created this 'ioplib' some time ago, based on sources from elsewhere (OPL I think it was). Since then I've made many copies = bad practice.
For naming consistency, if you name the library modhook
which I think covers what the library does better that ioplib
, then I think the include header should also be named modhook.h
. Also the function names should then begin with something like modhook_*
or mh_*
.
ioplib_hookExportEntry(lib, 46, _46_psio2_pad_transfer_init); | ||
ioplib_hookExportEntry(lib, 47, _47_psio2_mc_transfer_init); | ||
ioplib_hookExportEntry(lib, 48, _48_psio2_mtap_transfer_init); | ||
modhookk_hookExportEntry(lib, 23, _23_psio2_pad_transfer_init); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How did the CI build this succesfully? modhookk
with double 'k'?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lol, didn't saw that. Will recheck this later!
Currently there are a bunch of IRX modules around (AFAIK) using ioplib:
The Idea is to stop having local copies of ioplib.h and ioplib.c on every project that requires manipulating exports of other modules.
Therefore, converting this into a library wich is part of the PS2SDK seemed like the most reasonable approach, having one implementation for all the use cases. instead of local copies