One thing you could do is plugging your monitor straight into the iGPU outputs and using DRI_PRIME only for applications that need the powerful dGPU.

Unless you want to run either everything or nothing on a specific GPU, I don’t think there’s a more convenient way than setting DRI_PRIME per application.

In addition this feature makes debugging and developing KWin much easier because you can just restart the compositor without interrupting your workflow.

Pretty cool in principle, although the default word list on my system is awful for wordle.

I’m surprised he was able to watch Paramount Plus. I would assume that site requires Widevine DRM, and would not assume that it’s available on RISC-V.

As for Blender and Kdenlive not working I’m assuming it’s not because of the ISA like Christopher said, but rather because the board likely ships with crappy GPU driver blobs that only support OpenGL ES and no desktop OpenGL. Which is an important detail that this guy always misses in SBC reviews.

Basically none of your current software works out of the box (you’ll need a special Xorg implementation that works with your Wayland implementation in order to run non-Wayland applications).

I’ve never seen any distro with Wayland that didn’t have XWayland set up and working out of the box, so that’s not something the end user needs to worry about. And “Basically None” is also not true anymore. Practically anything made with GTK3/4, Qt5/6, SDL2, recent Electron versions etc. natively runs on Wayland. It’s mostly games, Wine and a lot of proprietary software that doesn’t.

Most applications are specific to your Wayland implementation instead of a general application that runs in all environments.

Wdym by that exactly? I mean, a KDE application will run just fine on GNOME or Wlroots compositors.

s2idle is unfortunately the only supported state on my system apparently, no deep sleep :(

Reminds me of this…