aboutsummaryrefslogtreecommitdiffstats
path: root/docs/relnotes/17.0.1.html
diff options
context:
space:
mode:
authorBen Widawsky <[email protected]>2016-11-03 16:14:44 -0700
committerBen Widawsky <[email protected]>2017-03-15 10:36:05 -0700
commit63bd2ae7452d48f25962ae9985a34bbdba9c52cf (patch)
treed681018c1f51398472c8adf56aac3d800fffe67a /docs/relnotes/17.0.1.html
parent5e7d8d396196af61ce0b1663534d97bef7895993 (diff)
gbm: Introduce modifiers into surface/bo creation
The idea behind modifiers like this is that the user of GBM will have some mechanism to query what properties the hardware supports for its BO or surface. This information is directly passed in (and stored) so that the DRI implementation can create an image with the appropriate attributes. A getter() will be added later so that the user GBM will be able to query what modifier should be used. Only in surface creation, the modifiers are stored until the BO is actually allocated. In regular buffer allocation, the correct modifier can (will be, in future patches be chosen at creation time. v2: Make sure to check if count is non-zero in addition to testing if calloc fails. (Daniel) v3: Remove "usage" and "flags" from modifier creation. Requested by Kristian. v4: Take advantage of the "INVALID" modifier added by the GET_PLANE2 series. v5: Don't bother with storing modifiers for gbm_bo_create because that's a synchronous operation and we can actually select the correct modifier at create time (done in a later patch) (Jason) v6: Make modifier condition outside the check so that dri_use will work properly (Jason) Cc: Kristian Høgsberg <[email protected]> References (v4): https://lists.freedesktop.org/archives/intel-gfx/2017-January/116636.html Signed-off-by: Ben Widawsky <[email protected]> Reviewed-by: Eric Engestrom <[email protected]> (v1) Reviewed-by: Jason Ekstrand <[email protected]> Acked-by: Daniel Stone <[email protected]>
Diffstat (limited to 'docs/relnotes/17.0.1.html')
0 files changed, 0 insertions, 0 deletions