If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Once such chips are available, I'm sure you will see it.
For now, IFC6410, quad krait.

This rpi stuff is boring as hell. Cheap sure, but in this case, you really do only get what you pay for, which was obsolete even before they came up with the idea. It would be far more interesting if they actually updated the hardware to keep at least consistently far behind the "current standards".

If your objective is running a graphical desktop, rpi is useless. About its only use is in automation/remote control.

That may mean that wayland isn't versatile enough to be supported from driver space.

No it doesn't? I mean I guess it could be possible to write kernel wrappers around these platform specific interfaces but that has nothing to do with Wayland itself. The thing is that if you want to take use of hardware specific functionality, you need to support hardware specific functionality. That's true for every display server, compositor and graphics framework.

Originally Posted by TheOne

Imagine every hardware manufacturer doing custom changes to wayland/weston in order to support their specific graphic chips capabilities.

The idea is that drivers expose KMS/EGL interfaces that Wayland uses but if there's some hardware specific features that would be benefitical for a compositor then it probably should be added, then again that's true for every display server and compositor. NVIDIA will likely never support the Linux KMS interface so similar functionality has to be exposed to Wayland compositors in some otherway hence a NVIDIA backend. I don't think there's anyway to escape that.

That may mean that wayland isn't versatile enough to be supported from driver space.

Imagine every hardware manufacturer doing custom changes to wayland/weston in order to support their specific graphic chips capabilities.

Wayland is versatile because it is backend-agnostic. You can use whatever backend you want for Wayland and Wayland itself will work the same, it's the backend that needs to be different for different hardware and different situations.

Like, you can have a backend for gpu egl drivers, you can have another backend for software rendering, another backend for some other type of drivers (android drivers maybe)... that's versatile.