RSS Bot

Description tiny housekeeping. update major_minor to match collabora tree View the full article

Description This reverts https://github.com/armbian/build/pull/5615 Need to split and fix. View the full article

Backport DTS/DTSI changes from linux-6.4.y to 6.1.y Add meson64-reboot driver to all boards Add board: ODROID N2L Add uart_A uart_AO_B uart_B uart_C where appropriate U-Boot v2023.07.02: ODROID N2/N2L/N2Plus/C4 Meson64-reboot driver: (source: tobetter) While the current meson64-reboot driver is cleaner and doesn't depend on modding other kernel sources, its functionality leaves much to be desired. One example can be found in the ODROID C4. Using the current driver, the board will not properly power off, leaving the POWER LED still on. The new driver powers off the unit completely. Fan control: (ODROID N2L/N2PLus) Added service and script for controlling the trip point. fanctrl: arguments: 65 55 45 35 25 menu run ┌──┤ Fan Control ├──┐ │ │ │ 6) 65°C │ │ 5) 55°C │ │ 4) 45°C │ │ 3) 35°C │ │ 2) 25°C │ │ E) Exit .. │ │ │ │ │ │ <Ok> │ │ │ └───────────────────┘ NOTES: (N2L/HC4): I do not own the units so I can't run tests. Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

khadas-vim4: add modprobe config to avoid kernel panic during ISP firmware loading khadas-vim4: add modprobe config to avoid kernel panic during ISP firmware loading See https://armbian.atlassian.net/browse/AR-1801?focusedCommentId=11995 View the full article

rockpro64: bump ATF to lts-2.8.8 rockpro64: bump ATF to lts-2.8.8 View the full article

Description irony of using bleeding edge uboot was to take advantage of the native rock 4SE support in uboot....which is broken. using generic rockpi-4i uboot defconfig for now.. which works.. leaving placeholder so that we can one day, embrace what is pure. View the full article

