Guido Günther @agx@librem.one

@purism and here's @merge 's update for #linux 5.9 /5.10 https://puri.sm/posts/purism-and-linux-5-9-and-5-10/

@linmob that's perfectly fine - you should do what you enjoy! 🚀 Thanks for your videos so far!

@linmob with that argument demoing distros would also be moot since that's also simple. I think the point is to show how things work, what the current workarounds are and what to do (even when simple).

As of todays #linux-next (https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tag/?h=next-20210112) you can run the #librem5devkit without any additional patches using the default mainline arm64 #defconfig. This means distributions can enable it without trouble from #linux 5.12 onwards. The #librem5 itself needs some more work but it builds a lot on what we have for the devkit.

@linmob what about #HowDoI series like: how to sync calendar, how to backup, how to get org-mode, how to play doom, how to write your first app, ...?

@purism It's a bit dated (was already written a couple of weeks back but afaik @merge is already working on update to cover 5.9 and 5.10. There's also more in 5.11.

@linmob Great! As a data point: I'm running #phosh on about a handful of different devices (#librem5, laptops, "media center" (which is basically a laptop attached to a TV) with #PureOS or #Debian and it's pretty stable there) so version comparisons and reviewing your distros patches may help).

@linmob if phosh (I assume you mean the session) crashes for you, you really want to check with you distro since it's fairly stable over here with PureOS for daily usage. Figuring out which component fails and gathering backtraces would be the first step (https://honk.sigxcpu.org/con/phosh_overview.html)

@cogitri @purism yes, it's a NexDock that provides keyboard/trackpad via usb and the librem5 feeds display via usb-pd alt-mode.

@joshfowler @purism send patches!

Besides the scaling from yesterday #phosh now also handles single / join display mode via GNOME Settings (arranging outputs, also changing resolution, rotation). There's bugs to be fixed in #phoc and #phosh to make this fully reliable but if you're careful it's already pretty useful:

#librem5 #gnomeonmobile @purism

Temporarily need more screen space with #phosh? Just scale to 100% instead of 200%:

@purism #librem5 #gnomeonmobile

@bart wonder how that happened, fixed now. Thanks!

#phosh in numbers 2020:

commits: 759
distinct authors (incl. i18n): 40
releases: 18

Thanks everyone!

While we had enabled power saving for the vivante gpu on the #librem5 since some time we couldn't power off the corresponding regulator (power supply) since the phone would hang then. Turns out we just didn't give it enough time to come back up. Fix is already merged into linux-next: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=3b66e4a8e58a85af3212c7117d7a29c9ef6679a2

#etnaviv #librem5 #batterylife

I've put together a short overview on #phosh and closely related components and how they play together: https://honk.sigxcpu.org/con/phosh_overview.html

#gnomeonmobile #phoc #squeekboard