SBC News

Description Typo View the full article

Description CSC target, not tested on hardware View the full article

u-boot-menu: allow avoid using uInitrd, for when the bootloader requires modern initrd.img u-boot-menu: allow avoid using uInitrd, for when the bootloader requires modern initrd.img View the full article

u-boot-menu: curb logging, no need to emit warn's here u-boot-menu: curb logging, no need to emit warn's here View the full article

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 …

u-boot-radxa-rk3588/legacy: use 000.patching_config; fix boot from SD when combined with from-factory eMMC blobs (TEE mismatch) u-boot-radxa-rk3588/legacy: rewrite u-boot patches, no changes u-boot-radxa-rk3588/legacy: add 0000.patching_config.yaml and move all null-patches into dt and defconfig dirs as bare files DTs and defconfigs should be identical to their null-patch equivalents u-boot-radxa-rk3588/legacy: rewrite nanopc_t6_defconfig -- no changes CONFIG_REGULATOR_RK806=y seems a leftover that's not really used? u-boot-radxa-rk3588/legacy: rewrite nanopc_cm3588_defconfig -- no changes CONFIG_REGULATOR_RK806=y seems a leftover that's not really used? u-boot-…

Description Fix boot from btrfs fs in uboot 2024.07 (backport patch from uboot.next https://github.com/u-boot/u-boot/commit/ee1941e4fec601a8444f49c7dad04ad700d501a6) 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] Compile image and boot from (zstd-compressed) btrfs sole rootfs/bootfs partition Checklist: [x] I have performed a self-review of my own code View the full article

u-boot: add HOME env for make invocations to avoid binman/Python problems with older u-boot versions tinkerboard: rewrite u-boot patches, no changes xt-q8l-v10: rewrite u-boot patches, no changes u-boot: add HOME env for make invocations to avoid binman/Python problems with older u-boot versions this avoids trouble building certain older versions with binman as it tries to os.path.join(os.getenv('HOME'), 'bin') and gets a None and dies naming names: tinkerboard & xt-q8l-v10 (BOARDFAMILY=rockchip), which actually use binman & 22.04 combo View the full article

Description These patches went missing sometime during development cycle of this release. Looks like they are needed for emmc support on nanopi neo core 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] Checked that u-boot builds and patches gets applied correctly 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 depe…

u-boot: call olddefconfig after config hooks; use pipetty instead of unbuffer for make u-boot: call olddefconfig after config hooks; use pipetty instead of unbuffer for make also: cli uboot-config produces a defconfig diff (useful to create post_config_uboot_target) View the full article

u-boot: embed armbian artifact version in CONFIG_LOCALVERSION u-boot: embed armbian artifact version in CONFIG_LOCALVERSION we're hacking at it anyway, so why not use it to uniquely identify the exact build 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

u-boot: rewrite/rebase u-boot patches for a few boards; bump odroidm1 and orangepi3b u-boot: rewrite/rebase u-boot patches for a few boards; drop long-forgotten old version patches; no actual changes I guess this is most of the u-boot's I've touched over the years; notable exception is the orangepi3b (patches live in Kwiboo's tree) this is in preparation for bumping versions, hopefully soon radxa-zero, radxa-zero2, khadas-vim3, khadas-vim3l: drop patches for old u-boot versions no longer used odroidm1: bump u-boot to v2024.04-rc3 odroidm1: copy patches from v2023.10 odroidm1: rebase u-boot patches against v2024.04-rc3 odroidm1: drop v2023.10 u-boot patches orangepi…

Description Bumped u-boot for allwinner to 2023.10 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] All patches gets applied [X] U-boot build for all of the allwinner boards 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

u-boot: use pipetty in place of unbuffer u-boot: use pipetty in place of unbuffer unbuffer never solved anything; pipetty might View the full article

Move the BPI-M2PRO off the BPI-M5 U-Boot. The BananaPi M5 supports the RTL8822CS Mezzanine, so let us provide the proper bluetooth firmware. NOTE: Boot needs verifying. 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

uboot: allow adding/changing uboot CFLAGS with post_config_uboot_target() hook uboot: allow adding/changing uboot CFLAGS with post_config_uboot_target() hook View the full article

Description Current armbian images can't boot from sd card, and rockchip has provided uboot patches to fix it. 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] ./compile.sh BOARD=armsom-sige5 BRANCH=vendor BUILD_MINIMAL=no DEB_COMPRESS=xz KERNEL_CONFIGURE=no RELEASE=noble KERNEL_GIT=shallow BUILD_DESKTOP=yes DESKTOP_APPGROUPS_SELECTED= DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base [x] Tested sd card boot with armsom sige5 Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project …

