diff options
| author | Simon Ser <contact@emersion.fr> | 2021-07-08 16:52:59 +0200 |
|---|---|---|
| committer | Simon Ser <contact@emersion.fr> | 2021-07-28 22:52:35 +0200 |
| commit | 85d7ad2eef99b5ddc9da514231306c3678179f10 (patch) | |
| tree | 54c7f54ee7ceddc0317565e4af4387a30d06d4ea /protocol/input-method-unstable-v2.xml | |
| parent | 6aadf811aa75a07d4303a7c23e3b8499ffdb54db (diff) | |
backend/drm: allow legacy scan-out if FB props match
Historically we haven't allowed direct scan-out for legacy KMS,
because legacy misses the functionality to make sure a buffer can
be scanned out. However with renderer v6 the backend can't figure
out anymore whether the buffer comes from its internal swap-chain,
because the backend doesn't have an internal swap-chain.
The legacy KMS API guarantees that the driver won't reject a buffer
as long as it's been allocated with the same parameters as the
previous one. Let's check this in legacy_crtc_test.
Diffstat (limited to 'protocol/input-method-unstable-v2.xml')
0 files changed, 0 insertions, 0 deletions