RSS Bot

Description This is the generic default and should not have this postfix. How Has This Been Tested? [x] When ATFDIR is not set, the default directory is called simply "arm-trusted-firmware" 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 [x] Any dependent changes have been merged and published in downstream modules View the full article

Description Seems updates to all but the first extension hooks were not causing a rebuild, looks like the hash function dumper only looks at the first argument, but it is passed in a list of functions to dump in every call site. @rpardini , Does this look right? My BASH skills still need some work :smile: How Has This Been Tested? [x] Before this patch, make change to extension function (like fetch_custom_uboot) see that U-Boot is not regenerated [x] Make same change after applying this patch and see it now does get regenerated 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 The causes the first-stage bootloader to be generated before the normal U-Boot allowing the later build to use the firmware fetched during the first-stage build. How Has This Been Tested? [x] Boot SK-AM62B 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 This however only works for selected monitors with 1920x1080 and 4K resolutions. Also display seems to render extremely slowly. If the monitor is turned off and then on or is disconnected and reconnected while Armbian is running, monitor is not detected until a device reboot is performed. All of these however seems to be Khadas's kernel/u-boot limitations 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 attaching vim1s to samsung's 1920x1080 monitor [X] Rpardini tested on 4k display 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

rk3568-odroid/edge: bump to 6.5.y from -rc6; rebase all patches vs v6.5(.0) rk3568-odroid/edge: bump to 6.5.y from -rc6; rebase all patches vs v6.5(.0) View the full article

uefi-arm64/edge: bump to 6.5.y; rebase all patches vs v6.5(.0); fix Phytium's stmmac patch uefi-arm64/edge: bump to 6.5.y; rebase all patches vs v6.5(.0); fix Phytium's stmmac patch hammer patch driver-phytium-stmmac-acpi.patch use .remove_new due to "net: stmmac: Make stmmac_pltfr_remove() return void" View the full article

meson64/edge: bump to 6.5.y; rebase all patches vs v6.5(.0) meson64/edge: bump to 6.5.y; rebase all patches vs v6.5(.0) drop upstreamed patch meson-dts-add-missing-cache-properties.patch View the full article

bcm2711/edge: bump to RPi Foundation's 6.5.y branch; rebase all patches bcm2711/edge: bump to RPi Foundation's 6.5.y branch; rebase all patches 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 Add support for the HiKey 960 board. How Has This Been Tested? [x] Boot from SD Card [x] Serial console [x] USB ethernet [x] WLAN 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 Fixed the problem that nanopi r1 cannot boot from emmc. The reason is that uboot uses nanopineo's defconfig and dts when compiling so that it lacks the mmc2 definition. A topic on the forum about this issues: https://forum.armbian.com/topic/28704-nanopi-r1-emmc-install-fails-to-start How Has This Been Tested? Build and update u-boot 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 For some boards its time to be retired, but lets decide this together. Welcome to add / remove more. This can be here for few weeks, after release is just fine. View the full article

Description Patches are updated and build is successful. I haven't tested the kernel yet. Here are patch fixes: 1, add-rockchip-iep-driver.patch: rk3288.dtsi is moved to arch/arm/boot/dts/rockchip/rk3288.dtsi 2, general-possibility-of-disabling-rk808-rtc.patch: drivers/mfd/rk808.c is moved to drivers/mfd/rk8xx-core.c 3, rk356x-rga.patch: removed becaused of upstream merged 4, board-rockpis-0001-arm64-dts.patch: fixed due to upstream change 5, board-nanopi-r2c-plus.patch: new added patch fixing missing &vcc_io_33 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] Patches are all applied [x] Kernel build is successfull 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

The 6.5 release is here and it comes with many changes. As is often the case, Collabora has been actively involved in the submission of patches, mostly in the task of hardware enablement for Mediatek and Rockchip SoCs. View the full article

thinkpad-x13s: don't try to add Lunar x13s repos if BUILD_MINIMAL=yes thinkpad-x13s: don't try to add Lunar x13s repos if BUILD_MINIMAL=yes View the full article

