-
Notifications
You must be signed in to change notification settings - Fork 169
Improve sceGuSignal usage
#306
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
Conversation
| if (gu_call_mode == GU_CALL_SIGNAL) | ||
| { | ||
| sendCommandi(SIGNAL, (list_addr >> 16) | 0x110000); | ||
| sendCommandi(SIGNAL, (0x11 << 16) | (list_addr >> 16)); |
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.
I like the old syntax (list_addr >> 16) | 0x110000 as it's clearer to me, but it's probably just my personal preference.
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.
Same here… 0x11 is an specific command
| if (gu_call_mode == GU_CALL_SIGNAL) | ||
| { | ||
| sendCommandi(SIGNAL, 0x120000); | ||
| sendCommandi(SIGNAL, 0x12 << 16); |
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.
same here, I'd keep 0x120000 (personal preference)
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.
The reason why I split it is because 0x12 is actually part of a GE command when SIGNAL CMD is used.
Description
This PR improves the function definition of
sceGuSignalandsceGuCallMode, having now better-named parameters and a better description too.Additionally, I have fixed the usage in the examples that PSPSDK has.