Skip to content

kms-impl-simple: Handle lack of cached mode set in flip fallback

When a page flip fails with a certain error code, we've treated this as a hint that page flipping is broken and we should try to use mode setting instead.

On some drivers, it seems that this error is also reported when there was no mode set, which means we'll have no cached mode set to use in the fallback. The lack of prior mode set tends to happen when we hit a race when the DRM objects change before we have the time to process a hotplug event.

Handle the lack a missing mode set in the flip fallback path, with the assumption that we'll get a hotplug event that'll fix things up for us eventually.

Closes: #917 (closed)

Merge request reports