Search the Community

Hi I've made a new kernel Auxiliary Display Driver for TM16XX and compatible LED controllers. This driver supports various LED controller chips, including TM16XX family, FD6XX family, PT6964, and HBS658. It provides support for both I2C and SPI interfaces. I wanted it to manage the hardware on the kernel space while having an easy sysfs user space interface. It also aims to reduce the code to maintain by relaying on existing kernel features instead of recoding them. Plus, you can switch to hardware i2c/spi (instead of software gpio) depending on the pins used. You can use "vfdconf-convert" to convert your existing vfd.conf to its device-tree version. Or you can use the already converted vfd.conf of https://github.com/arthur-liberman/vfd-configurations that are listed in the device table. You don't need to manually edit your device tree, the "make" command will apply the device tree source overlay to your dtb. It comes with a service written as a simple bash script. So it's easily customizable without having to write custom C code. Instructions and source code at https://github.com/jefflessard/tm16xx-display/ Could you please give it a try and report your feedback?

Hi, anyone have already connected a speaker to gpio of lcpi h3 v8 (like orange pi pc). I have tried but im not sure if i2s is enabled on armbian

Hello, since the build for OrangePi Plus 2 is only community maintained (and there is a warning during installation that this build is not suitable for production), I though of using some generic image or a image for a similar board with standard support. Is it a good Idea? Which image should I choose? Thanks for help, Skalistan P.S. there is no tag for "OrangePi Plus 2", so I used the tag for "OrangePi Plus 2E" since it is required to add a tag.

Hi, all I have a development kit board Snapdragon 8 Gen 2 SoC HDK 8550/SM8550/sm8x50. As understand it's more smartphone. Do we have support from Armbian for this board ? If so, can you provide me some info how to install it on sm8550 ? Currently, sm8550 has only fastboot and some AOSP images (u-boot, boot etc)

Hi! Currently try to figure out how to run my freshly builded Armbian using QEMU arm64. According to this tutorial: https://docs.armbian.com/Developer-Guide_Build-Preparation/ I prepare clean Jammy VM. Build using this CMD: ./compile.sh BOARD=qemu-uboot-arm64 BRANCH=current RELEASE=bookworm Build process was going smoothly i pick up two files from output folder: 1) Armbian-unofficial_24.5.0-trunk_Qemu-uboot-arm64_bookworm_current_6.6.29_minimal.img.qcow2 2) Armbian-unofficial_24.5.0-trunk_Qemu-uboot-arm64_bookworm_current_6.6.29_minimal.u-boot.bin Currently boot up process stucked, i can run U-boot and mount qcow2 image using this CMD: qemu-system-aarch64 \ -machine virt -cpu cortex-a57 \ -netdev user,id=net0 -device e1000,netdev=net0 \ -serial stdio \ -bios Armbian-unofficial_24.5.0-trunk_Qemu-uboot-arm64_bookworm_current_6.6.29_minimal.u-boot.bin \ -drive if=none,file=Armbian-unofficial_24.5.0-trunk_Qemu-uboot-arm64_bookworm_current_6.6.29_minimal.img.qcow2,id=mydisk \ -device ich9-ahci,id=ahci \ -device ide-hd,drive=mydisk,bus=ahci.0 U-boot see the drive with rootfs, but during boot process i had this error: Failed to load '/boot/uInitrd' Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid Boot failed (err=-14) Full boot process log: U-Boot 2023.10-armbian (Mar 14 2024 - 01:18:23 +0000) DRAM: 128 MiB Core: 51 devices, 14 uclasses, devicetree: board Flash: 64 MiB Loading Environment from Flash... *** Warning - bad CRC, using default environment In: pl011@9000000 Out: pl011@9000000 Err: pl011@9000000 Net: e1000: 52:54:00:12:34:56 eth0: e1000#0 Hit any key to stop autoboot: 0 Scanning for bootflows in all bootdevs Seq Method State Uclass Part Name Filename --- ----------- ------ -------- ---- ------------------------ ---------------- Scanning global bootmeth 'efi_mgr': Scanning bootdev 'fw-cfg@9020000.bootdev': fatal: no kernel available No working controllers found scanning bus for devices... Target spinup took 0 ms. SATA link 1 timeout. SATA link 2 timeout. SATA link 3 timeout. SATA link 4 timeout. SATA link 5 timeout. AHCI 0001.0000 32 slots 6 ports 1.5 Gbps 0x3f impl SATA mode flags: 64bit ncq only Device 0: (0:0) Vendor: ATA Prod.: QEMU HARDDISK Rev: 2.5+ Type: Hard Disk Capacity: 54564.0 MB = 53.2 GB (111747072 x 512) Scanning bootdev 'ahci_scsi.id0lun0.bootdev': 0 script ready scsi 1 ahci_scsi.id0lun0.bootdev /boot/boot.scr ** Booting bootflow 'ahci_scsi.id0lun0.bootdev.part_1' with script scanning bus for devices... Device 0: (0:0) Vendor: ATA Prod.: QEMU HARDDISK Rev: 2.5+ Type: Hard Disk Capacity: 54564.0 MB = 53.2 GB (111747072 x 512) Device 0: (0:0) Vendor: ATA Prod.: QEMU HARDDISK Rev: 2.5+ Type: Hard Disk Capacity: 54564.0 MB = 53.2 GB (111747072 x 512) <DIR> 4096 . <DIR> 4096 .. <SYM> 28 Image <SYM> 24 dtb <DIR> 4096 dtb-6.6.29-current-arm64 38518 boot.bmp 0 .next <SYM> 28 uInitrd 906 boot.cmd 6040046 System.map-6.6.29-current-arm64 978 boot.scr 49178863 uInitrd-6.6.29-current-arm64 318778 config-6.6.29-current-arm64 38134272 vmlinuz-6.6.29-current-arm64 49178799 initrd.img-6.6.29-current-arm64 KERNEL LOAD ADDRESS: kernel_addr_r : 0x40400000 INITRD LOAD ADDRESS: ramdisk_addr_r: 0x44000000 FDT LOAD ADDRESS : fdt_addr : 0x40000000 38134272 bytes read in 853 ms (42.6 MiB/s) ** Reading file would overwrite reserved memory ** Failed to load '/boot/uInitrd' Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid Boot failed (err=-14) --- ----------- ------ -------- ---- ------------------------ ---------------- (1 bootflow, 1 valid) Any ideas what i'm doing wrong?

