SecBSD/xenocara
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

sync with OpenBSD -current

Browse source
This commit is contained in:
purplerain 2024-04-29 00:35:41 +00:00
parent 5d45cd7ee8
commit 155eb8555e
Signed by: purplerain
GPG key ID: F42C07F07E2E35B7
5506 changed files with 1786257 additions and 1416034 deletions
Download patch file Download diff file Expand all files Collapse all files

10
lib/mesa/docs/drivers/freedreno.rst
View file

@ -42,7 +42,7 @@ Hardware acronyms
work and the clusters of registers for the state that hardware blocks use.
CP
Command Processor. Reads the stream of statechanges and draw commands
Command Processor. Reads the stream of state changes and draw commands
generated by the driver.
PFP
@ -165,7 +165,7 @@ call is going to actually execute (some primitive is visible in the current
tile), the SQE goes through the ``GROUP_ID``\s and for any with an update since
the last time they were executed, it executes the corresponding fragment.
Starting with a6xx, states can be taggged with whether they should be executed
Starting with a6xx, states can be tagged with whether they should be executed
at draw time for any of sysmem, binning, or tile rendering. This allows a
single command stream to be generated which can be executed in any of the modes,
unlike pre-a6xx where we had to generate separate command lists for the binning
@ -173,7 +173,7 @@ and rendering phases.
Note that this means that the generated draw state has to always update all of
the state you have chosen to pack into that ``GROUP_ID``, since any of your
previous statechanges in a previous draw state command may have been skipped.
previous state changes in a previous draw state command may have been skipped.
Pipelining (a6xx+)
^^^^^^^^^^^^^^^^^^
@ -387,7 +387,7 @@ You can enable capturing all the BOs with:
Note that, since all command streams get captured, it is easy to run the system
out of memory doing this, so you probably don't want to enable it during play of
a heavyweight game. Instead, to capture a command stream within a game, you
probably want to cause a crash in the GPU during a farme of interest so that a
probably want to cause a crash in the GPU during a frame of interest so that a
single GPU core dump is generated. Emitting ``0xdeadbeef`` in the CS should be
enough to cause a fault.
@ -569,7 +569,7 @@ A typical work flow would be:
- After the breakpoint is reached each breadcrumb would require
explicit ack from the user. This way it's possible to find
the last packet which did't hang.
the last packet which didn't hang.
- Find the packet in the decoded cmdstream.