APT:ReceiveParameter: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
|||
| Line 45: | Line 45: | ||
|- | |- | ||
| 3 | | 3 | ||
| | | Signal type (?) | ||
|- | |- | ||
| 4 | | 4 | ||
Revision as of 12:11, 1 February 2014
Request
| Index Word | Description |
|---|---|
| 0 | Header code [0x000D0080] |
| 1 | AppID |
| 2 | Parameter buffer size, max size is 0x1000(this can be zero). |
The following is located 0x100-bytes after the beginning of the above command buffer:
| Index Word | Description |
|---|---|
| 0 | (Size<<14) | 2 |
| 1 | Output parameter buffer ptr |
Response
| Index Word | Description |
|---|---|
| 0 | Header code |
| 1 | Result code |
| 2 | Unknown |
| 3 | Signal type (?) |
| 4 | Actual parameter buffer size, this is <= to the the input size. |
| 5 | Value 0x10 |
| 6 | Handle from the source process which set the parameters, this handle is likely used for shared memory(this can be 0x0). |
| 7 | (Size<<14) | 2 |
| 8 | Output parameter buffer ptr |
Description
This returns the current parameter data from NS state, from the source process which set the parameters. Once finished, NS will clear a flag in the NS state so that this command will return an error if this command is used again if parameters were not set again.