ozacas

@going a pretty broad question, but i'll try 😁
 
hardware accelerated video processing on rk3588 and linux - https://github.com/blakeblackshear/frigate/discussions/11502
hardware accelerated NPU via linux - https://github.com/airockchip/rknn-toolkit2/
large language models (LLM's) using NPU - https://github.com/airockchip/rknn-llm
 
Its important to understand you will need a compatible kernel driver to connect to the hardware - most likely the best option is the vendor kernel 6.1.75 with armbian. Also this is a rapidly evolving space - hard to keep up!
 
Depending on what you read though, often the CPU can offer better performance, although it is dependent on your requirements and the ability to utilise the hardware effectively.

IIRC he prefered to stay independent which I understood. Though that was a year ago where his motivation was still high.
 
Now things have changed. We told him he'd be more than welcome to join forces and share the burden.

@Benjamin Sonntag I think you want to ask aplay to list recording devices rather than playback devices - I have a different rk3588 device and it shows:
 
acas@t6:~$ aplay -C -l **** List of CAPTURE Hardware Devices **** card 0: rockchiphdmiin [rockchip-hdmiin], device 0: rockchip-hdmiin i2s-hifi-0 [rockchip-hdmiin i2s-hifi-0] Subdevices: 0/1 Subdevice #0: subdevice #0 card 1: realtekrt5616co [realtek,rt5616-codec], device 0: fe470000.i2s-rt5616-aif1 rt5616-aif1-0 [fe470000.i2s-rt5616-aif1 rt5616-aif1-0] Subdevices: 1/1 Subdevice #0: subdevice #0  that is with the overlay enabled as described 

the original system that started the thread, after (failed) armbian-install run, looks like this with the USB stick used to boot the system:
 
acas@uefi-arm64:~$ df Filesystem 1K-blocks Used Available Use% Mounted on tmpfs 1605708 12816 1592892 1% /run /dev/sda2 59094688 5773640 52631248 10% / tmpfs 8028524 0 8028524 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock efivarfs 64 42 23 65% /sys/firmware/efi/efivars tmpfs 8028524 0 8028524 0% /tmp /dev/sda1 258094 150 257945 1% /boot/efi /dev/zram1 47960 2152 42224 5% /var/log tmpfs 1605704 60 1605644 1% /run/user/1000 acas@uefi-arm64:~$ fdisk -l Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors Disk model: Fanxiang S501Q 1TB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: A3C2AE18-4086-48D2-B1F9-90B315BAB1FA Device Start End Sectors Size Type /dev/nvme0n1p1 2048 2000408575 2000406528 953.9G Linux filesystem Disk /dev/sda: 57.62 GiB, 61865984000 bytes, 120832000 sectors Disk model: USB Flash Drive Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 611F458A-F35E-B04A-9F22-8E04707F1E17 Device Start End Sectors Size Type /dev/sda1 8192 532479 524288 256M EFI System /dev/sda2 532480 120831966 120299487 57.4G Linux root (ARM-64) Disk /dev/zram0: 7.66 GiB, 8221212672 bytes, 2007132 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram1: 50 MiB, 52428800 bytes, 12800 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes  
note how there is no EFI partition on the NVME drive. But the image from the armbian build framework has an EFI system partition and is what i'm using to boot the system right now via the USB stick.

the box i was referring to has the following -
acas@opi2:~/build$ fdisk -l Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors Disk model: Fanxiang S500Pro 1TB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x4f11c8df Device Boot Start End Sectors Size Id Type /dev/nvme0n1p1 2048 411647 409600 200M ef EFI (FAT-12/16/32) /dev/nvme0n1p2 411648 2000409263 1999997616 953.7G 83 Linux Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: ASM1153USB3.0TOS Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 33553920 bytes Disklabel type: dos Disk identifier: 0x2eeae39f Device Boot Start End Sectors Size Id Type /dev/sda1 2048 8390655 8388608 4G b W95 FAT32 /dev/sda2 8390656 50333695 41943040 20G 83 Linux /dev/sda3 50333696 3907029167 3856695472 1.8T 83 Linux Disk /dev/zram0: 3.74 GiB, 4014276608 bytes, 980048 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram1: 50 MiB, 52428800 bytes, 12800 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes  
ah... i have a USB connected sata adapter ssd as /dev/sda - forgot about that. Maybe that is accidentally providing boot (used to be connected to an rpi4)

Dont forget that you can now use the vendor 6.1.x kernel now for hardware acceleration using MPP -
 
acas@t6:~$ ls -l /dev/rga crw-rw---- 1 root video 10, 121 Aug 17 15:12 /dev/rga acas@t6:~$ ls -l /dev/mpp_service crw-rw---- 1 root video 241, 0 Aug 17 15:12 /dev/mpp_service acas@t6:~$ uname -a Linux t6 6.1.75-vendor-rk35xx #1 SMP Thu Aug 8 17:42:28 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux acas@t6:~$ hostnamectl Static hostname: t6 Icon name: computer Machine ID: 8a38793a5b9543f2a8467803940786e8 Boot ID: 0840de02a4a249e884141dee335ede77 Operating System: Armbian-unofficial 24.8.0-trunk noble Kernel: Linux 6.1.75-vendor-rk35xx Architecture: arm64 dont need to be stuck on 5.10 for MPP support. Works fine with rkmppenc just as for kernel 5.10 series.
 
The only quirk is that for Ubuntu 24.04 you have to hack/build rkmppenc from source at the moment.