RSS Bot

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

uboot: introduce hook post_config_uboot_target uboot: introduce hook post_config_uboot_target runs after other configuration changes, but before actually compiling a target useful to hack into .config for a specific target View the full article

rk3568-odroid edge: .config, remove ARCH_TEGRA and ARCH_SUNXI, since this is Rockchip kernel rk3568-odroid edge: update config, no actual changes rk3568-odroid edge: .config, remove ARCH_TEGRA and ARCH_SUNXI, since this is Rockchip kernel View the full article

BREAKING CHANGE: patches failing to apply now break the build. fixes #4958 BREAKING CHANGE: patches failing to apply now break the build. fixes #4958 also break on legacy process_patch_file() failure, remove EXIT_PATCHING_ERROR View the full article

Upstream link: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/net/phy/motorcomm.c?h=v6.3.5&id=4ac94f728a588e7096dd5010cd7141a309ea7805 How Has This Been Tested? No test preformed. 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

Lets us put down the hammer. Cleaned 6.1, 6.3 and added 6.2 patch set. Simplified function: rtw88_driver This PR was created in order to ease the pain here https://github.com/armbian/build/pull/5276 and add support for the current edge branch 6.2. 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

Description The 32-bit Allwinner dtb files are under /boot/dtb and not under /boot/dtb/allwinner as expected by u-boot because of the current board config. Fixed dtb location by removing the allwinner/ prefix for nanopi-r1 and nanopi duo2 boards. This issue seems to have already reported on the forums as well - https://forum.armbian.com/topic/28117-nanopi-duo-2-hang-on-boot/ How Has This Been Tested? Tested by creating edge image with the changes included in the pull request. The stable image still doesn't boot because of the ongoing issue with the 6.1.30 kernel image, but 6.2.16 kernel from edge image works [x] Created edge image and booted on nanopi duo2 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

driver_rtl8723cs: completely (not partially) disable for bcm2711 and d1 families I think Igor half-disabled this for the release. No use having half of this View the full article

rock-5a: fix broken u-boot build + move from family to board file rock-5a: fix broken u-boot build by forcing build of u-boot.dtb before u-boot.itb rock-5a: move board-specific code from family file to board file with post_family_config_branch_legacy hook View the full article

For @pyavitz @adeepn appreciation, most patches failed to apply on 6.3, and a few on 6.2. View the full article

rpardini's bag-of-stuff incl fixes - early June/'23 I'm back at it, fixing and breaking stuff. Fixing: prepare-host: check_host_has_enough_disk_space(): don't check if dir does not exist; fixes #5246 distro-agnostic: don't assume armbian.list exists when seding for beta pipeline: repo-reprepro: run clearvanished & check before adding to repo Breaking: BREAKING CHANGE: patches failing to apply now break the build. fixes #4958 also break on legacy process_patch_file() failure, remove EXIT_PATCHING_ERROR repo: 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 Other stuff armbian-gaming customize launcher for @NicoD-SBC (v2) add image suffix -gaming uboot: introduce hook post_config_uboot_target, runs after other configuration changes, but before actually compiling a target View the full article

This will reset bluetooth host-wake-gpios, enabling it to come back upon reboots. Jira reference number AR-1724 How Has This Been Tested? [X] On cold boot and reboot. 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

Description Adaptation of @the-going import and closing https://github.com/armbian/build/issues/5268 How Has This Been Tested? [x] Build test 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 [ ] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Simple change to h616 OrangepiZero2 LED's functioning. Resembles Legacy kernel behavior, symbolically signifies more active development OrangepiZero2 How Has This Been Tested? [x] Test A compiled and booted with expected result [ ] Test B Checklist: [x] 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 [x] Any dependent changes have been merged and published in downstream modules View the full article

A while back I presented USB 2.0 host support that was added to U-boot for the Radxa Rock-5B RK3588 Rockchip board. This time, USB 3.0 was added with support for the host and gadget. View the full article

BPI-CM4: In accordance with the BSP DTS, set LED gpio to GPIO_ACTIVE_LOW. Added default-on trigger to led-green Board now powers off, added reboot node 'meson64-reboot'. CONFIG_POWER_RESET_MESON64 Isolated RESET ODROID driver and renamed to MESON64 as it can be used in more than ODROIDS. MESON UART Series improves support for UART attached Bluetooth modules on Amlogic Meson G12A and newer SoCs. These SoCs also support the "divide XTAL by 2" bit which (greatly) reduces jitter when generating baud rates such as 1500000 (which is used by the Bluetooth part of the RTL8822CS SDIO WiFi and UART Bluetooth combo chip). Jira reference number [AR-9999] How Has This Been Tested? This has been tested on the BPI-CM4 IO and X96-AIR (X96-AIR to check the Bluetooth). The Meson64 Reset Driver in my testing works on the C4 and N2's, so if some one was so inclined they could add the node. 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

Description BigTreeTech CB1 current(6.1) & edge(6.2) patches. AXP313A PMIC ok Onboard RTL8189FS WIFI ok The Ethernet AC200/AC300 PHY drivers built-in H616 and HDMI have not yet been adapted. In fact, the HDMI of sun50i-h616-orangepi-zero2.dts and the ethernet of sun50i-h616-x96-mate.dts also have the same effect(cannot work) Jira reference number [AR-9999] How Has This Been Tested? Both BRANCH=current and BRANCH=edge have been compiled successfully without any errors and can be started normally when written to the device. 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

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 Additional driver support: Realtek 8822BS SDIO wireless network adapter Realtek 8822BU USB wireless network adapter Realtek 8822CS SDIO wireless network adapter Realtek 8822CU USB wireless network adapter Realtek 8821CS SDIO wireless network adapter Realtek 8821CU USB wireless network adapter Revert "Revert "BPI-CM4 IO: RTW88: Realtek 8822CS SDIO Wireless Support"": This reverts commit 672bd5393af1d8d59cad02462bc52980f1a99dfd. This restore commit 3f169bcae25557e60fe9fec613ab2a5bcf8219ac. Revert: https://github.com/armbian/build/pull/5257 Based on: https://github.com/armbian/build/pull/5248 WARNING: This move RTL88x2CS driver to EXTRA_WIFI=no Jira reference number AR-1724 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 @pyavitz on BPI-CM4 https://github.com/armbian/build/pull/5248 [X] Tested on JetHub D1/H1 https://github.com/armbian/build/pull/5248#issuecomment-1564117135 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