Press "Enter" to skip to content

They propose to standardize the information of the monitors to avoid fragmentation in Wayland

Wayland

One of the most relevant changes that has been forced Wayland it is the fact of delegating or transferring to the composers many of the functions that were exercised or executed by Xorg. This new approach opens the door to generate fragmentation because each of the functions that Xorg exerted can end up being implemented in a different way in each composer.

Fragmentation is something that has turned against GNU / Linux a long time ago, and the fact that Wayland and the complexity of its implementation can aggravate the situation would end up leaving the system in a compromised situation in the desktop sector (or at least it would compromise its evolution).

One of the fronts that is worrying Wayland the most is the analysis of blobs of Extended Display Identification Data (EDID) to obtain the information of the monitors, whose implementation by the composers is not responding, at least in appearance, to any standard process. Or in other words, that each one is doing it in a different way.

The situation with the monitor data comes from the fact that Linux does not have any library for the analysis of the EDIDs, although it is capable of supplying the user space with various metadata of the connected monitors. From there, the Wayland composers who have implemented it can perform the EDID analysis, thus obtaining more information about the standardized structure that the kernel exposes to the user space. Performing this process is becoming important for features like advanced color and HDR.

In order to avoid fragmentation, Pekka Paalanen, a developer at Wayland, has called for EDID blob analysis is supported by a standardized library to avoid duplication and possible fragmentation generated by Wayland composers.

The new EDID blob analysis library, if Paalanen’s intentions are fulfilled, will be hosted on freedesktop.org, published under the MIT license, would offer at least one C ABI and have minimal dependencies, although in its implementation it should be offer quite complete functionality. On the other hand, it will likely also offer support for DisplayID, the VESA standard that is intended to replace EDID and E-EDID.

The complexity of the Wayland implementation points to having to undertake new initiatives to address in a standardized way some of the challenges that it has posed, especially when it comes to minimizing a possible fragmentation that could lead to an increase in incompatibility.

Be First to Comment

Leave a Reply

Your email address will not be published. Required fields are marked *