549
edits
Changes
Jump to navigation
Jump to search
Line 516:
Line 516: − + Line 1,313:
Line 1,313: + + + + + + + +
no edit summary
| style="background: green" | Yes
| style="background: green" | Yes
| style="background: green" | Yes
| style="background: green" | Yes
| Result BindInterrupt(Interrupt name, Handle syncObject, s32 priority, bool isManualClear)
| Result [[#Interrupt Handling|BindInterrupt]](Interrupt name, Handle syncObject, s32 priority, bool isManualClear)
|
|
|-
|-
= [[DMA]] =
= [[DMA]] =
The CTRSDK code for using svcStartInterProcessDma will execute svcBreak when svcStartInterProcessDma returns an error(except for certain error value(s)). Therefore on retail, triggering a svcStartInterProcessDma via a system-module which results in an error from svcStartInterProcessDma will result in the system-module terminating.
The CTRSDK code for using svcStartInterProcessDma will execute svcBreak when svcStartInterProcessDma returns an error(except for certain error value(s)). Therefore on retail, triggering a svcStartInterProcessDma via a system-module which results in an error from svcStartInterProcessDma will result in the system-module terminating.
= Interrupt Handling =
BindInterrupt adds the given event handle to an internal list for the given interrupt ID. Whenever the given interrupt is triggered, the kernel's interrupt handler will signal all events in the list corresponding to that interrupt.
Applications hence can wait for specific interrupts to happen by calling WaitSynchronization(N) on the event handles.
It is unknown whether BindInterrupt may be used with non-event handles.
= Debugging =
= Debugging =