3dbrew

GSP Shared Memory: Difference between revisions

← Older editNewer edit →
Yuriks (talk | contribs)
110 edits
Kynex7510 (talk | contribs)
99 edits
mNo edit summary
(6 intermediate revisions by 3 users not shown)
Line 4: Line 4:
=Interrupt info=
=Interrupt info=
The Interrupt info structure is located at sharedmemvadr + process_gsp_index*0x40.
The Interrupt info structure is located at sharedmemvadr + process_gsp_index*0x40.
It is a list of interrupts (id's 0-6 exist).


{| class="wikitable" border="1"
{| class="wikitable" border="1"
Line 13: Line 11:
|-
|-
| 0x0
| 0x0
| Index of the last processed data (field size is 0x33) (must be updated manually)
| Offset from the count where to save incoming interrupts
|-
|-
| 0x1
| 0x1
| To be processed datafields, (max 0x20 for PDC interrupts else the missed PDC filds are used,max 0x34 for all other if more interrupts happen and the Errorflag is 0 the Errorflag is set to 1)
| Count (max 0x20 for PDC, 0x34 for others)
|-
|-
| 0x2
| 0x2
| Errorflag (if the first bit of Errorflag is set future PDC interrupts are ignored)
| Missed other interrupts (set to 1 when 0 and count >= 0x34)
|-
|-
| 0x3
| 0x3
| not used
| Flags (bit0 = skip PDC)
|-
|-
| 0x4-0x7
| 0x4-0x7
| missed PDC0
| Missed PDC0 (incremented when flags.bit0 is clear and count >= 0x20)
|-
|-
| 0x8-0xB
| 0x8-0xB
| missed PDC1
| Missed PDC1 (same as above)
|-
|-
| 0xC-0x3F
| 0xC-0x3F
| u8 Interrupttypefield (0=PSC0, 1=PSC1, 2=PDC0/VBlankTop (sent to all threads), 3=PDC1/VBlankBottom (sent to all threads), 4=PPF, 5=P3D, 6=DMA)
| Interrupt list (u8) (0=PSC0, 1=PSC1, 2=PDC0/VBlankTop, 3=PDC1/VBlankBottom, 4=PPF, 5=P3D, 6=DMA)
|}
|}
GSP fills the interrupt list, then triggers the event set with [[GSPGPU:RegisterInterruptRelayQueue|RegisterInterruptRelayQueue]] for the specified process(es).
PDC interrupts are sent to all processes; other interrupts are only sent to the process with GPU rights.


=Framebuffer info=
=Framebuffer info=
Line 127: Line 129:
|-
|-
| 7
| 7
| Flag: when source buffer is not located in VRAM and this flag is non-zero, svcFlushProcessDataCache is used with the source buffer.
| Flush source (0 = don't flush, 1 = flush)
|}
|}


This command is normally used to DMA data from the application GSP [[Memory_layout|heap]] to VRAM.
This command is normally used to DMA data from the application GSP [[Memory_layout|heap]] to VRAM. When flushing is enabled and the source buffer is not located within VRAM, svcFlushProcessDataCache is used to flush the source buffer.


== Trigger Command List Processing ==
== Trigger Command List Processing ==
Line 148: Line 150:
|-
|-
| 3
| 3
| Flag, bit0 is written to GSP module state
| Update gas additive blend results (0 = don't update, 1 = update)
|-
|-
| 6-4
| 6-4
Line 154: Line 156:
|-
|-
| 7
| 7
| When non-zero, call svcFlushProcessDataCache() with the specified buffer
| Flush buffer (0 = don't flush, 1 = flush)
|}
|}


This command converts the specified address to a physical address, then writes the physical address and size to the [[GPU]] registers at 0x1EF018E0. This buffer contains [[GPU_Commands|GPU commands]].
This command converts the specified address to a physical address, then writes the physical address and size to the [[GPU]] registers at 0x1EF018E0. This buffer contains [[GPU/Internal_Registers|GPU commands]]. When flushing is enabled, svcFlushProcessDataCache is used to flush the buffer.


== Trigger Memory Fill ==
== Trigger Memory Fill ==
Line 187: Line 189:
|-
|-
| 7
| 7
| The low u16 is control0, while the high u16 is control1 (?)
| Control0 <nowiki>|</nowiki> (Control1 << 16)
|}
|}


Line 193: Line 195:
The associated buffer address must not be <= to the main buffer address, thus the associated buffer address must not be zero as well. When the bufX address is zero, processing for the bufX parameters is skipped.
The associated buffer address must not be <= to the main buffer address, thus the associated buffer address must not be zero as well. When the bufX address is zero, processing for the bufX parameters is skipped.


The values of control0 and control1 give information about the type of memory fill. See [[GPU Registers#Memory Fill|here]] for more information about memory fill parameters.
The values of Control0 and Control1 give information about the type of memory fill. See [[GPU/External_Registers#Memory Fill|here]] for more information about memory fill parameters.


== Trigger Display Transfer ==
== Trigger Display Transfer ==
Line 241: Line 243:
|-
|-
| 1
| 1
| Input buffer address
| Input buffer address.
|-
|-
| 2
| 2
| Output buffer address
| Output buffer address.
|-
|-
| 3
| 3
| Size
| Total bytes to copy, not including gaps.
|-
|-
| 4
| 4
| Input [[GPU|dimensions]]?
| Bits 0-15: Size of input line, in bytes. Bits 16-31: Gap between input lines, in bytes.
|-
|-
| 5
| 5
| Output dimensions?
| Same as 4, but for the output.
|-
|-
| 6
| 6
| Flags, normally this is 0x8, with bit2 optionally set when either of the dimensions fields are set.
| Flags, corresponding to the [[GPU/External_Registers#Transfer_Engine|Transfer Engine flags]]. However, for TextureCopy commands, bit 3 is always set, bit 2 is set if any output dimension is smaller than the input, and other bits are always 0.
|-
|-
| 7
| 7
Line 262: Line 264:
|}
|}


This command is similar to cmd3. It also writes to the [[GPU]] registers at 0x1EF00C00. It's unknown where the difference is.
This command is similar to cmd3. It also triggers the [[GPU/External_Registers#Transfer_Engine|GPU Transfer Engine]], but setting the TextureCopy parameters.


== Flush Cache Regions ==
== Flush Cache Regions ==
Retrieved from "https://www.3dbrew.org/wiki/GSP_Shared_Memory"