In memory of Ben “bushing” Byer, who passed away on Monday, February 8th, 2016.

Difference between revisions of "Talk:IOSU syscalls"

From WiiUBrew
Jump to navigation Jump to search
m (Hallowizer2 moved page Talk:IOSU Syscalls to Talk:IOSU syscalls: Sentence case in titles)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
It says under heading Syscalls (via syscall instruction) that "Currently only syscall 0x04 is still used in production versions of IOSU."
+
I asked how to correctly use IOS_CreateThread : (Here's Tueidj answer)
This does not seem correct. I see several other Thumb SysCalls still in use on FW 5.5.x (15702)
 
Example:
 
    IOS_KERNEL:08133F44 Call_IOS_KERNEL__sys_close                                                ; CODE XREF: sub_8132C64+14             
 
    IOS_KERNEL:08133F44                              LDR            R12, =(__sys_close+1)            
 
    IOS_KERNEL:08133F48                              BX              R12 ; __sys_close               
 
    IOS_KERNEL:08133F4C off_8133F4C                  DCD __sys_close+1                               
 
    IOS_KERNEL:08133F50 Call_IOS_KERNEL__sys_open                                                               
 
    IOS_KERNEL:08133F50                              LDR            R12, =(__sys_open+1)             
 
    IOS_KERNEL:08133F54                              BX              R12 ; __sys_open                 
 
    IOS_KERNEL:08133F58 off_8133F58                  DCD __sys_open+1                            ; CODE XREF: sub_8132C84+7C   
 
    IOS_KERNEL:08133F5C Call_IOS_KERNEL__sys_read                                                               
 
    IOS_KERNEL:08133F5C                              LDR            R12, =(__sys_read+1)             
 
    IOS_KERNEL:08133F60                              BX              R12 ; __sys_read            ; CODE XREF: sub_8132D14+20
 
    IOS_KERNEL:08133F64 off_8133F64                  DCD __sys_read+1
 
  
IOS_KERNEL, IOS_NIM_BOSS, IOS_FPD,  use more than just 0x04, __sys_write0.  
+
proc is a function pointer, for a function that returns a u32 and takes one argument of type void*, which the new thread will execute. stack_top        points to the top of the stack that will be used by the new thread. [[User:Tueidj|Tueidj]] ([[User talk:Tueidj|talk]]) 12:46, 4 August 2016 (CEST)
Unless otherwise challenged as to why not, I will update the tables to correct this [[User:Datalogger|Datalogger]] ([[User talk:Datalogger|talk]])
 
:The disassembly you posted just looks like generated thunking stubs, are you sure they're referenced by other code? [[User:Tueidj|Tueidj]] ([[User talk:Tueidj|talk]]) 11:31, 30 April 2016 (CEST)
 
Technically, the statement "Used by Production units" excludes the use of Debug mode, and the functions above are still in-use for what is shipping in Production Unit's Debug code (all of the above are used if the user press "1" in debug mode), so I'm suggesting they be tagged as "Debug Units Only" instead of "unused". [[User:Datalogger|Datalogger]] ([[User talk:Datalogger|talk]]) 21:27, 30 April 2016 (CEST)
 

Latest revision as of 04:56, 10 August 2021

I asked how to correctly use IOS_CreateThread : (Here's Tueidj answer)

proc is a function pointer, for a function that returns a u32 and takes one argument of type void*, which the new thread will execute. stack_top points to the top of the stack that will be used by the new thread. Tueidj (talk) 12:46, 4 August 2016 (CEST)