aboutsummaryrefslogtreecommitdiffstats
path: root/hw/gfx_ctrl_sweep.py (follow)
Commit message (Collapse)AuthorAge
* enumerate the ring control command space: all ids inertuser2026-09-30
The control register carries an identifier in four bits, so there are sixteen possible commands, eleven named in the headers and five undocumented, of which only ring-create and destroy had ever been used. This is a command space distinct from both the ring command space and the application command space and it had never been enumerated. With one identifier per fresh boot and each run passing its own control first, every one of the fourteen tested identifiers leaves the processor able to create a ring and run a command. The two excluded are the destroy command the driver uses normally and the reset command that resets the chip by design. The interrupt-ring setter deserved attention since it points the processor at a host-supplied ring, the same shape as the unvalidated fence destination, but writing it changes nothing observable, so on this firmware it needs parameters this path does not supply. This is the only structure in the ring family with no defect, the frame having two unvalidated fields and creation an alignment gap, and it exhausts that family.