News for hackers. Stuff that matters.
Re:Why don't we have Wayland on Raspberry Pi yet? (2018) by floatboth on Tuesday April 23, 2019 @04:26PM (#19732480)
Screen tearing, bad performance, bad touchscreen support (not independent of mouse cursor), and especially important these days: no real HiDPI support (practically impossible to support different scales for different monitors). It's not good enough.
Re:Why don't we have Wayland on Raspberry Pi yet? (2018) by chmln on Tuesday April 23, 2019 @05:28PM (#19733075)
These claims are blown out of proportion and/or simply untrue.

Screen tearing: both Intel and AMD have hardware-backed "TearFree" buffering to prevent tearing. Bad performance: citation required - in my experience, Xorg is way faster. Touchscreen support - in most cases just works out of the box thanks to libinput. No HiDPI support for different scales per monitor - simply wrong - this is trivial with xrandr.

Re:Why don't we have Wayland on Raspberry Pi yet? (2018) by blibble on Tuesday April 23, 2019 @05:45PM (#19733253)
I still find tearing to be problematic

I have a machine with a supported Radeon card (open-source driver), another machine with a supported nvidia card (binary blob driver), and another two machines using different intel onboard graphics chips (open-source driver)

the radeon and the intel (both drivers which work with it) have issues putting out a stable jitterless 60fps without tearing (with tearfree on, and various combinations of with/without compositing/glx/...)

Re:Why don't we have Wayland on Raspberry Pi yet? (2018) by chmln on Tuesday April 23, 2019 @10:15PM (#19734988)
How did you test the fps?

I'm using the intel driver as well, and it's definitely not perfect. But it's pretty close, at least for me - I get hardware-accelerated video decoding with VAAPI, no tearing, and excellent input latency (~3ms).

Re:Why don't we have Wayland on Raspberry Pi yet? (2018) by blibble on Wednesday April 24, 2019 @02:22PM (#19741346)
I've got a couple of videos I use that make the tearing/jitter obvious, e.g. https://www.youtube.com/watch?v=0RvIbVmCOxg (you can get a .mp4 too which eliminates the browser as a possible cause)

sadly I can see the jitter/tearing, vs. on Windows where it's perfect

(with 4k or higher frame rates it's far more obvious)

Re:Why don't we have Wayland on Raspberry Pi yet? (2018) by kevin_thibedeau on Wednesday April 24, 2019 @12:18AM (#19735517)
That's your video driver's fault. Not X's.
Re:Why don't we have Wayland on Raspberry Pi yet? (2018) by curt15 on Tuesday April 23, 2019 @09:47PM (#19734856)
If you click and drag a window around in xorg, does the window stick perfectly to the cursor or is there still noticeable lag?
Re:Why don't we have Wayland on Raspberry Pi yet? (2018) by chmln on Tuesday April 23, 2019 @10:08PM (#19734943)
I use a tiling wm (i3), so I can't exactly drag windows around, but I can drag-and-resize them. In my case, there is no lag. However, there is a tiny amount of stuttering since I don't use a compositor, but I can live with that.
Re:Why don't we have Wayland on Raspberry Pi yet? (2018) by yjftsjthsd-h on Wednesday April 24, 2019 @01:23AM (#19735779)
> I use a tiling wm (i3), so I can't exactly drag windows around, but I can drag-and-resize them

Sure you can. Just pop the widow into floating mode; I think the default is meta-space.

Re:Why don't we have Wayland on Raspberry Pi yet? (2018) by andreyv on Wednesday April 24, 2019 @01:52AM (#19735885)
There is no tearing with proper drivers and window managers. This was a problem in the past, but now is largely overstated.
Re:Why don't we have Wayland on Raspberry Pi yet? (2018) by rwmj on Wednesday April 24, 2019 @08:25AM (#19737657)
I never even knew what the problem was supposed to be. A window isn't rendered absolutely perfectly when I drag it around? How is that even an issue that anyone cares about?! Do you spend all day moving windows around? Compared to major flaws in Wayland like not being able to use a program at all on a remote desktop, it's trivialities.