robertoj

The waveshare clones may not work with panel-mipi-dbi, because these LCDs are not purely SPI. They have a SPI-to-parallel chip which allows the LCD panel to work in parallel mode. Maybe they will work, but I don't own any waveshare LCD. There's a driver inside the kernel for waveshare SPI LCDs (ILI9486_DRM or something like that), but I still haven't seen any example of anyone using it.

I don't own any waveshare LCD. I am not sure what to suggest, except that I believe it will only work with a "ili9486_DRM" (can't remember the exact name) driver ko. It is made explicitly for waveshare SPI LCDSs, and you must activate within the armbian build script process.

No, it wont work. I have made another thread just for the orange pi zero 3 and ili9488 https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/#comment-208446 Change the GPIOs to match your wiring and connections.

I am glad that you have the first 15% done: get your kernel module in the OS, and the uboot accepting the DTBO Now you are stuck in correcting the DTS, so that it configures the SPI pins correctly. My last advice for you (through this stage) is: make sure you don't have anything else using SPI pins. Deactivate "spi_dev" in armbian-config. Since I only had experience with H3 and H618 CPUs, I can't help with confidence. Post your question in the appropriate Rockchip forum section for up-to-date reliable advice. I can say that Radxa/Waveshare DTS is very out of date: it uses the fb_ili9486, which is "framebuffer" (poor fps), instead of the modern "DRM" display driver (high fps, will allow wayland). You should stay with that DTS with fb_ili9486, because it is still the closest starting point for you, and when you have it working, claiming all the GPIO pins needed, I can help again to use the DRM driver panel-mipi-dbi. Regarding MISO and MOSI, I only meant to change that nomenclature in the graphic that you show in the forum. I did't mean to change it in the DTS, if that's how other people make it work. Maybe you need to have the full linux source, so you can decompile the DTBO correctly, showing the gpio pin addresses or symbols. Is it possible that you get the Radxa/Waveshare original DTS?

The first post reads "your mileage may vary" and "the latest kernel will work best" Start by recompiling armbian for your Rockchip SBC, with the edge kernel option, then follow the ffmpeg install instructions If it doesn't work, try the older Ubuntu, and both Debian options

If you already checked "dmesg|grep panel-mipi" and "dmesg|grep spi", check this: * share which LCD you are using. Half of those LCDs are waveshare clones, which need a different driver. My DTS works in the RED LCDs. * Look at the uboot messages in the serial port output. Does it confirm it is finding your dtbo and using it? * verify that panel-mipi-dbi.ko exists in the modules folder. I know it is not preselected by default within the linux configuration menu * Search the word "pinctrl" in this thread https://forum.armbian.com/topic/44191-orangepi-zero-lts-ili9341-tft-lcd-and-later-orangepi-zero-3/#comment-204741 To confirm that the kernel driver is using the gpio and spi pins * send link of the rock3c DTS you are referencing, to see an example of how GPIOs are configured * correct the gpio pin map you shared. Instead of tx/rx, use MOSI, MISO. Highlight and label clearly the CS0, CS1, RESET, DC, IRQ * explain how those gpio numbers gpioX,XX transform into the DTS gpioX XX 1/0 If you at least get noise in the LCD, you are 50% done (and maybe you will get lucky in the last 50%)

Can you copy those dtbo's to /boot/user-overlays (maybe they will need renaming) Then activate them in armbianEnv.txt? https://docs.armbian.com/User-Guide_Armbian_overlays/

Oh I get it. Since you are using another distro with newer versions of everything, my effort to build ffmpeg and mpv in Debian Trixie LOOKS like a backport to you XD upon reading your comment again, I understand the consequences of upgrading ffmpeg from source (Debian Trixie's ffmpeg is version 7.1.2) According to: https://forums.linuxmint.com/viewtopic.php?t=457495, I would need to check with "apt-rdepends -r ffmpeg"

I thought this was the best way: official latest mpv + pull request i am not trying to backport it. I want to make it work in trixie.

The ffmpeg discussion posted a way to test the code (at the bottom of https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20847 ) *install all the ffmpeg dependencies, then: $ git fetch -u https://code.ffmpeg.org/Kwiboo/FFmpeg v4l2request-v3:Kwiboo-v4l2request-v3 $ git switch Kwiboo-v4l2request-v3 * compile and install Then rebuild mpv+PR14690 (https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/page/5/#findComment-226567)

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.