robertoj

No. I haven't tried anything new. My previous attempts compiling mpv in Trixie were unsuccessful. I want to try it again by compiling and installing this new ffmpeg+v4l2 first, then trying compiling mpv again. You should try it too

Thank you for sharing it Can you include these specifications, for quick reference for future readers? Board, Debian version, Kernel, Graphics (console, X11, wayland)

There's a new version of the kwiboo ffmpeg+v4l2request function https://code.ffmpeg.org/Kwiboo/FFmpeg/src/branch/v4l2request-v3 And it was shown as a work in progress in the ffmpeg community https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20847 Then, it was noticed in the mpv community https://github.com/mpv-player/mpv/pull/14690#issuecomment-3500141427 They previously said that v4l2request first needs to be integrated in ffmpeg officially, then mpv would start working on v4l2request This is needed, to have mpv+v4l2request compiling successfully and working under Debian Trixie (my experience)

In bookworm, trixie or noble?

Can someone confirm that xwayland is working in the other wayland desktops in armbian? I can't make it work in labwc

Share your DTS. It is the most challenging part of this. We can customize, based on SBC model.

Start with this DTS and change the GPIO for your OPIZ3 https://github.com/raspberrypi/linux/blob/rpi-6.12.y/arch/arm/boot/dts/overlays/piscreen-overlay.dts Or start with your DTS and change the "compatible" line to "compatible=waveshare,rpi-lcd-35" and copy the other parameters of piscreen-overlay.dts if needed Let us know if it works

Getting video acceleration is realtively easy in bookworm, but making it work in Trixie would be newsworthy

It all depends on the GUI apps you want to run. Web browser: at least 4GB Your own Python GUI app: 1GB 16GB storage is fine. "A more advanced build framework" only refers to the laptop you use to compile your own Armbian OS... it doesn't refer to the SBC where you will run it.

Yes, CONFIG_TINYDRM_ILI9486 is the kernel module for that model of LCD with DRM. There's another thread explaining how to use it. I think you can use udev rules to force SPI LCD as /dev/fb0 and HDMI as /dev/fb1 always.

I noticed this problem a long time ago, but now I feel it is important to fix it: I get a slim black bar on the left side, and a portion of the pixels on the right get "cropped" because they don't fit in the LCD display area? I get the left 2 pixels of the screen "cropped", so in console, the first left-side are always missing the left pixels. Do you get the same in your LCD? Do you know a way to fix it? I am talking about this LCD: RED PCB LCD https://www.aliexpress.us/item/3256802847521952.html?

In that case, dont try my solution: it is for the red ili9341. If you search ili9486 threads in this forum, that same blue LCD is ili9486... so you were wrong in calling it ili9341 in the first place If you have time, find another solution to get you a DRM frambuffer (instead of a classic FB). Then you can enjoy smoother animations and video. Regarding displaying boot messages to the LCD, instead of HDMI. I don't know, but it may be because your HDMI is /dev/fb0 and the LCD is /dev/fb1 Will you use X11?

Try this solution for the orange pi zero LTS, which is the same chip as the opiPC, but change the pin definitions to what you have. Do you have a 480x320 ili9341? Which one is it?

If anyone in interested in a lightweight wayland desktop, inspired by openbox, you should try labwc. In orange pi zero 3, we need to stay in bookworm to get video acceleration, so this guide helps build labwc in bookworm As a greeter, I chose pi-greeter, because it is the lightest login manager I could setup, without any X11 https://github.com/robertojguerra/opiz3-labwc-setup I am open to read any improvements, or show me how I could make deb packages. In the near future, I will make a step-by-step video tutorial in Youtube.

For video acceleration, you need to stick with Bookworm.