mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-04-19 01:30:36 +02:00
panfrost: Make comment less confusing
Signed-off-by: Alyssa Rosenzweig <alyssa@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10393>
This commit is contained in:
parent
c6bb55ffcf
commit
a368cc022d
1 changed files with 4 additions and 6 deletions
|
|
@ -49,12 +49,10 @@
|
|||
* However, that same blend configuration will compile to many different blend
|
||||
* shaders, depending on the framebuffer formats active. The rationale is that
|
||||
* blend shaders override not just fixed-function blending but also
|
||||
* fixed-function format conversion. As such, each blend shader must be
|
||||
* hardcoded to a particular framebuffer format to correctly pack/unpack it. As
|
||||
* a concrete example, to the hardware there is no difference (!) between RG16F
|
||||
* and RG16UI -- both are simply 4-byte-per-pixel chunks. Thus both formats
|
||||
* require a blend shader (even with blending is totally disabled!), required
|
||||
* to do conversion as necessary (if necessary).
|
||||
* fixed-function format conversion, so blend shaders are keyed to a particular
|
||||
* framebuffer format. As an example, the tilebuffer format is identical for
|
||||
* RG16F and RG16UI -- both are simply 32-bit raw pixels -- so both require
|
||||
* blend shaders.
|
||||
*
|
||||
* All of this state is encapsulated in the panfrost_blend_state struct
|
||||
* (our subclass of pipe_blend_state).
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue