CPU Load Pairs and GTE Input Timing: Difference between revisions
| Revision as of 05:41, 23 October 2026 RemmyLee (Hardware tests: See also links back from 37 existing pages to the new ones) | Revision as of 05:49, 23 October 2026 RemmyLee (Hardware tests: the last 15 test pages (timers, SPU, CPU, GPU, DMA, CD-ROM, GTE), See also links both ways; uncited clock claim removed) | ||
| Line 14: | Line 14: | ||
| Each GTE row sets every input the command reads, sets the input under test to its old value 00010002h, waits four NOPs, writes the new value 00030004h, waits the stated number of NOPs and issues the command. Rows marked "after" issue the command first and write the new value after it. Each row runs twice. The cold run fetches its code from RAM and the cached run takes it from the instruction cache.[^runh] | Each GTE row sets every input the command reads, sets the input under test to its old value 00010002h, waits four NOPs, writes the new value 00030004h, waits the stated number of NOPs and issues the command. Rows marked "after" issue the command first and write the new value after it. Each row runs twice. The cold run fetches its code from RAM and the cached run takes it from the instruction cache.[^runh] | ||
| + | See also: | ||
| + | |||
| + | - [GTE Register Writes and Expansion Reads](/tests/gte-register-writes-expansion-reads/) | ||
| + | - [GTE Input Timing and CD-ROM Queries](/tests/gte-input-timing-cd-rom-queries/) | ||
| + | |||
| ## Results | ## Results | ||