Description Fixes compilation issue introduced by u-boot bump. Not sure why this was not caught in the test as I ran building of all allwinner u-boots in a loop. Anyways, now these are getting built correctly 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 u-boot builds for orangepizero2 [X] Tested u-boot builds for Bigtreetech cb1 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 cha…

ubuntu: add mantic (23.10), symlinks to lunar ubuntu: add mantic (23.10), symlinks to lunar ubuntu: desktop gnome: drop package gconf2 this had already been done for Debian variants View the full article

uefi edge 6.6: bump to 6.6-rc6; rebase patches uefi edge 6.6: bump to 6.6-rc6; rebase patches also bump qemu-uboot variant's uboot from 23.10-rc4 to final 23.10 View the full article

Description Maint. How Has This Been Tested? [ ] Compile at CI Checklist: [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Maint. How Has This Been Tested? [ ] CI Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

uefi-(arm64|x86)-edge/5.19: bump to 5.19.y uefi-arm64-edge/5.19: add patch for ACPI enablement of PHYT0004 onboard network card reworked 5.10 version of patch to 5.19, trivial datatype change sent by Dragonbox/Pythium person via @lanefu uefi-(arm64|x86)-edge/5.19: split patch dir from x86, otherwise identical Description This was mostly done and tested together with https://github.com/armbian/build/pull/3941 in terms of builds and tests. View the full article

As of 2024 Feb, Github still no allow a source branch to be renamed. Previous PR https://github.com/armbian/build/pull/6291 was auto closed by Github upon source branch renaming. This new PR supersedes it. Description Running "uefi-x86" board image on qemu-system-x86_64 --display none --serial stdio ... did not: allow GRUB boot without GUI display display early kernel boot messages on the serial console display the console prompt on serial console Jira reference number: None 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] Test A: Boot uefi-x86 board imag…

uefi: rollover current to legacy, edge to current, bump edge to 6.7, fix drivers, remove symlinks uefi: common: stop using symlinks, instead point directly to KERNEL_MAJOR_MINOR uefi: common: drop kernel symlinks remove duplicate decls simplify some comments thinkpad-x13s: set explicit LINUXCONFIG to compensate for changes in uefi-common uefi: all: update all .config's, no changes; edge: 6.6.y; current 6.1.y; legacy 5.15.y uefi: all: rollover current 6.1.y to legacy, taking over 5.15.y uefi: all: rollover edge 6.6.y to current, taking over 6.1.y uefi-arm64 6.7: copy patches from 6.6 uefi: all: edge: bump to 6.7-rc7; arm64: fix Phytium stmmac patch (by Igor) Co-authore…

Description Maint. How Has This Been Tested? [x] Patches applies well View the full article

Currently adopted 5.20-1 Reboot board. Change from regulator-boot-on to regulator-always-on. reg_dcdce: dcdce { regulator-always-on; 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? 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 c…

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…

https://armbian.atlassian.net/browse/AR-1001 added function to unmount and format MTD flash added menu entry for said function. added form mtd Jira reference number AR-1001 How Has This Been Tested? added nandsim and virtulied the MTD. https://gist.github.com/Tearran/e704f04a6fbc457a56dc5f5f87f8899d created a virtual MTD mounted /temp/boot created a file to erace Unmounted then remounted to confirm file still exist ran mtd-tools format confirmed no data remained created function and ran with same results 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 …

Original version destroyed journal on command postrotate as files in /var/log.hdd/journal are overwritten by cat. With the patch journal is not damaged anymore. Description In original version in postrotate files in /var/log.hdd/journal are deleted by the command dest="/var/log/$file" cat $file > $dest as /var/log/journal is a symling to /var/log.hdd/journal files are cated on themselves which ends up with an empty file. How Has This Been Tested? check journal by journactl. There is no data earlier than today 0:00. Also "journalctl --verify" shows that journal is damaged. Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a s…

Description Recently a patch solved the problem with /var/log.hdd/journal increasing in size. However, the patch also deletes all files created by logrotate. This makes logrotate useless. This patch can at the same time decrease the size of the journal folder and keeps files created by logrotate. see discussion at https://forum.armbian.com/topic/19995-armbian-ramlog-problems-and-possible-improvements/ How Has This Been Tested? I am using the changed file on my system. No problems so far. 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…

Description Previous help message armbianmonitor -h Usage: armbianmonitor [-h] [-b] [-c $path] [-d $device] [-D] [-m] [-p] [-r] [-u] ############################################################################ Use armbianmonitor for the following tasks: armbianmonitor -c /path/to/test performs disk health/performance tests armbianmonitor -d monitors writes to $device armbianmonitor -D tries to upload debug disk info to improve armbianmonitor armbianmonitor -m provides simple CLI monitoring - scrolling output armbianmonitor -M provides simple CLI monitoring - fixed-line output armbianmonitor -n provides simple CLI network monitoring - scrolling output armbianmon…

Description Le potato mainline vendor asound.state to fix analog out issues View the full article

Description Added PPA source for Noble, added Bluetooth service, required fixed Bluetooth MAC to use Bluetooth function, added automatic generation of random MAC function (to be tested), fixed some udev file content issues Jira reference number [AR-9999] 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] Bluetooth [ ] Auto gen random bt Mac 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 cha…

Description These two blob files have been in repo armbian/rkbin for a long time: armbian/rkbin#8. I test them on rock-3a today. Should be okay to update. 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 on rock-3a 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 publish…

since armbian 24.8.0-trunk.205 this board stop working find a fix on station-p2 for it forum thread How Has This Been Tested? H96-MAX-RK3566 V56 4GB 32GB internal MMC Checklist: Please delete options that are not relevant. [ 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 Move broken CSC target to EOS. Jira reference number AR-1272 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 Since we are making a list of all boards, some stands out for wrong naming. Cosmetic adjustment. How Has This Been Tested? No need. 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 Current u-boot is a bit unstable, so this bump can't hurt. How Has This Been Tested? [x] Generated image, survived several reboots. Checklist: [x] My changes generate no new warnings View the full article

-Clean, remove params for old kernel -Add option to disable usb autosuspend -Add display console replace rootdev with "LABEL=armbi_root" to boot from sd card an emmc with same boot.ini View the full article

Description 'setenv console "display"' in boot-sunxi.cmd & in armbianEnv.txt had the same effect as 'setenv console "both"'. That was due to a false if-statement in boot-sunxi.cmd:41 Fixed that, so 'setenv console "display"' will not co-enable the serial console anymore. No dependencies required. Jira reference number: [n/a] How Has This Been Tested? Test A: Executed mkimage on BananaPi. Yielded results as expected. [x] Test A Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [n/a] I have commented my code, particularly in hard-to-understand areas [n/a] I have made corresponding changes to the d…

Description Add @adeepn to meson64-related stuff Jira reference number AR-1766 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 Reported by mboehmer on the forums Kernel update made direct spidev in dts an error rather than warning, this patch didn't get updated post-break. Use "armbian,spi-dev" compatible defined in another patch. How Has This Been Tested? Builds OK 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 New blobs has been pushed to rk bin repository. https://github.com/armbian/rkbin/pull/25 Probably support for new memory chips. Jira reference number AR-2077 How Has This Been Tested? [x] Boot on Orange Pi 5 v1.2 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 New Docker generating script is based on @rpardini for Armbian NEXT with one exception - hard coded values has been replaced with automated generation from our build config. We will be making Docker images for all images except AR-1495 old releases such as Focal / Buster which are currently still tagged as supported. To do: [ ] Switch from armbian-next to master [ ] Resolve AR-1495 Script: https://github.com/armbian/scripts/pull/38/files Test run: https://github.com/armbian/build/actions/runs/3938745257 Jira reference number AR-1449 How Has This Been Tested? [x] Manual run, images are deployed Checklist: [x] My code follows the style guidelines of thi…

Description Update to the latest v6.4 kernel when using "edge" on K3 family devices How Has This Been Tested? [x] Tested on SK-TDA4VM, SK-AM62B, and SK-AM64B boards 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 Changing export-logs.sh script from posting to armbian.next.armbian.com to posting to the primary paste server which has now been upgraded at paste.armbian.com. Jira reference number INFRA-13 How Has This Been Tested? [x] Manual run Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code View the full article

Description Update JetHome JetHub D2 support: add patchset for u-boot update kernel patches Update #6725 Jira reference number AR-2028 View the full article

Description Update JetHub D1 (j100) u-boot patchset to buildable state. Jira reference number AR-1310 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] fixes jethub_j100 build [X] no other changes View the full article

Description Some network related dependency were missing as DNS within docker container was not working. While dealing with config, several other options were enabled, which should be harmless. Jira reference number AR-2086 How Has This Been Tested? [x] Generated Debian Bookworm with HA extension which loads automatically 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 We were still using 6.0 ... just enabling what is sane. How Has This Been Tested? [x] Tested on Bpi M5. 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 Lets wait for upstream to be updated for 6.3, 6.4 and up. How Has This Been Tested? [x] Build test Checklist: [x] My changes generate no new warnings View the full article

Description I want to rebuild Bpi M5 with current kernel (now they are EDGE only). Jira reference number [AR-9999] How Has This Been Tested? [x] Boot Odroid N2+ image 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 Rework of https://github.com/armbian/build/pull/5563 with use of ./compile.sh BOARD=x BRANCH=y kernel-config How Has This Been Tested? [x] Build test with CI Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Test build from here: https://github.com/amazingfate/armbian-rock5b-images/releases/tag/20230524-0807 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] Image build sucessfully [x] Image running fine 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…

Description Winter, Spring, Summer, Autumn. This can only apply in northern hemisphere countries. Southern hemisphere is the opposite months. First quarter, second quarter, third quarter, fourth quarter are universal options. Jira reference number AR-1933 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 docu…

Description Radxa has changed to use branch linux-5.10-gen-rkr3.4 for rock5b: https://github.com/radxa/kernel/tree/linux-5.10-gen-rkr3.4. So we just use new branch and remove obsolete patches. 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] Build kernel for rock5b successfully. [x] Kernel works for 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 …

Description add PSI, ashmem, binder, binderfs to kernel config on meson64 to make Waydroid work on Amlogic S9xx. I just cherry-picked and copy/pasted changes from here: https://github.com/armbian/build/pull/4806 How Has This Been Tested? I build a ubuntu 22.04 image with Gnome, installed Waydroid, it works. View the full article

Enable bcachefs filesystem support in rk3588 kernel config (copied from armbian rockpro64 edge config). Description This adds support for the bcachefs filesystem in the rk3588 edge kernel config. Bcachefs is a new and exciting filesystem that is similar to btrfs / zfs, but simpler to use. The relevant kernel options were already in other configs, such as the rockpro64 edge config, but not in the rk3588 edge one. This needs kernel version 6.7+. How Has This Been Tested? custom kernel build Checklist: Please delete options that are not relevant. [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have comment…

No descriptionView the full article

Description Update meson64 edge kernel branch to linux-6.2.y Jira reference number AR-1551 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 Bump the K2 to u-boot 2024.01, let's try to get old u-boots out of our hair. How Has This Been Tested? builds and boots, everything works. 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 WAN ethernet does not work on NanoPI R2C on edge because GMAC_CLK pin on PHY not provides output clock (for GMAC) by default. This updated device tree fix this issue. current and legacy branches have different (out of kernel) driver and don't need this dts fix. [ 2.902617] rk_gmac-dwmac ff540000.ethernet: IRQ eth_wake_irq not found [ 2.902640] rk_gmac-dwmac ff540000.ethernet: IRQ eth_lpi not found [ 2.902793] rk_gmac-dwmac ff540000.ethernet: PTP uses main clock [ 2.903026] rk_gmac-dwmac ff540000.ethernet: clock input or output? (input). <- this clock MUST be provided by PHY [ 2.903049] rk_gmac-dwmac ff540000.ethernet: TX delay(0x22). [ 2.…

Description Added PPA source for Noble, added Bluetooth service, required fixed Bluetooth MAC to use Bluetooth function, added automatic generation of random MAC function (to be tested), fixed some udev file content issues Jira reference number [AR-9999] 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] Bluetooth [x] Auto gen random bt Mac 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 cha…

Description Update the kernel to use the preset configurations so that you don't need an external keyboard to access the desktop Jira reference number [AR-9999] 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] Flash and directly boot to the desktop Checklist: Please delete options that are not relevant. [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 mer…

Description Update odroidxu4-current kernel to 5.4.251. I am not sure if the patches fixing the wireless drivers are the correct way of handling this, please feel free to ignore this PR if they are not. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 5.4.204. How Has This Been Tested? [x] Cold reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 5.4.208. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 5.4.210. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 5.4.212. Hardkernel's upstream seems fixed so let's switch back to the branch. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 5.4.215. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 5.4.220. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 5.4.223. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 5.4.225. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 5.4.229. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 5.4.230. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 5.4.232. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 5.4.233. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 5.4.239. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 5.4.241 How Has This Been Tested? [x] Reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 5.4.242 How Has This Been Tested? [x] Reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 5.4.245 How Has This Been Tested? [x] Reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 5.4.246 How Has This Been Tested? [x] Reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 5.4.252. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 5.4.253. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 5.4.255. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 5.4.256. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 Update odroidxu4-current kernel to 6.1.60. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Update odroidxu4-current kernel to 6.1.63. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Update odroidxu4-current kernel to 6.1.65. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Update odroidxu4-current kernel to 6.1.67. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Update odroidxu4-current kernel to 6.1.75. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Update odroidxu4-current kernel to 6.1.76. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Update odroidxu4-current kernel to 6.1.76. How Has This Been Tested? not yet, just committing current work. 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 [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Update odroidxu4-current kernel to 6.1.80. How Has This Been Tested? Reboot of my Odroid HC1. 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 [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Update odroidxu4-current kernel to 6.1.83. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Update odroidxu4-current kernel to 6.6.31. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Update odroidxu4-current kernel to 6.6.36. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description Update odroidxu4-current kernel to 6.6.41. How Has This Been Tested? [x] Reboot of my Odroid HC1 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 [ ] Any dependent changes have been merged and published in downstream modules View the full article