Sebastian Krzyszkowiak @dos@librem.one

Also, it looks like NXP has picked up their Cadence HDMI/DP bridge/PHY driver upstreaming effort again, which is a great news as it's one of the biggest things we carry in the downstream #librem5 tree!

https://lore.kernel.org/lkml/20260407-dcss-hdmi-upstreaming-v21-0-4681070ab82f@oss.nxp.com/T/

Linux 7.0 has now been tagged, coming with 19 commits upstreamed from the Librem 5 tree - two by NXP and the rest by yours truly on behalf of @purism. Three more are already queued for 7.1.

While the mainline kernel still can't drive the display without extra patches, it's very close now 👀

#linuxmobile #mobilelinux #linux #kernel #librem5 #mainline #linuxphone #linuxsmartphone #shotonlibrem5 #purism #nxp #imx8mq #cats #catsofmastodon

Protip: GTK can do hardware video acceleration using V4L2 on e.g. #Librem5, but only if you let it.

Adding "--device=all" to overrides lets it be used in #Flatpak apps that don't specify it in their permissions already, such as #Tuba.

https://github.com/flatpak/flatpak/issues/5524

#mobilelinux #linuxmobile

If you happen to maintain a distro that runs on the #Librem5, then please be aware that all the known issues resulting in the modem dropping out from the USB bus have been resolved *years ago* already. This shouldn't happen even with runtime power management enabled if configured properly.

If you still see that happening on your distro, feel free to hit me up on Matrix and we'll work together to have your distro set up well.

#linuxmobile #mobilelinux

The #Librem5 has properly detected chargers using BC1.2, Type-C and PD signaling for years now, but it struggled with sources that couldn't actually provide the advertised current (which could happen with buggy chargers/docks, broken or poorly made cables etc.). It would attempt to draw power, drop below voltage threshold, disconnect, and then do it all again once the voltage went back up to a good level in an endless loop. Good news: this behavior is about to be gone 😁 #mobilelinux #linuxmobile

It's nothing new and has even been proposed for upstreaming years ago, but I wasn't aware until now. Apparently it broke some iMX7 platforms, but could still be something worth having downstream.

NXP has published their 6.18-based kernel tree and while browsing it I have noticed that they apparently found a way to support custom horizontal strides with mxsfb (by using some undocumented leftover IP for EPDC panels that imx8mq doesn't support). This may be interesting as it potentially opens a way to use linear PE in #etnaviv with the #Librem5's internal screen, so the GPU could render directly to the scanout surface without having to resolve its tiled buffer to linear afterwards. #imx8mq

Despite of its enormous codebase it wasn't that hard to look around and find relevant stuff - the GTK layer is fairly thin. The hardest part was to compile it, but running distcc on a Steam Deck sped it up well 😄

We still need to:
- emit pointercancel when the browser takes the touch gesture over
- not change scrolling targets during scrolling just because a new one "flew" onto the cursor/finger
- have some thresholds to differentiate between vertical and horizontal scrolling

All my #WebKit merge requests have been merged. Now #WebKitGTK supports touch PointerEvent API, touch point coordinates are fractional, synthesized mouse events are unbroken and both WebKitGTK and WPE WebKit handle pointer capture and release according to the spec. This should considerably improve compatibility of #Epiphany (#GNOME Web) with touch interfaces.

There are still some more things to fix in there, maybe someone in #mobilelinux #linuxmobile community would like to give it a try?