I have Armbian running on Banana Pi R1 without networking access. Is this board suppported at all or it is just a waste of time?

There is a uwe5621ds WiFi module on my rk3576 development board. I burned the system image of armsom-cm5-io. After booting, calling the modprobe sprdwl_ng command will encounter the following kernel pannic [ 71.088504] Unable to handle kernel NULL pointer dereference at virtual address 00000000000001d0 [ 71.089376] Mem abort info: [ 71.089655] ESR = 0x0000000096000004 [ 71.090002] EC = 0x25: DABT (current EL), IL = 32 bits [ 71.090490] SET = 0, FnV = 0 [ 71.090784] EA = 0, S1PTW = 0 [ 71.091069] FSC = 0x04: level 0 translation fault [ 71.091509] Data abort info: [ 71.091772] ISV = 0, ISS = 0x00000004 [ 71.092147] CM = 0, WnR = 0 [ 71.092432] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000102e2e000 [ 71.093018] [00000000000001d0] pgd=0000000000000000, p4d=0000000000000000 [ 71.093635] Internal error: Oops: 0000000096000004 [#1] SMP [ 71.094144] Modules linked in: sprdwl_ng(+) sprdbt_tty bnep rk805_pwrkey ufs_rockchip nvmem_rockchip_otp rockchip_cpuinfo ufshcd_pltfrm joydev input_leds ufshcd_core uio_pdrv_genirq uio zram zsmalloc binfmt_misc sch_fq_codel fuse ip_tables ipv6 pwm_blpanel_simple panfrost drm_shmem_helper gpu_sched [ 71.096551] CPU: 5 PID: 2071 Comm: modprobe Not tainted 6.1.84-vendor-rk35xx #1 [ 71.097217] Hardware name: ArmSoM CM5 IO (DT) [ 71.097614] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 71.098246] pc : get_loopcheck_status+0x18/0x20 [ 71.098662] lr : start_marlin+0x7c/0xc4 [ 71.099023] sp : ffff80000e8137d0 [ 71.099330] x29: ffff80000e8137d0 x28: ffff80000a31a910 x27: 0000000000000000 [ 71.099976] x26: 0000000000000000 x25: ffff80000a44e000 x24: ffff80000a670310 [ 71.100621] x23: 0000000000000000 x22: ffff80000a575fa8 x21: 0000000000000002 [ 71.101265] x20: ffff0000c4671810 x19: ffff800009466f1f x18: 0000000000000000 [ 71.101910] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 [ 71.102555] x14: 0000000000000000 x13: 5d494649575f4e49 x12: 4c52414d5b206e69 [ 71.103201] x11: 0000000000000000 x10: 0000000000000000 x9 : ffff800009205260 [ 71.103846] x8 : 00000817c200001f x7 : 696c72616d5f7472 x6 : 617473203a4e4357 [ 71.104492] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000 [ 71.105136] x2 : 0000000000000000 x1 : ffff0000c24aeac0 x0 : 0000000000000000 [ 71.105781] Call trace: [ 71.106011] get_loopcheck_status+0x18/0x20 [ 71.106397] sprdwl_probe+0x2c/0x330 [sprdwl_ng] [ 71.106881] platform_probe+0x70/0xc0 [ 71.107224] really_probe+0x1cc/0x390 [ 71.107570] __driver_probe_device+0x140/0x158 [ 71.107980] driver_probe_device+0x48/0xd0 [ 71.108356] __device_attach_driver+0x110/0x124 [ 71.108775] bus_for_each_drv+0xa4/0xd0 [ 71.109129] __device_attach+0xf0/0x174 [ 71.109482] device_initial_probe+0x1c/0x28 [ 71.109870] bus_probe_device+0x38/0x9c [ 71.110223] device_add+0x558/0x694 [ 71.110545] platform_device_add+0xe0/0x218 [ 71.110931] unisoc_wlan_init+0x54/0x1000 [sprdwl_ng] [ 71.111441] do_one_initcall+0x94/0x1e8 [ 71.111799] do_init_module+0x58/0x1dc [ 71.112152] load_module+0x1820/0x18d4 [ 71.112494] __do_sys_finit_module+0xfc/0x120 [ 71.112894] __arm64_sys_finit_module+0x24/0x30 [ 71.113315] invoke_syscall+0x8c/0x128 [ 71.113656] el0_svc_common.constprop.0+0xd8/0x124 [ 71.114097] do_el0_svc+0xa8/0xb8 [ 71.114406] el0_svc+0x2c/0x54 [ 71.114694] el0t_64_sync_handler+0xac/0x13c [ 71.115082] el0t_64_sync+0x19c/0x1a0 [ 71.115424] [ 71.115424] PC: 0xffff800008ac54c8:

I can't seem to get apt-get update to work, this is a fresh install anyone know the fix? mango@nezha:~$ sudo apt-get update Hit:3 http://ports.ubuntu.com jammy InRelease Hit:4 http://ports.ubuntu.com jammy-security InRelease Hit:5 http://ppa.launchpadcontent.net/oibaf/graphics-drivers/ubuntu jammy InRelease Hit:6 http://ports.ubuntu.com jammy-updates InRelease Hit:7 http://ports.ubuntu.com jammy-backports InRelease Hit:1 https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs vscodium InRelease Hit:2 https://cli.github.com/packages stable InRelease Err:2 https://cli.github.com/packages stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059 Reading package lists... Done N: Skipping acquire of configured file 'main/binary-riscv64/Packages' as repository 'http://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs vscodium InRelease' doesn't support architecture 'riscv64' W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://cli.github.com/packages stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059 W: Failed to fetch http://cli.github.com/packages/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059 W: Some index files failed to download. They have been ignored, or old ones used instead.

I want to understand the feasibility of installing Armbain on a board that is currently Tina Linux. The board has an Allwinner R528 processor and an emmc . The R528 is not a well known Allwinner processor but it is essentially a D1 with two Arm-a7 processors instead of a RISCV processor. It also is a essentially the same processor as a T113-s3 but in a different physical package. I see the mangopi-mq and the nehza have the D1, but I'm not sure it helps. I have a full dts file (3000+ lines) for this board. But what I am failing to get a grasp of is: Given that I that I have a complete dts file, what is the work flow to get Armbian onto this board? What other information and/or files do I need to successfully install Armbian? Am I "barking up the wrong tree" (i.e. am I asking the wrong question)? Should I be looking to install a standard version of Ubuntu or Debian?

Hello everyone, new ARM user here, but long-time GNU/Linux user for about 25 years. I'm trying to install a (preferably debian based) distribution on a newly acquired ARM laptop, a Samsung "galaxy S book" model SM-W767V - this machine is based on qcom's "Snapdragon 8cx" SoC. When i try to boot a generic image (assuming the BIOS/UEFI lists it in the boot menu) it either freezes or reboots at a specific point during the boot process. Where it crashes is always consistent for a specific image, but can differ across different images. The Armbian ones make it past the bootloader and crash at some point during the kernel boot. Has anyone had success installing GNU/Linux on this laptop, and/or can point me to which installer image i should try next? Thanks for any assistance!

Hello everyone, I encountered a "No space left on device (28)" issue while compiling custom firmware and would like to seek your help. The firmware compilation process works fine under normal circumstances. However, after using the customize-image.sh script to install my own applications, the rootfs size became 3285 MiB, and I encountered the "No space left on device (28)" error during compilation. I modified FIXED_IMAGE_SIZE to 6G and recompiled, but the same issue persisted. After mounting the raw file, I confirmed that no additional files could be added. I suspect there’s some parameter restricting this, but I’m not sure what it is. Can anyone provide some hints? Thank you! The compile log: Mount

Hello All, Preface: First time posting, I am not an experienced software developer but have designed a working SBC around the RV1126. I have had some success recently getting video out of an IMX258 camera connected to the RV1126 but I am experiencing a strange issue where the camera feed has a green hue. (see attached picture). I have tried to change variables within the kernel - IMX258.c and many other places to change the auto white balance with no success but have recently come across this thread which may provide better results: https://forum.pine64.org/showthread.php?tid=17067 I do not have the RKISP2_tuner.exe in the camera_engine_rkaiq section of the SDK so was wondering if anyone can point me in the right direction or is able to provide an iq file for the IMX258 camera? Thank you in advance, any help at this point would be greatly appreciated.

Hello Everyone I have added Armbian for the Heltec HT-M2808 Helium Miner https://github.com/armbian/build/pull/6989#event-13647037453 https://heltec.org/project/ht-m2808/ To Compile ./compile.sh build BOARD=rk3328-heltec BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=no KERNEL_CONFIGURE=yes KERNEL_GIT=shallow RELEASE=bookworm You can obviously decide to go with a desktop environment (board has no HDMI) or use a different release. How to Flash 1) Install Rockchip Flash Tools 2) Download bootloader (rk3328_loader_ddr333_v1.16.250.bin) attached here. 3) Boot device into LOADER mode. Plug USB Cable in to back of the unit, powered off. On the back of the device. Use a small pin and hold the reset button (unit powered off) THEN insert the power cable while the reset button is pressed 4) Follow the flash procedure found here. Maskrom Pin If you get stuck and need to reflash, there's a good chance holding the reset button will not work to get back into LOADER mode. To boot directly to MASKROM, you can short this pin Needed 1) Wifi/BT does not work currently 2) SPI not recognized 3) LEDs not working 4) Likely other things, but the OS is 90% functional. rk3328_loader_ddr333_v1.16.250.bin

Hi All, Looking for assistance with getting an old SmartQ5 Mobile Internet Device running with Armbian. I was able to locate Github page (https://github.com/tpruvot/smartq-magicsd) which references booting from SD but need assistance getting armbian compiled and configured for the device. Any help is appreciated! SPECS: Samsung Mobile Application Processor S3C6410 based on ARM11 core at 667 MHz/800 MHz 128 MB DDR 133/333 MHz SDRAM 1 GB NAND FLASH (256 MB usable for storage) AC97 audio codec & PCM 24-bit audio SoC graphics unit, OpenGL ES 1.1/2.0, 4M triangles/sec @133Mhz (Transform only) Integrated Wi-Fi 802.11b/g Integrated Bluetooth 2.0 + EDR 800x480 resolution resistive touchscreen LCD, 4.3", 16.7 million colors SDHC card slot (up to 32 GB) Headphone output power up to earphone 40 mW, frequency Response 20 Hz-20.000 Hz SNR 94dB Internal microphone USB 2.0 OTG port (480 Mbit/s) Runs Ubuntu Linux 2000mAH rechargeable lithium polymer battery Dimensions: 120x74x14mm Weight: 160 g

I just created this account. During the account creation process there was a part where I had to click a checkbox saying that I agree to the forum rules & policies. But I didn't see a link to actually read the policies (I'm usually impatient about these things, I may have missed something obvious). Now, after the fact, I've spent more time looking, and I can't find the forum rules / policies. Is there a post or webpage somewhere detailing what they are?

Hi all, I need to customize the /etc/fstab during the build to mount a mtd partition and also to override some mountpoints with tmpfs in order to reduce wearing on mmc. So, have added the following lines to customize-image.sh: cat <<EOT >> /etc/fstab # Reduce SD wearing by storing log files into ram (no need as overlayroot is used to freeze all the rootfs) tmpfs /tmp tmpfs defaults,noatime,nosuid,nodev 0 0 tmpfs /run tmpfs defaults,noatime,nosuid,nodev 0 0 tmpfs /var/tmp tmpfs defaults,noatime,nosuid,nodev 0 0 tmpfs /var/log tmpfs defaults,noatime,nosuid,nodev,noexec 0 0 tmpfs /var/lib/logrotate tmpfs defaults,noatime,nosuid,nodev,noexec,size=1m,mode=0755 0 0 tmpfs /var/lib/sudo tmpfs defaults,noatime,nosuid,nodev,noexec,size=1m,mode=0700 0 0 # MTD EEPROM memory dev/mtdblock0 /mnt/mtd jffs2 ro,relatime 0 0 EOT However changes in /etc/fstab are overridden somewhere over the build process, and this is the resulting /etc/fstab: UUID=c8167755-b557-4288-9109-9108bc48dd94 / btrfs defaults,noatime,commit=600 0 1 UUID=27ac6cc6-eff3-4736-a7bd-5517e3b150c0 /boot ext4 defaults,commit=600,errors=remount-ro 0 2 tmpfs /tmp tmpfs defaults,nosuid 0 0 Is there a way to safely patch the /etc/fstab file? Thanks very much! Andrea

I noticed the BPI-M4 Zero is supported. It's the same SoC as the BPI-M4 Berry and mostly the same hardware (8GB eMMC, 2GB RAM). The main differences seem to be the ports. Is there a chance the image would work? Is the BPI-M4 Berry possibly going to get support?

Hi, I'm trying to build armbian with the tutorial https://docs.armbian.com/Developer-Guide_Build-Preparation/#what-do-i-need but I get this error: ~/git/others/armbian/build$ ./compile.sh [🚸] Docker is installed, but not usable [ can't use Docker; check your Docker config / groups / etc ] [💥] Problem detected [ Docker installed but not usable ] [💥] Exiting in 10 seconds [ Press <Ctrl-C> to abort, <Enter> to ignore and continue ] Counting down: 9... 8... 7... 6... 5... 4... 3... 2... 1... 0... [💥] error! [ Exiting due to 'Docker installed but not usable' ] [💥] Exiting with error 43 [ at /home/eloy/git/others/armbian/build/lib/functions/logging/traps.sh:1 exit_with_error() --> lib/functions/logging/traps.sh:1 exit_if_countdown_not_aborted() --> lib/functions/general/countdown.sh:41 cli_standard_relaunch_docker_or_sudo() --> lib/functions/cli/utils-cli.sh:261 cli_standard_build_pre_run() --> lib/functions/cli/cli-build.sh:14 armbian_cli_pre_run_command() --> lib/functions/cli/utils-cli.sh:122 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:79 main() --> ./compile.sh:50 ] I have virtualbox installed, and my OS is: cat /etc/os-release PRETTY_NAME="Ubuntu 22.04.4 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=jammy lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 43 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Vendor ID: AuthenticAMD Model name: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx What am I doing wrong? Thanks in advance.

