RSS Bot

Description Now NVME has the highest boot priority in uboot. But I think SD card should have higher boot priority than NVME SSD because SD card is much easier to plug in/out than NVME SSD. This patch is from https://github.com/radxa/u-boot/pull/25. We can add it to armbian whe it's not merged upstream. 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] uboot build successfully [x] Armbian on SD card boots when NVME SSD is installed. 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 NanoPC-T6 dts had a missing pinctrl which meant a conflicting default with I2C. Fixed, and add collabora kernel as target. How Has This Been Tested? Collabora kernel builds, boots, Edge kernel builds (does not boot for any board as far as I know) 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 Added "collabora" to the interactive config kernel branch selection (new branch for rk3588) 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] Interactive configuration started 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 Bumped u-boot and kernel version for Allwinner. Toggled CONFIG_MEDIA_SUPPORT from y to m in linux-sunxi-current.config similar to edge kernel to resolve the boot issue on 32-bit boards. U-boot 2023.07-rc4 -> 2023.07-rc6 (2023.07 is delayed by a week. Will bump it again once thats released) Kernel Legacy 5.15.113 -> 5.15.119 Kernel Current 6.1.34 -> 6.1.37 Kernel Edge 6.4.0 -> 6.4.1 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] Booted on NanoPi Duo2 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

partitioning: move hook call image_specific_armbian_env_ready() after the end of related manipulations partitioning: move hook call image_specific_armbian_env_ready() after the end of related manipulations depending on rootpart/extlinux/boot.ini it might not have run or had any effect View the full article

mekotronics: post_family_config() hook is too late to change DDR_BLOB and BL31_BLOB, move to board-scope variables mekotronics: post_family_config() hook is too late to change DDR_BLOB and BL31_BLOB, move to board-scope variables thanks @efectn for spotting this; I had tested the blobs in other ways, before deciding to refactor their change into a hook, which never worked. View the full article

Description Update ddr and bl31 blobs for opi5 and nanopi r6s Jira reference number [AR-9999] How Has This Been Tested? [x] Built and booted R6S fine [x] Orange Pi 5 was already working fine with https://github.com/armbian/build/commit/084fba8524937298a05fea55076ced540924cd22 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 Does following cleanup for series.* files from patch/kernel/archive/sunxi-*/ Disabled Revert-net-Remove-net-ipx.h-and-uapi-linux-ipx.h-header-files.patch as its also applied from patch/misc For 6.2+, series.armbian file also had list of patches from patches.fixes directory. As we have series.fixes file for that, removed the same from series. armbian Some patches were disabled in series.conf file, but were not disabled in the corresponding series.* files. Synced the same so that concatenating series.megous, series.fixes and series.armbian file produces matching series.conf file. These are just cosmetic fixes/cleanup, doesn't change anything on code level or functionality wise 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. [ ] Test A [ ] Test B 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 When crust is enabled on H3 and H5 boards, when booting, the following error is displayed during u-boot spl stage. ns16550_serial serial@1c28000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 The error is quite benign and doesn't impact functionality in any way. Still for user experience sake, this PR fixes the same. 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] Booted on Nanopiduo2 and verified that error is no longer produced 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 The BOOTPATCHDIR and KERNELPATCHDIR variables can contain multiple directories names separated by spaces as explained in lib/functions/compilation/uboot-patching.sh and lib/functions/compilation/kernel-patching.sh respectively but when calculating hash we were treating it as a single directory name. Also as ATF and crust gets bundled in u-boot, the hash of their patches must also be considered to determine if we need to rebuild u-boot 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] Tested by adding removing patches in patch/u-boot/u-boot-sunxi, patch/u-boot/u-boot-sunxi-crust and patch/crust directories and then compiling u-boot for nanopiduo2. U-boot recompiles as expected, which is not the current behavior. 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

Reduce failed to get tx report from firmware dmesg spam. https://lore.kernel.org/linux-wireless/20210713104524.47101-1-pkshih@realtek.com/ https://cgit.freebsd.org/src/commit/?id=e140d551b78670fbf99c83a59438cb13de50420f 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

python2/python3: symlink python3 as python/python2 if python2 is not found in host python2/python3: symlink python3 as python/python2 if python2 is not found in host this might allow some u-boots to build on bookworm/sid/etc (python2-less build hosts) View the full article

docker: default COLUMNS env var to 160 if unset / not-interactive docker: default COLUMNS env var to 160 if unset / not-interactive View the full article

