525
edits
Changes
Jump to navigation
Jump to search
Line 1,300:
Line 1,300: − + Line 1,308:
Line 1,308: − [[Configuration_Memory|0x1FF80015]] ("is devmode enabled") needs to be true. +
→KernelSetState
| Used by kernelpanic. This makes core0 enter a WFI/B infinite loop. Threads that were created on core1 or core2 have their priority set to 0x3F, except if the thread was created on core1 and whose parent process (if any) has the "Runnable on sleep" [[NCCH/Extended_Header#ARM11_Kernel_Flags|ARM11 kernel flag]] set. Core1 threads with a priority of 0x40 without a parent process have their priority set to 0x3E.
| Used by kernelpanic. This makes core0 enter a WFI/B infinite loop. Threads that were created on core1 or core2 have their priority set to 0x3F, except if the thread was created on core1 and whose parent process (if any) has the "Runnable on sleep" [[NCCH/Extended_Header#ARM11_Kernel_Flags|ARM11 kernel flag]] set. Core1 threads with a priority of 0x40 without a parent process have their priority set to 0x3E.
Prior to first invoking this handler, if and only if both UNITINFO and [[Configuration_Memory#0x1FF80015|0x1FF80015]] are not 0, and if there is no [[LCD_Registers#Fill_Color|LCD fill]] set at the time kernelpanic is called, kernelpanic fill the top screen with white (it does the same for the bottom screen if the current process is running under the APPLICATION memregion).
Prior to first invoking this handler, the global variable holding <code>UNITINFO != 0</code> is true, and if there is no [[LCD_Registers#Fill_Color|LCD fill]] set at the time kernelpanic is called, kernelpanic fill the top screen with white (it does the same for the bottom screen if the current process is running under the APPLICATION memregion).
Before invoking this handler a second time, kernelpanic wait for the user to hold L+R+Start+Select down.
Before invoking this handler a second time, kernelpanic wait for the user to hold L+R+Start+Select down.
| No
| No
| Arguments: <code>u32 what, u64 val</code>
| Arguments: <code>u32 what, u64 val</code>
UNITINFO needs to be non-zero.
If <code>what</code> is 0 or any invalid value, nothing is done.
If <code>what</code> is 0 or any invalid value, nothing is done.