Updated: 6.1 / 6.4 Added: 6.5 For doc sake, this update makes 6.1 slightly different than 6.4 and 6.5 in one particular area of main.c. As shown here: https://github.com/lwfinger/rtw88/commit/7746e2fa87a6687c068c9c746f6efbeee2616496 6.1 requires we use del_timer_sync, where the above releases use timer_delete_sync. Tested-on: ODROID-C4 X96-AIR BPI-CM4 (linux 6.x.y) There is no meson64-6.5 patch dir as of yet, so I didn't run an official test using Armbian. In my own personal builds, these patches all apply clean and the resulting kernel behaves as expected. 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 Simple calculator is must have desktop utility. Jira reference number AR-1834 How Has This Been Tested? Adding simple package which seems to be present everywhere. 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 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

Description Created udev config for renaming interfaces to WAN, LAN1, LAN2 Created device tree overlay rockchip-nanopi-r5s-leds for enabling front panel status LED's for NICs. enabled by default How Has This Been Tested? Built image. Leds work when cable plugged in. interface names are friendly root@nanopi-r5s:~# ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: wan: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 link/ether 12:ad:f7:2a:2f:a3 brd ff:ff:ff:ff:ff:ff altname end0 3: lan1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether c2:3b:8d:34:73:49 brd ff:ff:ff:ff:ff:ff altname enp1s0 4: lan2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether a6:5c:a3:ad:4c:33 brd ff:ff:ff:ff:ff:ff altname enP1p1s0 `` # 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

After rtw_usb_alloc_rx_bufs() has been called rx urbs have been allocated and must be freed in the error path. After rtw_usb_init_rx() has been called they are submitted, so they also must be killed. Add these forgotten steps to the probe error path. Besides the lost memory this also fixes a problem when the driver fails to download the firmware in rtw_chip_info_setup(). In this case it can happen that the completion of the rx urbs handler runs at a time when we already freed our data structures resulting in a kernel crash. This has been applied to wireless-next https://lore.kernel.org/linux-wireless/8b4b4228bfd140119665417137a087ea@realtek.com/T/#t [ ] 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 I had kept it back because I wasn't sure about what values to use for CONFIG_DRAM_SUN50I_H616_DX_ODT, CONFIG_DRAM_SUN50I_H616_DX_DRI, CONFIG_DRAM_SUN50I_H616_CA_DRI and CONFIG_DRAM_SUN50I_H616_TPR10. I found them on BigTreeTech's u-boot repository https://github.com/bigtreetech/u-boot/blob/v2023.07-cb1/configs/bigtreetech_cb1_defconfig 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] 2023.07.02 uboot builds successfully 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 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

thinkpad-x13s: move image customizations to bsp-cli thinkpad-x13s: move image customizations to bsp-cli should result in the same, except we can now update stuff via the bsp-cli pkg View the full article

Description They don't apply as they have been merged upstream and build fails. View the full article

odroidm1: really fix flashcp --partition non-usage for old mtd-utils (bullseye etc) odroidm1: really fix flashcp --partition non-usage for old mtd-utils (bullseye etc) we should probably refactor this into a shared library's functions... flashcp --partition is much more efficient than just dd'ing to mtdblockX but only supported on bookworm+ / jammy+ View the full article

pipeline: add userspace inventory capabilities config_post_main: sanity checks for RELEASE (vs ARCH) and RELEASE+DESKTOP_ENVIRONMENT (vs ARCH) the interactive menus didn't allow interactive users to select invalid combinations... ... but if specified directly on cmdline, no checks were done at all. introduce exit_with_target_not_supported_error(), which is just exit_with_error (code 43) but with code 44 this way the targets pipeline can just warn instead of break; sometimes it's easier multiplying matrixes and skipping the few that can't be built rpi4b: use exit_with_target_not_supported_error() instead of exit_with_error() if RELEASE is not supported pipeline: add userspace inventory capabilities digs into config/distributions and config/desktops for info this produces output/info/all_userspace_inventory.json this is now passed down to the targets-compositor in cli-jsoninfo targets-compositor now accepts userspace: as items-from-inventory extra: add targets-composed CLI command, to stop after targets-compositor pipeline: handle exit_with_target_not_supported_error() (retcode 44) as warning and not error split errors and warnings into multiple lines, so a bit easier to see in the logs what the real error was also turn down a few spurious warnings to debugs pipeline: use ncores * 4 for info gathering View the full article