Description Ordered this WiFi key and it was not working out of the box. Adding pids (and also for Netgear variant) helps that it works OOB. Jira reference number AR-1803 How Has This Been Tested? [x] Build and booted USB wireless device (on Odroid N2 https://paste.armbian.com/onulekucil) Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Firmware update. Jira reference number AR-1700 How Has This Been Tested? [ ] Build test as HW is n/a Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description -- remember its not rockpi 4SE its rock 4SE now that RK3399-T friendly ddr blobs have been added, lets given this a discrete config..... and use mainline uboot with an official uboot defconfig. View the full article

odroidm1: de-infest Petitboot 🔥 use Kwiboo's 2023.10 u-boot; UMS works; bump kernel to 6.5-rcX odroidm1/edge (rk3568-odroid): bump to 6.4.y, update config, rebase patches to 6.4.10 odroidm1/edge (rk3568-odroid): bump to 6.5-rc6; manually fix RK808 breakage in .config; rebase patches add patch to remove Petitboot-mandated MTD partitions this way we have access to the full flash, and can write our own u-boot to it rebase all patches odroidm1/edge (rk3568-odroid): drop 6.3 and 6.4 patches odroidm1: de-infest Petitboot 🔥 use Kwiboo's 2023.10 u-boot; UMS works using Kwiboo's rk3568-2023.10 branch with BINMAN-handled blobs patches (defconfig unless indicated): boot usb first (rockchip-common) blink leds & keep red one one on preboot change usb_host0_xhci to otg (u-boot dtsi) enable DM_GADGET, UMS 🔥 and RockUSB usage instructions: build & burn image to SD card insert SD card into board hold the recovery (RCY) button and power on the board watch board boot de-infest Petitboot: use armbian-install to install bootloader to MTD if you don't, you'll need to hold the recovery button every boot optionally: use armbian-install to install OS to eMMC/NVMe/USB power-off board remove SD card (new u-boot always boots SD first!) boot into your newly de-infested machine boot order: USB, SD, MMC, NVME, SCSI de-infested machine can now boot (directly) from USB/SATA/NVMe: Armbian UEFI-arm64 Fedora 38 aarch64 Talos arm64 others... extra: new u-boot by Kwiboo (with GMAC patches) gives us stable MAC address although it is based on cpuid#, doesn't match the HK sticker on the board odroidm1: update DDR/BL31 blobs (this depends on https://github.com/armbian/rkbin/pull/20) View the full article

Description Enabled compilation options for the USB interface MT7921 chip driver module mt7921u. Need to work with the corresponding firmware https://github.com/armbian/firmware/pull/57 . How Has This Been Tested? [x] built and tested on nanopi-r4s The Wi-Fi is working well, Bluetooth was not tested. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description bump atf to LTS v2.8 for Rockchip64 How Has This Been Tested? Rockpro64 boots Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Update maintainers and board status synced status from the database rename to .csc where we don't have anyone If you want to become a board maintainer, adjust data here. Ref: Board Maintainers Procedures and Guidelines View the full article

Description I thought edge would carry the fixes forward, missed 6.4 folder. How Has This Been Tested? Carryover from 6.3 Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Debian moved riscv64 into 1st class so exceptions are not needed. But ports repository is still needed in the lists file as they didn't manage to move everything. Jira reference number AR-1824 How Has This Been Tested? [x] Generated image with clean rootfs Armbian_23.08.0-trunk_Star64_sid_edge_5.15.0.img Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

odroidm1: de-infest Petitboot 🔥 use Kwiboo's 2023.10-rc2+gmac u-boot odroidm1/edge (rk3568-odroid): bump to 6.4.y, update config, rebase patches to 6.4.10 odroidm1/edge (rk3568-odroid): bump to 6.5-rc6; manually fix RK808 breakage in .config; rebase patches add patch to remove Petitboot-mandated MTD partitions this way we have access to the full flash, and can write our own u-boot to it rebase all patches odroidm1/edge (rk3568-odroid): drop 6.3 and 6.4 patches odroidm1: de-infest Petitboot 🔥 use Kwiboo's 2023.10-rc2+gmac u-boot using Kwiboo's rk3568-2023.10-gmac branch with BINMAN-handled blobs patches: boot usb first preboot pci/usb enum/scan usage instructions: build & burn image to SD card insert SD card into board hold the recovery (RCY) button and power on the board watch board boot de-infest Petitboot: use armbian-install to install bootloader to MTD if you don't, you'll need to hold the recovery button every boot optionally: use armbian-install to install OS to eMMC/NVMe/USB power-off board remove SD card (new u-boot always boots SD first!) boot into your newly de-infested machine boot order: USB, SD, MMC, NVME, SCSI (SATA) de-infested machine can now boot (directly) from USB/SATA/NVMe: Armbian UEFI-arm64 Fedora 38 aarch64 Talos arm64 others... extra: new u-boot by Kwiboo (with GMAC patches) gives us stable MAC address although it is based on cpuid#, doesn't match the HK sticker on the board odroidm1: update DDR/BL31 blobs; cleanup old Petitboot stuff this depends on https://github.com/armbian/rkbin/pull/20 View the full article

Description The command takes long time to continue and it makes it seem like the build halted, so this adds an alert to mitigate this --> (3) COMMAND: fakeroot dpkg-deb -b -Znone /armbian/.tmp/work-cfd2d6ad-1f9b-473e-80e7-cbcf9d157c68/uboot-Bd1Ms /armbian/output/packages-hashed/gl> dpkg-deb: building package 'linux-u-boot-sipeed-lichee-pi-4a-current' in '/armbian/output/packages-hashed/global/linux-u-boot-sipeed-lichee-pi-4> --> (372) INFO: Built u-boot deb OK [ linux-u-boot-sipeed-lichee-pi-4a-current 2022.07-Se092-P0000-H6f49-V9cb9-B9963-R448a ] Jira reference number [AR-9999] How Has This Been Tested? Builds on my end Checklist: [X] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [X] I have commented my code, particularly in hard-to-understand areas [X] I have made corresponding changes to the documentation [X] My changes generate no new warnings [X] Any dependent changes have been merged and published in downstream modules View the full article

See rationale on https://www.shellcheck.net/wiki/SC2086 Description Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. Jira reference number [AR-9999] How Has This Been Tested? Blind edit Checklist: [X] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [X] I have commented my code, particularly in hard-to-understand areas [X] I have made corresponding changes to the documentation [X] My changes generate no new warnings [X] Any dependent changes have been merged and published in downstream modules View the full article

Got the board too and doing OSHW development for the platform View the full article

Description Enabling CPU idle can lower CPU power at low load. How Has This Been Tested? [x] Bootup test [x] Stress test Checklist: [ ] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Prior to this patch, adding a user-overlay using the script will add the filename with a space after the user-overlays=, even if there aren't any overlays present. This will result in the following: before adding: user_overlays= after adding: user_overlays= rk3588-i2c0-m1.dts with a space. This patch will add another else branch to handle this, as well as handling any additional spaces present prior. New script does this before adding: user_overlays= or user_overlays= after adding: user_overlays=rk3588-i2c0-m1.dts Adding more overlays works as intended, with a space and the name.dtbo How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Copied conditional branch part of the code, modified changes and ran all the possible situations, worked as intended. [x] Modified the script the same way on my Rock5B with Armbian Bookworm 23.5.1 install and tried adding multiple overlays, worked as intended. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas Not strictly required [x] I have made corresponding changes to the documentation Not required [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules Not required View the full article

meson-g12-bananapi-rtl8822cs.dtbo (M2S / M5) meson-sm1-odroid-c4-rtl8822cs.dtbo (ODROID C4) Add support for the RTL8822CS expansion board. https://wiki.banana-pi.org/Banana_Pi_BPI-M5#Wifi_.26_BT_support_via_expansion_board The overlays were tested on the BananaPi M2S and ODROID C4. Although not intended to be used on the C4, it works without issue. NOTE: Whilst further testing, I found bluetooth doesn't come back upon reboot when using Armbian on the C4. Not really a game changer, but it needs to be resolved in the future. Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

extensions: image-output-oowow: creates Khadas oowow compatible images extensions: image-output-oowow: creates Khadas oowow compatible images requires KHADAS_OOWOW_BOARD_ID set in board file (see next commit) always produces xz-compressed images, so this automatically disables COMPRESS_OUTPUTIMAGE uses xze script from Khadas, forcing IN and OUT env vars so it's not confused by fd 1 to use, add EXT=image-output-oowow parameter to build to get into oowow: VIM3/VIM3L: download oowow SD card image from Khadas: VIM3: https://dl.khadas.com/products/oowow/system/vim3-oowow-latest-sd.img.gz VIM3L: https://dl.khadas.com/products/oowow/system/vim3l-oowow-latest-sd.img.gz write image to SD card, use BalenaEtcher or similar insert SD card into board (and remove NVMe if present and bootable) boot board into Upgrade mode, see https://docs.khadas.com/products/sbc/vim3/install-os/boot-into-upgrade-mode oowow should be running now recommended: go into Advanced and reset to factory defaults, so MCU, PCIe/USB3 etc is reset to defaults VIM4/VIM4N/VIM1S/Edge2: those have oowow in SPI from factory, check out the manual there's a few ways to use these images with oowow: Using External media prepare media (USB), format it with ext4 or fat, copy produced oowow.img.xz to it for ease of use, rename the image file, so it begins with the board-id (vim1s-/vim4-/edge2- etc) boot board into oowow (see oowow's manual) insert media into board exit wizard, use "Write image to eMMC", browse to "../" change from "XXXX only" to "All" if you didn't rename the image choose image file and write (remove SD card if using one) and reboot Via network (Ethernet or Wi-Fi) boot board into oowow plug in Ethernet cable or connect to Wi-Fi (see oowow's manual) set the firewall mode to "allow" in oowow's Network Settings (see oowow's manual) obtain the IP address of the board in oowow (usually shown on top of the screen, or see manual) from a remote machine, use curl to upload and write the image to oowow's eMMC, example: curl -L <ip_address>/shell/write | sh -s - <image_filename>.oowow.img.xz reboot board From the Internet (one day) when Khadas publishes Armbian oowow images to their HTTP server khadas boards: VIM1S/3/3L/4/Edge2: add KHADAS_OOWOW_BOARD_ID definition for use with oowow (EXT=image-output-oowow) View the full article

Description rkr5.1 is already synced with rkr4. Tested on rock5b. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Rock5b kernel build success [x] Kernel works on rock5b Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description licheepi-4a: add a .wip for Sipeed LicheePi 4A board The u-boot of LicheePi 4A can be updated without the need to flash the system. Users can manually update it according to the instructions provided by Sipeed's wiki when needed. The opensbi used in LicheePi 4A is not packaged within u-boot using a fit image. Therefore, it is stored in the repository as a binary file. During startup, LicheePi 4A requires loading audio and aon firmware. These two files will also be stored in the repository in binary format. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Successfully built. [x] System startup. Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article