Can I run a YOLOv8 model in RKNN format, developed for Rockchip 3588, on a Rockchip 3588S without any issues?

I have FriendlyElect CM3588 (RK3588 based) Nas kit which is lagging behind in terms of incorporating the latest NPU driver (the current is 0.9.3) in their firmwares. Thier repository contains Ubuntu / Debian with Kernels 6.1.x As far as I know the latest RKNPU version is 0.9.6. and as I understand there is no OS on Armian tailored for CM3588. What is best way to get the lastest driver?

Hello, thank you for your new image work. However, although I wrote to write your image to emmc or sd card, the device does not respond at all. The previous version Armbian_23.11.1_Panther-x2_bookworm_current_6.1.63.img.xz works normally on my panther device. The new version and minimal iot version do not boot at all. I kindly request your information about Armbian_community_24.11.0-trunk.25_Panther-x2_bookworm_current_6.6.47_minimal .img.xz.

While a friend of mine was developing my Rockchip rv 1126 device, we lost access as a result of a wrong operation. The device is powered on. the red light on the back is on, but we cannot access the device we have previously identified from the ip's. When I try the usb port on the device, I get a device not recognized warning in ubuntu 22.04 and windows10. Can anyone help me to reinstall the operating system or access the device? Thank you.

I found what a likely duplicate out-of-tree driver after investigating a warning from the kernel build: CC [M] drivers/gpu/drm/panel/panel-simple-dsi.o drivers/gpu/drm/panel/panel-simple-dsi.c: In function 'panel_simple_get_modes': drivers/gpu/drm/panel/panel-simple-dsi.c:310:73: warning: passing argument 3 of 'of_get_drm_display_mode' makes pointer from integer without a cast [-Wint-conversion] 310 | ret = of_get_drm_display_mode(panel->dev->of_node, mode, p->desc->bus_format, | ~~~~~~~^~~~~~~~of_get_drm_display_mode~~~~ | | | u32 {aka unsigned int} In file included from ./include/drm/drm_crtc.h:32, from drivers/gpu/drm/panel/panel-simple-dsi.c:13: ./include/drm/drm_modes.h:509:66: note: expected 'u32 *' {aka 'unsigned int *'} but argument is of type 'u32' {aka 'unsigned int'} 509 | struct drm_display_mode *dmode, u32 *bus_flags, | ~~~~~^~~~~~~~~ This code cannot work as is and a fix would be to add the missing ampersand before the p->desc->bus_format. Still other warning surface when this is fixed. This driver calls of_get_drm_display_mode against bus_format while panel-simple does against bus_flags (it also has bus_format but it passes it as an argument to drm_display_info_set_bus_formats). So it might well be that the driver would pass the wrong arguments. It has no documentation for its DTS parameters so it is hard to tell if bus_format should be set as bus_flags from the panel-simple documentation or if its user will end up sending bus_format as a bus_flags. There is already a dsi driver in upstream drivers/gpu/drm/panel/panel-simple.c (panel-dsi-simple while this one is panel-simple-dsi). So I wonder if there is a use in shipping two drivers for the same purpose. And there are no dts users of this out-of-tree driver panel-simple-dsi. The discussion about its introduction is in: https://github.com/armbian/build/pull/3140 It is told in the commit log to be a port of a rockchip kernel 4.4 driver, but panel-simple has dsi probe since v3.14. I am puzzled rockchip forked panel-simple instead of expanding it. Rockchip.DRM.Panel.Porting.Guide.pdf has no mention of the bus_format dts parameter so maybe this code path was never used and the buggy code affects no users. (a few dts parameters in the rockchip code are also not documented in this PDF). @iamdrq you are the author of this driver. Was there code missing in the dis support of panel-simple.c for dsi support, ie is panel-simple-dsi necessary? Was the aim to have a version of the panel dsi code that is bit-to-bit compatible with the rockchip kernel, so no porting was necessary? If features were missing could we bake them into the panel-simple.c driver (so they could be tested and one day be upstreamed)?

Is there any generic build of Armbian compatible with that processor?

Hi, I'm trying to use desktop community build for Windows dev kit 2023 but it is not working. Current image: Armbian_community_24.8.0-trunk.554_Wdk2023_noble_wdk2023_6.7.0-rc6_gnome_desktop.img.xz When using etcher to flash to usb, it will flash but fail at validation step say "Cannot validate, the image could be corrupt" or something like that. If still use that usb in WDK, it won't boot. The lite version Armbian_community_24.8.0-trunk.554_Wdk2023_bookworm_wdk2023_6.7.0-rc6_minimal.img.xz is still working fine.