RSS Bot

Description Couple small fixes I found when starting to add support for TI SK boards. Wanted to test the waters with these patches before working to add board support. How Has This Been Tested? Built a couple platforms without issue due to this change. 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 linux-rk3399-legacy.conf is unused. Remove it. How Has This Been Tested? No references to file found in build system, only to linux-rockchip64-legacy.conf, which is for the same kernel. 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

https://github.com/armbian/build/blob/main/patch/kernel/archive/rockchip-6.3/01-linux-0002-rockchip-from-list.patch#L248-L291 this looks like better alternative for this patch. and this patch has build issue when build mmc and dw_mmc-rockchip as module, no export symbol for mmc_power_off I should use bug report to create an issue to discuss, but I can't open docs.google.com. 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 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

rockchip64 edge 6.3: move to bare DTs and overlays + fixes rockchip64 edge 6.3: drop add-boards-to-dts-makefile.patch rockchip64 edge 6.3: add 0000.patching_config.yaml for rockchip64 rockchip64 edge 6.3: rebase v6.3.6 + drop DT Makefile patches rockchip64 edge 6.3: drop overlay patches in favor of bare overlays in specific folder rockchip64 edge 6.3: replace DT-symlink patches with bare .dts with #include rockchip64 edge 6.3: drop null-patched DTS files, add them bare in dt/ folder remove double/triple-patching of nanopi-m4v2 (everything is in the bare .dts now) rockchip64 edge 6.3: drop need_checking and disabled patches let git have the history rockchip64 edge 6.3: rename most remaining "add-board" patches to "board" (all "add-board"s are now bare .dts in dt/ folder) keep helios64 as a reminder that it was overwritten once and probably should be dropped, together with other helios64 patches This depends and requires https://github.com/armbian/build/pull/5308 View the full article

meson64 edge: bump 6.2 to 6.4 + reworks + use bare DT's and overlays meson64 edge 6.2: rebase v6.2.16, drop Makefile patches, archeology, mbox'ing drop empty doc patch add-board-bananapi-cm4-cm4io.patch meson64 edge 6.2: update .config with no changes meson64 edge 6.4: initial copy (as-is) of 6.2 patches meson64 edge: bump from 6.2 to 6.4 (family file + symlink) meson64 edge 6.4: add 0000.patching_config.yaml for meson64 meson64 edge 6.4: drop patches that landed upstream and backports meson64 edge 6.4: rebase to 6.4-rc5; 7 are failing to apply meson64 edge 6.4: drop patches for boards that landed; change BPICM4 from add to board with pyavitz's fixes meson64 edge 6.4: rework board-bananapim5-sd-use-270-mmc-clock-phase-via-dt.patch meson64 edge 6.4: drop ODROID-N2+'s gpio fan patches, something similar landed upstream meson64 edge 6.4: simple fix for drv-spi-spidev-remove-warnings.patch meson64 edge 6.4: hammer general-gpu-drm-add-new-display-resolution-2560x1440.patch meson64 edge 6.4: drop general-meson-gx-mmc-fix-deferred-probing.patch -- upstreamed https://lore.kernel.org/linux-arm-kernel/16b74882-d65b-93c9-f72b-1d53bfefa22f@omp.ru/T/#t meson64 edge 6.4: rework general-meson-mmc-3-arm64-dts-docs-Update-mmc-meson-gx-documentation-for.patch into YAML meson64 edge 6.4: update .config at 6.4-rc5 enable a bunch of new _MESON and _AMLOGIC stuff meson64 edge 6.4: drop overlay patches in favor of bare overlays in specific folder meson64 edge 6.4: drop null-patched DTS files, add them bare in dt/ folder convert add-board-t95z.patch to board-t95z-add-rc-remote-keymap.patch since that's all that's left -spinor DTS really should be overlays, but keep them as alternate .dtbs for now This depends and requires https://github.com/armbian/build/pull/5308 View the full article

patching: Patching Summary and Patching Failures tables using Python's Rich + auto patchers: bare dts, bare overlays, DT Makefile patching: Patching Summary and Patching Failures tables using Python's Rich even Rich'er patch output by colorizing certain strings green/yellow/red BASE_GIT_TAG now very sneakily also accepts a branch name IMPORTANT: this includes: BREAKING CHANGE: patches failing to apply now break the build. fixes #4958 also break on legacy process_patch_file() failure, remove EXIT_PATCHING_ERROR patching: auto patchers: bare dts, bare overlays, DT Makefile View the full article

artifact-kernel: log what is the actual ${USERPATCHES_PATH}/kernel/${KERNELPATCHDIR} so people can find it artifact-kernel: log what is the actual ${USERPATCHES_PATH}/kernel/${KERNELPATCHDIR} so people can find it case in point: some families point KERNELPATCHDIR to something like archive/sunxi-5.15 which makes it harder to find than sunxi-legacy View the full article

