Sebastian Krzyszkowiak @dos@librem.one

@krogulczyk Jeżeli wygrywa ktoś raz na miesiąc, to w ciągu Twojego życia będzie takich osób ok. tysiąc, więc to chyba nic zaskakującego, że możesz nikogo takiego bezpośrednio nie poznać (a niebezpośrednio to raczej już znasz w ok. trzecim stopniu)

@krogulczyk Ale skąd pomysł, że nikogo takiego nie znasz w szóstym stopniu oddalenia? Hipoteza zakłada, że w szóstym stopniu znasz już całą ludzkość.

Gdy weźmiesz dwie dowolne osoby w kraju to w zasadzie wystarczy, by każda z nich znała kogokolwiek, kto zna jakiegoś celebrytę - a to wcale nie musi być najkrótsza możliwa ścieżka.

@wonziu A w wymaganiach na senior developera: "Active use of AI tools in daily development workflows, and enthusiasm for helping the team increase adoption" 😂

@wariat @emill1984 @LeoDar @grymas1000lecia Ale nie musisz instalować Steama. Możesz pobawić się tą samą technologią za pomocą takich narzędzi, jak choćby systemd-nspawn, lxc, podman czy docker.

@wariat @emill1984 @LeoDar @grymas1000lecia 2010 dzwoniło i pytało, gdzie się podziewasz. Jakoś Steam bez problemu instaluje natywne wersje gier bez roota i doinstalowywania czegokolwiek w systemie, ciekawe jak to działa... 😉

@pavel You can already get 10-bit 25 FPS without having to put extra plumbing between kernel drivers for questionable reward.

It doesn't look particularly useful for the use-case of streaming through USB 3.0 either.

With 2 lanes, at 4K we get 30 FPS with 8-bit and 25 FPS with 10-bit.

8-bit may fit into available USB 3.0 bandwidth, though it's already getting tight. 10-bit won't fit without repacking, cause we're getting 16-bit values from the CSI receiver - so you likely won't stream out more than 15 FPS anyway.

So 2 lanes it is!

This would translate to about 33 FPS when cropped to 4K.

We should be able to record up to 5 seconds of 10-bit 4K 30 FPS video to RAM, assuming 2GB of free space there. Is that worth the effort? 😁

@dubstar_04 Oh, and the 333 MHz pixel clock itself puts the hard limit on the framerate at 13 Mpx at about 25 FPS regardless of bit depth, and that's without counting blanking or protocol overhead - so we're hitting the ceiling anyway even with lane bandwidth left to spare.

@dubstar_04 5 Gbps* 😂

@dubstar_04 You can go slow enough with 3 lanes, but only for 10-bit pixels; with 8-bit ones, the slowest setting is too fast again.

4 lanes could theoretically work in this setup with 16-bit pixels, but even if the sensor could zero-pad its values to 16 bits it wouldn't let you achieve more FPS anyway, because then you'd hit the maximum supported MIPI CSI-2 bandwidth (5 Mbps).

So there's basically no combination of settings where 4 lanes are usable in this setup 🤷

@dubstar_04 It's a result of two limitations combined:

1) i.MX 8M Quad's MIPI CSI-2 receiver handles one pixel at each rising edge of the UI clock, which has a maximum rate of 333 MHz. This means the bandwidth you can realize is effectively limited by the used pixel depth.

2) The 13 Mpx Samsung sensor can't really go slower than about 1 Gbit per lane with 25 MHz MCLK - various clocks go out of their ranges when you try.

So it turns out that with 4 lanes, it just can't go slow enough 🐌

Actually, we could probably go up to 21 FPS with 10-bit by using 3 lanes, but not sure if that's worth the effort.

So I finally understand why 4-lane MIPI CSI-2 doesn't work with the #Librem5's big cam.

Turns out it's not going to work - but I now at least understand why 😂

(this limits streaming at full res to about 16 FPS 10-bit and 20 FPS 8-bit instead of the sensor's 30 FPS, but you won't really be able to process it at this speed anyway so it's not a big loss; lower res can still work with higher framerates; with the current driver up to 120 FPS but it could go even higher)

#linuxmobile #mobilelinux

@RootMoose It's much easier to make an "expensive premium device" than "decent enough, affordable" one. It's not a non-US company (though does it matter than much with FLOSS?), but Purism has pretty much already trodden that path.

@dilmandila Check out apt-offline if you're on a Debian-based distro.

@peja Unless you'd count some weird and complex setups with nested compositors in - no. GNOME Shell does not implement the interfaces Stevia (or Squeekboard) rely on.

@valpackett @postmarketOS That's not the only thing PulseAudio still does better on mobile - if you request filtering through stream properties (like Wys does for echo cancellation on the Librem 5), that won't yet work with pipewire-pulse: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4170