rockchip64_common: default, but do not overwrite, BL31_BLOB and MINILOADER_BLOB rockchip64_common: default, but do not overwrite, BL31_BLOB and MINILOADER_BLOB rockchip64_common: move the TB2's special DDR_BLOB out from family file into board file View the full article

boot-rk3588-legacy bootscript: add a lot of debugs boot-rk3588-legacy bootscript: add a lot of debugs rk's 3588 vendor u-boot (and Radxa's, etc) have trouble with our usage of load+import, add echo's to debug what breaks View the full article

linux-rk35xx-legacy.config: update .config, no changes (.110 -> .160) linux-rk35xx-legacy.config: update .config, no changes (.110 -> .160) View the full article

mekotronics: refactor vendor conf/hooks; vendor uboot with new patches; new blobs mekotronics: refactor vendor conf/hooks; vendor uboot with new patches; new blobs meko: don't use Radxa's Rock-5A u-boot anymore, switch to rockchip vendor next-dev branch meko: my own (horrible) patches for MAC address stability / defconfig meko: cherry picked a few patches for getting rid of BL32/read Bl31 from env and other fixes from Radxa meko: add OTP node to 3588 dtsi (so we don't need kern-dtb in ITS for working OTP) meko: refactor common code across 3 (soon to be 4) board files into vendor conf and hooks meko: bump DDR/BL31 blobs for all Meko boards View the full article

rock-5-cmio: add a .wip for Radxa CM5 with I/O board rock-5-cmio: add a .wip for Radxa CM5 with I/O board use OPi5's uboot, don't ask me. View the full article

rkbin-tools: allow using custom rkbin RKBIN_GIT_BRANCH as well as RKBIN_GIT_URL rkbin-tools: allow using custom rkbin RKBIN_GIT_BRANCH as well as RKBIN_GIT_URL notice: the rkbin repo or the bins themselves are not hashed or included in the u-boot version (yet) make sure to avoid caching when building with those custom git/branch (ARTIFACT_IGNORE_CACHE=yes CLEAN_LEVEL=make-uboot) View the full article

u-boot: log what the BOOTCONFIG is when building u-boot: log what the BOOTCONFIG is when building View the full article

rkdevflash: don't wait for "Loader" mode after sending spl_loader; show the loop counter rkdevflash: don't wait for "Loader" mode after sending spl_loader; show the loop counter I thought sending the spl_loader blob puts it into "Loader" mode, but... ... turns out "Loader" mode is a separate (rockusb, etc) mode. So if in Maskrom mode, just send the loader, and trust it can now WriteLba still keeps the timeout, for when a loader is not accepted View the full article

rockchip-rk3588 collabora: new branch (by @lanefu) rockchip-rk3588 collabora: new branch (by @lanefu) bsdextrautils for kernel 6.4 (only if collabora branch) kernel 6.4 major, but skip rtw88 driver patching View the full article

Description Bumps edge kernel to v6.4. Megous patches are synced from orange-pi-6.4-20230619-0323 tag. Following heuristic was used to disable some of the Megous patches patch was already disabled for previous kernel patch also had a revert patch patch had rockchip, rk3xxx or pinephone-pro in name Following armbian patches were modified a bit to fix patch application failures drv-iio-adc-axp20x_adc-arm64-dts-axp803-hwmon-enable-thermal.patch drv-pmic-add-axp313a.patch drv-rgb-add-ws2812.patch drv-rtc-sun6i-support-RTCs-without-external-LOSCs.patch drv-touchscreen-tsc2007-polling.patch Following armbian patches were modified to fix compilation issues Add-dump_reg-and-sunxi-sysinfo-drivers.patch Add-sunxi-addr-driver-Used-to-fix-uwe5622-bluetooth-MAC-address.patch Toggled CONFIG_MEDIA_SUPPORT from y to m in linux-sunxi-edge.config as a ridiculous workaround to fix booting on 32-bit devices otherwise it gets stuck on Starting Kernel similar to early 6.1.20 kernel builds. 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] Booted 32-bit kernel on Nanopiduo2 [X] Tested that 64-bit kernel compiles successfully 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 bump rockchip-rk3588-edge to 6.4 add preliminary device tree for nanopc-t6 (not yet working) adopt new dts/overlay structure for rockchip-rk3588-edge 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. builds, no boards have booted with edge kernel here so far 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 Add missing bluetooth service like meko and khadas edge 2 Jira reference number [AR-9999] How Has This Been Tested? [x] Got a feedback from the forum 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