export-logs: introduce PASTE_URL to make easy to change paste service used export-logs: introduce PASTE_URL to make easy to change paste service used View the full article

pipeline: download-debs: de-hardcode path to compile.sh for downloader pipeline: download-debs: de-hardcode path to compile.sh for downloader View the full article

armbian-gaming customize launcher for @NicoD-SBC (v2) armbian-gaming customize launcher for @NicoD-SBC (v2) add image suffix -gaming 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

Contrary to traditional software development, data is more important than code in machine learning. Building a high-performing model requires using reliable, precisely labelled data but poor-quality data is not always obvious. View the full article

Backport updates from Linux 6.3. In my testing this has no ill effects on SDIO 8822CS and fixes USB 8821CU dmesg | grep rtw [ 8.684999] rtw_8821cu 4-1:1.0: Firmware version 24.11.0, H2C version 12 [ 9.426555] usbcore: registered new interface driver rtw_8821cu lsmod | grep rtw88 rtw88_8821cu 16384 0 rtw88_8821c 81920 1 rtw88_8821cu rtw88_usb 20480 1 rtw88_8821cu rtw88_core 131072 2 rtw88_usb,rtw88_8821c mac80211 458752 2 rtw88_core,rtw88_usb cfg80211 331776 2 rtw88_core,mac80211 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

wireguard can be built successful on rk3566/rk3568/rk3588 socs. so we can remove these configurations. tested built orangepi5-plus and rock-3a. tested module load on orangepi5-plus. 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

orangepi5-plus.wip: initial Orange Pi 5 plus support using Xunlong vendor u-boot kernel dts is waiting for https://github.com/armbian/linux-rockchip/pull/38 to be merge i had tested on my opi5 plus(jammy/cli), it can boot from emmc, both 2 eth ports and nvme is working fine. View the full article

Description The 32-bit allwinner boards are known to hang with 6.1.30 kernel. On investigation, I was able to narrow the issue down to net-phy-Support-yt8531c.patch and upstream change for lib/mapple tree for some reason these two changes don't seem to be playing along very well. I am trying to get the reason for it, but so far even after enabling low level debugging, hung task detection, earlyprintk and countless such debugging option, I was not able to get more output from the kernel or to get the kernel into kgdb mode. This merge request is raised as a workaround for fixing the hang issue so that other task depending on the same can be unblocked. Jira reference number AR-1764 How Has This Been Tested? [X] Created an image with the change and booted on Nanopiduo2 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] 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 Requirement for commit c83b11cf1486ade72cfb92447e9212e654b43d8f so iw command is available on the default images. 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Remove stmmac change from net-phy-Support-yt8531c.patch as its causing 32-bit allwinner boards to hang on boot Description The 32-bit allwinner boards are known to hang with 6.1.30 kernel. On investigation, I was able to narrow the issue down to the above mentioned patch. The patch is supposed to add support for yt8531c, but it was also modifying stmmac ethernet driver to add a fix for realtek chip. This doesn't make sense to me and removing that code solved the issue. Jira reference number AR-1764 How Has This Been Tested? Created an bookworm current image for nanopi duo2 with and without stmmac part removed. [X] Removing the stmmac part of the patch results into board booting successfully [X] Restoring the stmmac part of the patch causes the board to hang 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 Mainline kernel 6.3 and above implements yt8531 driver. This pull request removes the legacy driver patch and fix the device tree for Orange Pi 4 LTS and other devices to use that driver. Note: this PR has a "dependency" upon this other PR (https://github.com/armbian/build/pull/5290) - these two PRs are unrelated, but the PR-5290 bug does not allow me to easily test without having conflicts later. This is just a note, everything should go on flawlessy once PR-5290 is merged. Jira reference number AR-1774 How Has This Been Tested? [x] Tested dtb on a live Orange Pi 4 LTS system [ ] Tested on Orange Pi R1 LTS (@schwar3kat) 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 [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description As per subject, implements same fix as https://github.com/armbian/build/pull/5216, but for kernel 6.3 How Has This Been Tested? [x] Patch applies [x] Bare dtb tested on live system 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

pipeline: repo-reprepro: run clearvanished and check before adding to repo pipeline: repo-reprepro: run clearvanished and check before adding to repo View the full article

repo: split image apt .list deployment into image-early and image-late repo: split image apt .list deployment into image-early and image-late split image apt .list deployment into image-early (after rootfs extract, before building) and image-late (after building) rationale: having the repo enabled during the image build can cause 'apt upgrade' and others to do inconsistent stuff depending on the (possibly random) state of the repo View the full article

prepare-host: check_host_has_enough_disk_space(): don't check if dir does not exist; fixes #5246 prepare-host: check_host_has_enough_disk_space(): don't check if dir does not exist; fixes #5246 View the full article

distro-agnostic: don't assume armbian.list exists when seding for beta distro-agnostic: don't assume armbian.list exists when seding for beta View the full article