3dbrew

GSP Shared Memory: Difference between revisions

← Older editNewer edit →
Steveice10 (talk | contribs)
1,434 edits
Kynex7510 (talk | contribs)
100 edits
mNo edit summary
(3 intermediate revisions by 2 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/Internal_Registers|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 ==
Retrieved from "https://www.3dbrew.org/wiki/GSP_Shared_Memory"