robertoj

Can you tell us what you did? diff old.dts new.dts

It is too bad that the cursor is shaking even if the driver panel-mipi-dbi is not used.... Now I have a feeling that using a separate software SPI for touch would be the best solution.

Thank you... that is what I need: a 480x320 LCD that works with a driver other than panel-mipi-dbi Do you keep having problems with cursor shakiness? Any screen redraw "garble"?

Going, I see that you worked on some SPI patches previously ... have you tested SPI in opiz3, under Linux 6.12? I found that the raspberry pi people are using panel-mipi-dbi-spi successfully under 6.12 https://forums.raspberrypi.com/viewtopic.php?p=2290196&hilit=panel+mipi+dbi+spi+6.12#p2290196

Process of using a kernel config from a file Copy the config file from /boot folder to build/userpatches Then rename: $ mv config-6.11.9-edge-sunxi64 linux-sunxi64-edge.config cd .. ./compile.sh I get this compilation error: It seems that a wifi driver is in 2 folders... I will see which kernel driver I should remove ...first trying removing mfd/ac200 I don't know if has improved anythig... but I see these new build errors:

Yes. I will try again when I get back home, along with re-including some armbian patches related to SPI Own reference:

Is anybody having success with ilitek LCD display, or SPI in general? I am trying 6.12 with my orange pi zero 3, but the LCD just remains white. When I switch back to my microSD with Linux 6.11, it works with no problem (ili9488+ads7846)

Can somebody with an orangepi zero 3 try my dts? It seems that either the patches in NickA's codebase make it incompatible, or linux 6.12 changed the DTS. https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/#findComment-208446 ili9488-ads7846.dts: I am able to do #armbian-add-overlay ili9488-ads7846.dts normally with armbian official and linux 6.11 But with this github's armbian build, I get in uboot: Applying user provided DT overlay ili9488-ads7846.dtbo failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND base fdt does not have a /__symbols__ node make sure you've compiled with -@ Error applying DT overlays, restoring original DT Hmm, I found that my armbian build didn't create a /boot/dtb/allwinner/overlay/ folder I copied the "overlay" folder, from my working armbian microsd, with linux 6.11, to this linux 6.12 microsd... I still get the same error: can't use my dtbo (I needed to make my own build, because I need to activate panel-drm-dbi.ko)

i dont know if this is new, but i see a ili9486 driver in the kernel config, which is unselected by default. Warning.... I just looked at some of the code in the linux mailing list discussion, and it looks like it is made specifically for 2 raspberry LCD hats * PISCREEN 3.5" 320x480 TFT (Ozzmaker 3.5") * RPILCD 3.5" 320x480 TFT (Waveshare 3.5") Which have a SPI->parallel chip on the circuitboard https://patchwork.kernel.org/project/dri-devel/patch/eb5672abbdb89d7018793c76d7193bfb78a2ea88.1580059987.git.kamlesh.gurudasani@gmail.com/ WDR_s: are you still having good experience with the ili9341 driver for the ili9486 LCD?

Thank you for sharing an image for opiz3 I also downloaded and built the code from your github (branch 202503060) as zip file, so I can start with a minimal image, and work the way up... since I always want a fast booting GUI with openbox... and eventually labwc

No. The driver for h264 encoding does not exist

This is the closest I can find https://forum.armbian.com/topic/26551-video-encoder-using-mainline-kernel/ https://gregdavill.com/posts/allwinner-s3-videoencoders/ https://linux-sunxi.org/Cedrus

Have you ever seen the OPIZ2w (or OPIZ3) doing HW video encoding in another Linux? Where did you find this cedrus driver? What does the website claim it can do? Where did your OS image come from? What DTS modifications did you mean? Why not just a DTS overlay?

When the driver is configured correctly for the orange pi zero 3, everything will look correct from inside the operating system and the SPI port will be clocking out bits. But the LCD is a one-way communication device. The orange pi zero 3 will never know something has failed The ILI9486 LCD's default byte ordering, color format, etc, may be different from the ILI9488. You should find one example of ILI9486 running in raspberry pi, arduino, etc and find the initial byte command sequence. See how it differs from the KungFuPancake's txt file. Make changes to the txt file one by one line, toward being closer to the ili9486 byte sequence you find elsewhere. If you are starting with a DTS that uses the "ilitek,ilixxxx" driver, and change it to "mipi-dbi-spi", remember to change the RESET pin definition (see my other ILI9431 thread for explanation)

Those LCD parameters where you found differences are: PGAMCTRL (Positive Gamma Control) (E0h) NGAMCTRL (Negative Gamma Control) (E1h) (See the ILI9488 PDF I posted) I don't know what they do exactly, but I guess they control pixel voltage, given a R, G or B digital value. I think that you can worry about it, after everything else works.