Changes

Jump to navigation Jump to search
1,285 bytes added ,  23:03, 24 April 2016
Created page with "=Request= {| class="wikitable" border="1" |- ! Index Word ! Description |- | 0 | Header code [0x001F0902] |- | 1-35 | 0x8C-byte input structure. |- | 36 | Size of each buffe..."
=Request=
{| class="wikitable" border="1"
|-
! Index Word
! Description
|-
| 0
| Header code [0x001F0902]
|-
| 1-35
| 0x8C-byte input structure.
|-
| 36
| Size of each buffer.
|-
| 37
| Value 0x0
|-
| 38
| KProcess handle
|}

=Response=
{| class="wikitable" border="1"
|-
! Index Word
! Description
|-
| 0
| Header code
|-
| 1
| Resultcode
|-
| 2-17
| Output state
|}

=Input Structure=
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Total entries that are actually used below.
|-
| 0x4
| 0x88
| 17 0x8-byte entries.
|}

==Entry Structure==
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Linearmem vaddr output buffer, equivalent to config+0x64. This must be non-zero.
|-
| 0x4
| 0x4
| Linearmem vaddr additional output buffer, equivalent to config+0x68. This can be zero when not used.
|}

=Description=
This command isn't used by SKATER.

This loads the input structure into state, the vaddrs are also converted to physaddrs.

Once this command is used, each [[MVDSTD:ControlFrameRendering|rendered]] frame will be written into the output buffers specified by the entry-list in state, instead of the output buffers from configuration. Exactly how multiple entries is handled during rendering is unknown.

Navigation menu