525
edits
Changes
Jump to navigation
Jump to search
Line 1,311:
Line 1,311: − + − − 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 fills the top screen with red and the bottom screen with either yellow (if the current process was running under the APPLICATION memregion) or red. − − Before invoking this handler a second time, kernelpanic wait for the user to hold L+R+Start+Select down. Line 1,340:
Line 1,336: − +
PTM + removing some wrong info →KernelSetState
| Yes
| Yes
| Yes
| Yes
| 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.
| Hangs the Arm11. Used by kernelpanic, and PTM on shutdown/reboot. This makes all cores enter a WFI/B infinite loop.
|-
|-
| 6
| 6
| Yes
| Yes
| No
| No
| Alternate FIRM launch code-path, with different [[PXI]] FIFO word constants. Usually not used. PTM-sysmodule can use this but it's unknown what exactly triggers that in PTM-sysmodule.
| Hangs the Arm9, using a code path similar to the one used on firmlaunch. Used by PTM on shutdown/reboot.
|-
|-
| 9
| 9