Originally posted by wagaf
View Post
In fact, if you look at the source code revisions, the Frecon console of the Freon display server is still in active development, which also proves that it's still being used: https://chromium.googlesource.com/ch...atform/frecon/
And Freon has no connection to Wayland at all: "Freon isn't based directly on Wayland nor Mir [...]" (source: https://www.phoronix.com/forums/foru...to-replace-x11)
And for another official source: this PDF by a Google employee, which lays out the different layers of ChromeOS: https://www.x.org/wiki/Events/XDC201...p_Graphics.pdf
"ChromeOS devices that run ARC++ uses the Freon graphics stack Under the Freon driver model, the Chrome browser talks directly to the kernel's DRM/KMS APIs"
Even native Linux apps are rendered through Freon: it basically acts as a websocket to pipe X server calls to Freon.
ChromeOS only uses Wayland for displaying Android apps, which is the only thing you got right (your linked articles also prove that), but ChromeOS itself really is using Freon still. That's the point I was trying to make.
Comment