GPU Command Timing: Difference between revisions
| Revision as of 05:40, 23 October 2026 RemmyLee (Hardware tests: 15 more test pages (CPU, DMA, SPU, GPU, MDEC, CD-ROM, bus), each with See also links to the pages that measure the same parts) | Revision as of 05:41, 23 October 2026 RemmyLee (Hardware tests: See also links back from 37 existing pages to the new ones) | ||
| Line 14: | Line 14: | ||
| The figure includes the CPU's stores and the period of the poll loop. Polling with nothing written took 108 cycles, and a single GP0(00h) took 127, so about 110 to 130 cycles of every figure are overhead. The display is collapsed with GP1(07h) so that the GPU stays in vertical blank, and all drawing goes to VRAM rows 256 to 511.[^src][^gbs] | The figure includes the CPU's stores and the period of the poll loop. Polling with nothing written took 108 cycles, and a single GP0(00h) took 127, so about 110 to 130 cycles of every figure are overhead. The display is collapsed with GP1(07h) so that the GPU stays in vertical blank, and all drawing goes to VRAM rows 256 to 511.[^src][^gbs] | ||
| + | See also: | ||
| + | |||
| + | - [GPU Drawing Time and Status Bits](/tests/gpu-drawing-time/) | ||
| + | - [GPU Flat Quad Fill Time](/tests/gpu-flat-quad-fill-time/) | ||
| + | |||
| ## Results | ## Results | ||