GSP Services: Difference between revisions

No edit summary
Kynex7510 (talk | contribs)
mNo edit summary
 
(One intermediate revision by the same user not shown)
Line 72: Line 72:
|  
|  
| No
| No
| SetDisplayTransfer (Stubbed)
| [[GSPGPU:SetDisplayTransfer|SetDisplayTransfer]]
|-
|-
| 0x000E0180
| 0x000E0180
|  
|  
| No
| No
| SetTextureCopy (Stubbed)
| [[GSPGPU:SetTextureCopy|SetTextureCopy]]
|-
|-
| 0x000F0200
| 0x000F0200
|  
|  
| No
| No
| SetMemoryFill (Stubbed)
| [[GSPGPU:SetMemoryFill|SetMemoryFill]]
|-
|-
| 0x00100040
| 0x00100040
Line 272: Line 272:
|-
|-
| [[8.0.0-18|v8196]]
| [[8.0.0-18|v8196]]
| Support for the new LINEAR memory region was implemented(for cache commands and vaddr->physaddr conversion). Support for the new process-mem 0x1E800000 region(however the GPU can't actually access this memory) was added for vaddr->physaddr conversion. Originally GSP module ignored vaddr->physaddr conversion errors(like with vaddrs outside of the handled ranges) and just wrote physaddr value0 to the GPU registers, however now GSP module returns an error for that instead(see [[GSP_Shared_Memory#Command_Buffer_Header|here]] regarding errors being written to GSP shared-mem). New services commands were added too, see above.
| Support for the new LINEAR memory region was implemented for cache commands and vaddr->paddr conversion. Support for the New3DS only [[Memory_layout#0x1F000000_.28New_3DS_only.29|QTM memory region]] was added for vaddr->paddr conversion. When vaddr->physaddr conversions fail while handling PSC commands, an error is now returned (see [[GSP_Shared_Memory#Command_Queue_Header|here]] regarding errors being written to GSP shared memory).
|}
|}