Originally posted by rxonda
View Post
And, yes. I guess that's why it isn't so "trivial" for the propietary drivers to support Wayland: they would either have to develop a backend for each compositor that supported their own private modesetting API, or switch to DRM/KMS. The later option, however, is not feasible, because of licenses, I think.
About your last question, I think you have confused the "platform" on which the compositor runs (DRM/KMS, Wayland, X11, propietary-modesetting-APIs,...), which is related to where the compositor's output is displayed and how the compositor takes input, and the GPU renderer that's used by clients. Optimus systems have two GPUs, and the ability to compute graphics with any of them in a per-application basis - for now, the user has to set an environment variable for the application to tell Mesa which GPU to use. A client could use any GPU to render its graphics; it would be up to the compositor to display its buffer on screen, using whatever means it had (DRM/KMS, Wayland, X11,...).
Comment