Difference between revisions of "Talk:Cafe OS syscalls"
Jump to navigation
Jump to search
(Created page with "How about we replace 'Y' with a mark (e.g. 'x') indicating that the syscall is available and remove 'N' completely? This way the table gets better readable.") |
Datalogger (talk | contribs) (→Missing FastCalls: new section) |
||
| Line 1: | Line 1: | ||
How about we replace 'Y' with a mark (e.g. 'x') indicating that the syscall is available and remove 'N' completely? This way the table gets better readable. | How about we replace 'Y' with a mark (e.g. 'x') indicating that the syscall is available and remove 'N' completely? This way the table gets better readable. | ||
| + | |||
| + | == Missing FastCalls == | ||
| + | |||
| + | Since the SysCall_Handler masks with rlwimi r12,r0,5,{22,26} - shouldn't the last FastCall be #0x1F ? | ||
| + | 0x3E0/0x20=0x1F, so base 0xFFF021A0 + 0x3E0 =0xFFF02580, the APP_Panic that loads r3 with 0x3001F. | ||
| + | |||
| + | I know 0x1A, 0x1B,0x1C, 0x1D, 0x1E and 0x1F all branch to the table_dispatcher with AppPanic loaded, but later we could use these for other things... | ||
Revision as of 08:11, 19 April 2016
How about we replace 'Y' with a mark (e.g. 'x') indicating that the syscall is available and remove 'N' completely? This way the table gets better readable.
Missing FastCalls
Since the SysCall_Handler masks with rlwimi r12,r0,5,{22,26} - shouldn't the last FastCall be #0x1F ? 0x3E0/0x20=0x1F, so base 0xFFF021A0 + 0x3E0 =0xFFF02580, the APP_Panic that loads r3 with 0x3001F.
I know 0x1A, 0x1B,0x1C, 0x1D, 0x1E and 0x1F all branch to the table_dispatcher with AppPanic loaded, but later we could use these for other things...