Slashdot Mirror
Wayland 1.1 Released — Now With Raspberry Pi Support
An anonymous reader writes "Six months after the release of Wayland 1.0, versions 1.1 of Wayland and Weston have been released. Wayland/Weston 1.1 brings new back-end support for the Raspberry Pi, Pixman renderer, Microsoft Remote Desktop Protocol (RDP), and FBDEV frame-buffer device. Wayland/Weston 1.1 also introduces a modules SDK, supports the EGL buffer-age extension, touch-screen calibration support, and numerous optimizations and bug-fixes."
Does it support a way to handle remote windows yet? Or does it still only support an entire desktop remoted?
SURELY NOT!!!!!
Why not link to the mailng list post? Don't give hits to the spammy fuckers. Link to the source! Use the source Luke! http://lists.freedesktop.org/archives/wayland-devel/2013-April/008631.html
I love my Pi, but it suffers immensely from slow redraws.
Nothing has been keeping Linux on the desktop behind more than X. Finally some decent graphics. Keep up the good work and keep the good bits coming.
Can anyone point me to the docs for writing my own window manager?
Call me ignorant. but can someone explain why we have more than a post per week either about or mentioning Wayland for the last couple of months? Is it really that interesting for the average /. user to hear about every feature added to Wayland or every project/company whatever that supports or does not support Wayland in some way? Or is it just one of those strange obsessions of the /. editors?
I understand it is an important project, supposed to be the successor to X11 etc so it has more interest to geeks than, say, bitcoins, but is it really that interesting?
Violence is the last refuge of the incompetent. Polar Scope Align for iOS
You can dream up all the X replacements you want, but you need to deliver working code.
Good job Wayland.
Maw! Fire up the karma burner!
Wayland is going to be the best thing to happen Linux ever! This is what's going to make Steam games smooth, make graphical lags and glitches nonexistent, and set the stage for better graphics drivers from graphics card venders! I'm stoked! Can't wait for this to go mainstream!
On the one hand I am beginning to find this development interesting.
On the other hand, we already have a proven stable graphical application protocol. It's called X and it's been around for 30 years. I just don't get it. Why reinvent the wheel?
And on the Eighth Day, Man created God.
At the most optimistic, Wayland is still one or two years away from mainstream use. Even then, most apps will run under the rootless X server.
X will finally disappear if and when all apps upgrade to GTK3 or QT5 (which might be never).
Wayland is X designed properly, however it is basically the same thing. It does not seem to yet acknowledge the wider changing context within which desktop Linux has to operate, i.e. we are moving away from a world where manufacturers produce devices for Windows (and don't care about desktop Linux) into a world where manufacturers produce devices for Android (and still don't care about desktop Linux).
Canonical became flame-bait central over Mir and their reactive 'community engagement' (troll feeding), but I wonder if they have a point, that by the time Wayland is widely deployable it will be outdated?
My little Linux and tech blog
All that unused cruft they've already broken like non-greyscale 8 bit pseudocolor palettes, all the legacy Xlib functionality (removed during the migration to xcb), XAA support, All those 'legacy' 16 bit capable 3d accelerators and the dri1 infrastructure to support them?
Cuz yeah, all that 'cruft' has already been dropped, whether the rest of us wanted it to or not, and irrespective of if the performance of the 'replacements' which generally speaking only showed performance improvements for the then-current generation of graphics cards, not the legacy ones which now had to fall back to unaccelerated drivers as the code their accelerated counterparts relied on was stripped out as 'too much trouble to maintain'.
The only reason I'm rooting for wayland is so all those douchebag devs and companies will move on and stop raping X11 into the bloated and ever less useful monstrosity it's become.
Not dead yet? No? Wake me when so, good sir.
One thing you didn't notice is Wayland is using those same hardware drivers that were built for X. Don't expect different performance in anything other than windows and widgets.
First.. this thread is already amazing for the shit being peddled, and the non factual based opinion.
From what I've read, the X devs don't like X. They don't think its network transparent, and they really don't like this idea that X is it.
They are trying to fix a lot of problems through wayland. It seems to me that Linux should really put a lot of weight behind wayland, not so it purely replaces X, but so the underlying work can be done to find the best solutions.
X has serious problems. And these are not likely to be fixed by throwing more into X.
These Devs seem to laugh at people who 'defend X'. And I'll take theor view over that of the less than educated baying mob..
We`re all equal
Too many flames in these weekly Wayland discussions and not enough facts (or maybe the facts are downmodded; I've gotten to the point where if I look at a wayland article, I don't read all of the comments).
So, I just spent 5 or 10 minutes skimming the Wayland FAQ and architecture diagram.
For comparison, when running X, you might have an ordinary window manager or you might have a compositing window manager. The Wayland model is that it *is* a compositor that provides both window manager functions and some of the functionality of an X server.
Intentionally misstating things rather badly, it sounds like the reason Wayland doesn't support remote displays is because it also doesn't support local displays! More accurately, wayland supports local displays (of course), but unlike X11 provides no way to render to them. Wayland doesn't do rendering; it apparently "just" knows how to swap video buffers to a display device and coordinate buffers between multiple clients.
I'm thinking that, for example, if you want to write a graphical app, you might target OpenGL or cario and then expect your code to work in both Unix (with X) and on Windows (without X). With Unix/X, I'd expect an opengl library that handed X primitives to the X server. With Wayland, you'd apparently have an opengl library that rendered to a buffer and then handed the buffer off to the Wayland compositor.
So, Wayland isn't doing some of the things we'd expect an X server to do. Wayland is never working with drawing primitives. It seems obvious that you'd never be able to run apps that use the old X toolkit libraries against Wayland without an X server in the picture. And, the FAQ admits this and notes that you'll need an X server in addition to Wayland for the foreseeable future.
However, as others have noted, an obvious question is how efficiently a "native" Wayland app could be displayed remotely. If the app and its libraries are rendering graphics primitives into display buffers, it seems obvious that low level primitive operations are lost by the time wayland gets the buffers, so you now have to be able to efficiently transmit bitmap deltas. Queue arguments re whether drawing primitives are more efficient or bitmaps are more efficient... OTOH, it seems unlikely that apps would include their own rendering code instead of using as library. So, we can hope that the libraries offer both wayland and X backends, I guess.
Not an X server developer nor a Wayland developer. I'm sure I garbled things somewhat, but perhaps someone could clarify the mistakes and help take a portion of the FUD out of the weekly Wayland discussions.
Looking forward to Wellesley and Woburn. Then maybe Winchester and Weymouth, Wakefield, probably not.
How about we run the next article on Wayland when it's an actual replacement for X, not a Linux-specific extra layer of bugs sitting between the X server and graphic drivers?
I always find these stories really confusing. Weston was the next town over.