Originally posted by bwat47
View Post
On a separate note, because I know what that someone else would mention it eventually...
Canonical has to implement Hybrid graphics on their own, in server. Wayland also is currently without Hybrid support but for them its actually better-- remember Wayland just wants buffers filled with pixels. It doesnt care how those pixels got there. Daniel Stone said "Optimus? Thats a client problem." at his linux.conf.au presentation, most likely meaning hybrid support will come down to the Mesa devs leveraging DMA-BUF (everything has to be done in the driver, the kernel, or the GL stack. Wayland just wants buffers.)
Of interesting note is the actual implementation. On Windows when the hybrid kicks in, things flicker or stutter for a half second whenever you change GPU's and then youre good until you change GPU's again. On OS X interestingly, no stuttering or flickering or even pausing. It was either Daniel or David that said they most likely did all of their hybrid stuff inside their GL layer.
On Wayland, with compositing being mandatory and with the use of double/triple buffers..I wonder if Wayland will get to the same level of tear-free flicker-free switching. Either solution (Flicker or no flickering) is fine, really, it just looks nicer if we can achieve zero-flicker.
Leave a comment: