IPC: Difference between revisions
Add some usage info for svcReplyAndReceive |
m spelling |
||
| Line 250: | Line 250: | ||
In a single operation, sends a IPC reply and waits for a new request. <code>handles</code> should be a pointer to an array of <code>handleCount</code> handles.<sup>TODO: Are only port/session handles supported?</sup> | In a single operation, sends a IPC reply and waits for a new request. <code>handles</code> should be a pointer to an array of <code>handleCount</code> handles.<sup>TODO: Are only port/session handles supported?</sup> | ||
<code>replyTarget</code> should contain a handle to the session to send the reply to. (This | <code>replyTarget</code> should contain a handle to the session to send the reply to. (This is usually the session from which we received the previous request.) | ||
If <code>replyTarget</code> is 0, no reply and the call will simply wait for an incoming event.<sup>TODO: It doesn't seem like the 0xFFFF0000 command id mentioned in the above sections is necessary, but needs confirmation.</sup> | If <code>replyTarget</code> is 0, no reply and the call will simply wait for an incoming event.<sup>TODO: It doesn't seem like the 0xFFFF0000 command id mentioned in the above sections is necessary, but needs confirmation.</sup> | ||