So..... why are the wayland developers making a hardware specific backend for weston anyway? Is every arm board and intel and amd chip lines going to need specific backends for weston? What's the point in this?
Announcement
Collapse
No announcement yet.
Raspberry Pi Gets New Wayland Weston Renderer
Collapse
X
-
Originally posted by Kivada View PostAgreed, they should do a both a $50 model and a $100 dollar model, more options with better performance would draw in more people. Though I'd love to see them focus more on parts that can get fully OSS drivers.
If i'm going to pay a 3-figure sum for a low-powered computer I'd rather spend more on any aftermarket board with an x86 Atom processor that is only a little more power hungry than the Broadcom SoC used in the Pi but has superior processing power. Not to mention all of the benefits that come with the x86 stack such as a wider range of precompiled software available and Flash support.
Comment
-
Originally posted by dh04000 View PostSo..... why are the wayland developers making a hardware specific backend for weston anyway? Is every arm board and intel and amd chip lines going to need specific backends for weston? What's the point in this?
When hardware gets drivers into the Linux kernel and Mesa, or proprietary drivers supporting KMS, GBM, EGL, and GLESv2, we just use the Weston drm-backend with the GLESv2-renderer. That already covers practically all PC hardware.
Also, using dispmanx for accelerating X would be so unimaginably painful, that it's practically not possible.
Comment
-
Originally posted by pq__ View PostBecause in this case it is the only way to support the hardware. It does not offer any of the standard Linux APIs.
Originally posted by pq__ View PostAlso, using dispmanx for accelerating X would be so unimaginably painful, that it's practically not possible.
Comment
-
-
Originally posted by ssvb View PostBy accelerating X, do you mean X11 EGL support for GLESv2? Or RENDER acceleration? Or something else?
The Weston backend hands the display hardware a list of every single visible surface, their stacking order, which transformation(s) should be applied, their position, and so on, and then the VideoCore displays it all with zero software intervention.
This isn't RPi-specific, it's really common on ARM platforms, especially ones targeted towards set-top boxes, in-vehicle, etc.
Comment
-
Originally posted by daniels View PostWhich, right now, isn't possible for them to do because of the userspace code required to interface with the VideoCore. So it can't provide KMS.
Entirely due to limitations in X's architecture.
Quick wayland-related question. How's touchpad acceleration going? Or is still on the "TODO" List? I know you had a lot on your plate so no biggie, just curious.All opinions are my own not those of my employer if you know who they are.
Comment
-
Originally posted by Ericg View PostHeeey look who's back, hey Daniel.
Quick wayland-related question. How's touchpad acceleration going? Or is still on the "TODO" List? I know you had a lot on your plate so no biggie, just curious.
I just wrote a blog post about the RPi stuff with a little more detail though, so I hope that makes up for it. http://fooishbar.org/tell-me-about/w...-raspberry-pi/
Comment
-
Originally posted by daniels View PostHi there! Still on the TODO list, I'm afraid.
I just wrote a blog post about the RPi stuff with a little more detail though, so I hope that makes up for it. http://fooishbar.org/tell-me-about/w...-raspberry-pi/
Once the touchpad work goes (Sorry, laptop user :P So I care about it haha) is that Weston work or libwayland work? Meaning: will Kwin have to copy-paste / re-implement your work or will it be automatically available to them as long as they are using version x.y.z of libwayland?All opinions are my own not those of my employer if you know who they are.
Comment
-
Originally posted by Ericg View PostActually a very interesting read, so thanks for the heads-up. I didn't even realize you had your own blog though looking at it, it seems pretty new haha.
Originally posted by Ericg View PostOnce the touchpad work goes (Sorry, laptop user :P So I care about it haha) is that Weston work or libwayland work? Meaning: will Kwin have to copy-paste / re-implement your work or will it be automatically available to them as long as they are using version x.y.z of libwayland?
And, no problem. I live on a laptop, with a touchpad and tap-to-click. Infuriating when it doesn't work, or is crap!
Comment
Comment