On Wed, 2018-04-04 at 16:16 +0100, Daniel Stone wrote:
> This series fixes running a modifier-aware server with a
> non-modifier-aware DRI3 compositing manager. We'd thought of and dealt
> with the case where we had legacy/non-modifier-aware clients, but
> slipped up with non-modifier-aware compositing managers.
> Glamor would allocate pixmaps with the full set of modifiers available
> to it from GBM/EGL, then try to export them to a non-modifier-aware
> client. This may fail outright (e.g. when the modifier adds a plane), or
> result in garbage (with an exotic modifier selection the client can't
> infer via magic back channels).
> When we get a request to export a buffer to a non-modifier-aware client
> in Glamor, forcibly reallocate it with no explicit modifiers, so we get
> something that can be exported to legacy clients.
Took me a second to figure out how 5/7 was getting the reallocation to
happen, but this all makes sense. It also fixes Xorg on my laptop, so
thank you very much! Merged:
remote: E: failed to find patch for rev
remote: I: patch #214874 updated using rev
remote: I: patch #214875 updated using rev
remote: I: patch #214873 updated using rev
remote: I: patch #214879 updated using rev
remote: I: patch #214877 updated using rev
remote: I: patch #214878 updated using rev
remote: I: 6 patch(es) updated to state Accepted.
574069c291..23c67987a3 master -> master
email@example.com: X.Org development