pimox7 VS libcamera

Proxmox [1] will see a boost in popularity, good. I'm using the free version in combination with the backup server on both small (several RasPi 4's spread over several countres running the 'PiMox' [2] port) as well as medium (DL380) sized systems and find it to be a stable as well as practical platform.

[1] https://proxmox.com/en/

[2] https://github.com/pimox/pimox7

Starting with the https://github.com/pimox/pimox7 website I now have a four node HA environment (all on Pi4's, 4GB RAM each, 16GB SD card each) along with a 500GB slice of space on my home SSD Synology (for all VMs, etc). As of this moment all four are up, talking to each other, and I'm running a PiHole instance with high availability enabled (or at least that is what the instructions I followed tell me).

Same experience here, the PiMox repository on GitHub is I.m.o the official unofficial pve ARM-port. I really hope the pve team is going to either support or find a way to leverage the work already done by Tim & the rest, it would be a waste not to.

https://github.com/pimox/pimox7 Look at this

For anyone who wants proxmox on their ARM device, check out pimox

Not massively recommended but version called pimox works okay https://github.com/pimox/pimox7

I wonder if pimox (Proxmox hypervisor) will run on it.

pi@rpi5:~ $ sudo apt show libcamera0.1 Package: libcamera0.1 Version: 0.1.0+rpt20231122-1 Priority: optional Section: libs Source: libcamera Maintainer: Serge Schneider Installed-Size: 1,755 kB Depends: libcamera-ipa, libatomic1 (>= 4.8), libc6 (>= 2.34), libdw1 (>= 0.158), libgcc-s1 (>= 3.5), libgnutls30 (>= 3.7.3), liblttng-ust1 (>= 2.13.0), libpisp1 (>= 1.0.2), libstdc++6 (>= 12), libudev1 (>= 183), libunwind8, libyaml-0-2 Breaks: libcamera0 Replaces: libcamera0 Homepage: https://libcamera.org/ Download-Size: 476 kB APT-Manual-Installed: no APT-Sources: http://archive.raspberrypi.com/debian bookworm/main armhf Packages Description: complex camera support library libcamera is a complex camera support library which handles low-level control of the camera devices, providing a unified higher-level programming interface to the applications.

Red Hat seems to be putting a lot more work into desktop Linux lately. They added extended lifecycle options to RHEL Workstation with RHEL 9, they've been doing a bunch of work on desktop Linux technologies (PipeWire, libcamera, HDR displays, etc.), and they've recently worked with AWS to launch a virtual desktop option in the cloud.

https://github.com/kbingham/libcamera

the libcamera stack moves all of that control loop stuff into linux userland, so you would think there are no secrets left

but the actual register writes to drive the ISP are still in the blob, and libcamera is just telling the blob how to tweak every knob in the hardware

it makes no sense why they have opened it up so much, yet still insist on keeping that last bit a secret