Annoyingly it seems Linux doesn't know the subpixel order of my monitor (DRM_MODE_SUBPIXEL_UNKNOWN). And Google seems to suggest this is pretty common, because the information isn't available in EDIDs. So I can't easily test any fix for nested just yet.
What I can do however is look at support for /setting/ the subpixel order. Since it seems that's what most people will need to do. We may also want to consider defaulting to HRGB if it's unknown. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1393578 Title: Subpixel order not included in Mir display information Status in Mir: In Progress Status in QtMir: Triaged Status in qtubuntu: Triaged Status in mir package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Bug description: Just capturing something mentioned by Trevinho on IRC this morning. MirDisplayOutput does not include subpixel ordering, it could and should though. The information is exposed on the drm side (drmModeSubPixel). Marking as wishlist in absence of other information. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1393578/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
