Originally posted by johnc
View Post
Announcement
Collapse
No announcement yet.
Does Using GNOME On Wayland Save Power?
Collapse
X
-
Originally posted by daniels View Postgood thing it's been running just fine on proprietary drivers (in shipping products) for the last 3+ years then.
Congratulations on the embedded market, however. Wayland seems useful there, but X11 isn't common in that space anyway.
Comment
-
Originally posted by johnc View PostCongratulations on the embedded market, however. Wayland seems useful there, but X11 isn't common in that space anyway.
Comment
-
Originally posted by pgoetz View Post
I tried that with xserver 1.17 git glamor and downclock my AMD Athlon 5350 to 800 MHz to simulate even more low end hardware... and no, no, it works all smooth and fine in X openbox/comption just like it do in wayland/weston... that is not what i have here, so don't see any strong point for wayland there
If Pi blob favor something, well that does not mean all driver in X behave like that .Last edited by dungeon; 31 December 2014, 11:52 AM.
Comment
-
Originally posted by dungeon View PostWhat is tested there is probably non composited X, or some borked Pi blob driver or not with vblank against of course Wayland which has composite requirement. You should not see that tear in X with vblanked composition and proper drivers .
I tried that with xserver 1.17 git glamor and downclock my AMD Athlon 5350 to 800 MHz to simulate even more low end hardware... and no, no, it works all smooth and fine in X openbox/comption just like it do in wayland/weston... that is not what i have here, so don't see any strong point for wayland there
If Pi blob favor something, well that does not mean all driver in X behave like that .
Have you measured the same variables the video shown? Or your opinion is just a sort of "my eyes say they are the same"?
Also, to be honest, the "vblacked composition and proper drivers" sounds like a list of things necessary to workaround to the X deficiencies more than a strong point in favor, to me.
Comment
-
Originally posted by valeriodean View PostDid you try?
Have you measured the same variables the video shown?
Or your opinion is just a sort of "my eyes say they are the same"?
Also, to be honest, the "vblacked composition and proper drivers" ...
Anyway, Happy New Year to you
Comment
-
Originally posted by valeriodean View Post... sounds like a list of things necessary to workaround to the X deficiencies more than a strong point in favor, to me.
I don't have that tearing in openbox, and i had not that laggy tear even 10+ years ago in DRI1/XAA drivers time with radeon 7200 and AMD Duron 650 MHz. That is pure shitty Pi blob / software problem
It is pure shit video, or Pi is shit or drivers there are shit - or all are shits there .
BTW, comments are disabled on that yt video - that approve video is pure marketing shit
Comment
-
Originally posted by dungeon View PostWhich deficiencies? It is Pi driver blob used there... if some blob prefer to go there why should I
I don't have that tearing in openbox, and i had not that laggy tear even 10+ years ago in DRI1/XAA drivers time with radeon 7200 and AMD Duron 650 MHz. That is pure shitty Pi blob / software problem
It is pure shit video, or Pi is shit or drivers there are shit - or all are shits there .
BTW, comments are disabled on that yt video - that approve video is pure marketing shit
Comment
-
Originally posted by dungeon View PostWhat is tested there is probably non composited X, or some borked Pi blob driver or not with vblank against of course Wayland which has composite requirement. You should not see that tear in X with vblanked composition and proper drivers .
You can try to blame the driver, but truth is the driver is used as is by both X and wayland, so if it sucks for X, it's mostly an issue with X.
Comment
Comment