|
|
Log in / Subscribe / Register

Achieving DisplayPort compliance

Achieving DisplayPort compliance

Posted Oct 18, 2017 16:31 UTC (Wed) by cesarb (subscriber, #6266)
Parent article: Achieving DisplayPort compliance

The last slide says it's compliant as of kernel 4.12 and xorg 1.19.3. What about Wayland?


to post comments

Achieving DisplayPort compliance

Posted Oct 18, 2017 16:41 UTC (Wed) by farnz (subscriber, #17727) [Link] (1 responses)

Any Wayland compositor running atop kernel 4.12 or later and handling the "link failed" uevent correctly will also be compliant. It's that latter bit that's difficult, and that will have to be checked on a compositor-by-compositor basis.

Achieving DisplayPort compliance

Posted Oct 18, 2017 19:48 UTC (Wed) by ManasiNavare (guest, #119160) [Link]

The newly added link-status property that gets exposed to the userland, should be used in Wayland and acted upon when its set to BAD to request a new modeset in order to make it compliant.
I plan to write a detailed article as a follow up with some examples to help scale this solution to other userspace drivers like Wayland, Surfaceflinger etc.

Manasi

Achieving DisplayPort compliance

Posted Oct 18, 2017 19:08 UTC (Wed) by mgraesslin (guest, #78959) [Link]

I can answer for Plasma/KWin: it's the first time that I hear about that.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds