14:41 <dsc_> arno: deepseek, MIT and self-hosted, fyi

14:41 <dsc_> arno11 *

15:11 <arno11> dsc_: deepseek...yeah just saw it today :P

15:11 <arno11> code seems exactly the same

15:12 <arno11> i mean the client part

15:18 <dsc_> was looking at it yesterday

15:18 <dsc_> seems interesting

15:18 <dsc_> especially due to the licensing

15:18 <arno11> yes indeed

15:32 <arno11> pricing seems difficult to compare as deepseek handles previous requests differently

15:34 <arno11> iiuc, it is far more interesting for long conversations like troubleshooting, compared to chatgpt

15:38 <arno11> anyway, i should rename maemo-gpt to maemo-AI now :)

15:51 <arno11> however there is no file handling atm (apparently)

16:17 <kiva> Here is information how to switch off/on cores on fly with linux to save power: https://community.arm.com/oss-platforms/w/docs/529/cpuidle-hotplug

16:19 <Wizzup> https://mort.coffee/home/wayland-input-latency/ O.o

16:27 <kiva> I would be happy with 24 fps and 42 ms latency with Pinephone :)

16:29 <uvos__> Wizzup: to be fair mutter is particulary bad at this

16:30 <uvos__> Wizzup: to be more fair if he had not used compositing his xorg result would be exactly one frame better too

16:32 <kiva> btw..there is also info about how to set cpu freq on the fly: https://community.arm.com/oss-platforms/w/docs/528/cpufreq-dvfs

16:34 <kiva> It would be nice drive Pinephone like car: four gear (cpus) and accelerato pedal (cpu freq)...

16:35 <kiva> ...seriously it would good some powersavings when battery is under 10%.

16:41 <kiva> I tried switch off core on fly, but Maemo did not allowed do that.

16:45 <kiva> wait a minute, it works!!! htop shows only 3 cores.

16:55 <kiva> have to use su command not sudo, to get it work.

17:03 <kiva> That cpu freq setting on the fly needs more linux knowledge than I have, I can show available settings that are in Pinephone: 648000 816000 912000 960000 1008000 1056000 1104000 1152000, but when I try change it says argument missmatch

17:07 <freemangordon> uvos__: no idea what do WL do, but I assume WL does not use separate scanout buffer for the cursor

17:08 <freemangordon> or, does not render it directly to the front buffer

17:08 <freemangordon> maybe they fix possible cursor tearing this way, dunno

17:23 <kiva> from kernel.org: "The CPUfreq governor "userspace" allows the user, or any userspace

17:23 <kiva> program running with UID "root", to set the CPU to a specific frequency

17:23 <kiva> by making a sysfs file "scaling_setspeed" available in the CPU-device

17:23 <kiva> directory.". I think that Leste has not have governor "userspace" so I cannot have scaling_setspeed...someboy who knows more can correct me, I hope I am wrong.

17:29 <Wizzup> kiva: yes, we use this on d4

17:32 <kiva> On PP scaling_available_governors shows only: performance schedutil

17:33 <Wizzup> well we manually set them to off

17:44 <kiva> PP works fine with one core. Not even feel slow in light Firefox use.

17:44 <kiva> with defaul cpu freq.