Originally posted by Nille
View Post
Announcement
Collapse
No announcement yet.
Whoops, There's A Big Problem For Wayland GTK+
Collapse
X
-
-
-
Originally posted by asdxAnd what have you done to help with that? Have you tried reporting bugs?
I never had problems with KMS, what driver/GPU were you using?
Comment
-
-
Originally posted by garegin View Posti've reported it to almost every linux forum, including this. kms is broken on many macs including the mac mini and macbook air. this is a known bug.
This can help you. I didn't read it yet because I've never found a mainstream bug (well, as a matter of fact, I've found a few, but they were already reported and fixed when I did figured out they were kernel bugs), and the ones with Openchrome were reported directly to their devlist.
EDIT: Whoops, forgot to put the link http://kernelnewbies.org/FoundBug.
Comment
-
Originally posted by RealNC View PostIn general, KMS in the blobs doesn't sound impossible. They would need glue in form of a kernel module with the actual functionality being provided by the blob.Originally posted by Serafean View PostKMS won't be easy for nvidia to implement in their binary blob (anyone remember the mess when OSS drivers became KMS enabled?). Another hard requirement for Wayland is EGL support, which I don't know if the binary blobs support.
EGL is not strict dependecy for Wayland by the way (check Wayland FAQ).
Comment
-
Originally posted by asdxOriginally posted by garegin View Posti've reported it to almost every linux forum, including this. kms is broken on many macs including the mac mini and macbook air. this is a known bug.
One of the more notorious ones: Radeon KMS on Macs with EFI boot. The workaround is to modify the kernel with a patch that was rejected by the radeon developers, and make it load the VGA BIOS from a dump you created in bootcamp.
Comment
-
Wayland requires kernel modesetting, or kms. It DOES NOT require KMS. Notice the difference in capitalization.
The nvidia and fglrx blobs already contain working kms systems in their drivers - they just use a different API than the open source drivers do (KMS).
That means those drivers just have to patch Wayland to interact with their own kernel drivers instead of the OSS APIs. That should be very simple to do, as Wayland handles that code very cleanly. Their drivers already have to heavily patch X to get it to work, so they just have to do the same thing to Wayland, but it will be much easier.
Comment
Comment