RSS Bot

Description Current rockchip64 bootscript always load kernel/etc from the first device partition, but not from partition bootscript itself was loaded. This PR makes bootscript load kernel/etc from the same partition. This allows to easily have multiple boot partitions (primary/backup) and switch them with MBR boot flags or GPT legacy_boot flags. How Has This Been Tested? [x] Compile and boot rk3318-box 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 [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description As per description. How Has This Been Tested? [ ] Build test Not tested on hardware. 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. [x] Someone tested with rock5 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 from rc1 to rc3 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] build [x] boot on OPi5 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 We use mkbootimg in rootfs which is installed only for jammy before. It's better to use mkbootimg from build host because this is a python script and may not run if build host and target rootfs are not the same release. This commit only make build for debian pass, but debian images won't work because of lacking packages. 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 build BOARD=xiaomi-elish BRANCH=sm8250 BUILD_DESKTOP=no BUILD_MINIMAL=yes DEB_COMPRESS=xz EXPERT=yes GITHUB_MIRROR=ghproxy KERNEL_CONFIGURE=no KERNEL_GIT=shallow MAINLINE_MIRROR=tuna RELEASE=trixie 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 The latest ATF has several fixes and improvements for the K3 platform. The current default ATFBRANCH is rather old (and should be updated, but I don't have all the other platforms needed to test right now). For now update to the latest stable tag for K3 platforms. How Has This Been Tested? [ ] Build and boot SK-AM64B [ ] Build and boot SK-AM62B [ ] Build and boot SK-TDA4VM 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 On older kernels like v6.1.x the TI devices are better supported by the TI vendor kernel than the upstream kernel. For the current kernel let's use the TI kernel for these boards. While here bump the edge kernel to v6.6.x which also has better support for features found on these platforms than v6.5.x. How Has This Been Tested? [x] Build and boot SK-AM64B with current kernel [ ] Build and boot SK-AM62B with current kernel [x] Build and boot SK-TDA4VM with current kernel [x] Build and boot SK-AM64B with edge kernel [ ] Build and boot SK-AM62B with edge kernel [ ] Build and boot SK-TDA4VM with edge kernel 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

The testing ecosystem in the Linux kernel has been steadily growing, but are efforts sufficiently coordinated? How can we help developers and maintainers integrate code more efficiently? How can we mitigate maintainer burnout? View the full article

The 3rd revision of the patch has been applied upstream. https://lore.kernel.org/linux-wireless/87cyvqsabo.fsf@kernel.org/T/#t I've been using this revision for about week now and all seems fine. 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 Resolves #5890 Jira reference number AR-1906 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 on RPi5 with mantic image. The iwconfig shows output shows that power management is off 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 Moving use of dbeinder's repo to fifteenhex repo for xradio driver as fifteenhex seems to give more consistent speeds. This also allows us to drop all of our xradio patches as we can now build right from fifteenhex code. 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 wifi on Orange Pi Zero 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 RPi5 in our bcm2711 kernel. This is mostly but not entirely based on changes from Raspberry Pi kernel PR 5618. After enabling those options, I noticed that even though hdmi was working, kernel was not able to find the sdcard and usb was also not working. So I had to use diffconfig to compare our configs with the vendor config and enable some more options. Raising the PR so that others can also play with it as well. Meanwhile I will work on getting Trixie Desktop Image running with mesa 23.3-rc5 from experimental repo. As part of that I will split RPi 5 into separate board config until recent version of mesa is made available in current debian or ubuntu distributions's backport repositories. 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 creating Mantic cli image. HDMI works, wifi works, ethernet is detected but I haven't tested if it works, usb 2 works, haven't tested usb3. 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 This was going to be used if building the bootloader from external source did not work. As this did work we never needed this blob, remove it. How Has This Been Tested? [x] SK-AM62B still builds and boots without this file Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Description thead: fix bluetooth problem, update to linux 6.7-rc3 Add RTL bluetooth firmware for LicheePi 4A. Update prebuilt opensbi binary. Update linux version and kernel config(fix SD-slot, cpufreq). How Has This Been Tested? [x] Successfully built. [x] System startup. 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

No descriptionView the full article

Description Maint. View the full article

Description Enabled CONFIG_RCU_TRACE as a workaround to fix booting 6.1.64 kernel on 32-bit allwinner boards. Edge kernel is not having this issue and hence workaround was not added for the same. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Booted on Orange Pi Zero (sun8i H3) 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 As per tittle. How Has This Been Tested? [ ] Build test, will run smoke tests right after too. 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 Fix uboot booting from zstd compressed BTRFS. uboot logs before fix: Found U-Boot script /boot/boot.scr ZSTD_decompressStream error 7 3252 bytes read in 41 ms (77.1 KiB/s) ... SCRIPT FAILED: continuing... Error 7 means "frame parameter window too large". It looks like uboot's max window size specification on decompressor init is totally wrong (compressed data size is used as max window size). Zstd default max window size is 128MB, but I'm unsure is it good idea to malloc 128MB in uboot on each BTRFS extent decompression. So I have capped minimum window size to 128KB - it should be sufficient for BTRFS as max compressed extent size is 128KB. How Has This Been Tested? [x] Compile [x] Boot ZSTD compressed BTRFS 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

Update maintainers and board status synced status from the database rename to .csc where we don't have anyone If you want to become a board maintainer, adjust data here. Ref: Board Maintainers Procedures and Guidelines View the full article

It is with the utmost excitement that we witness the release of PipeWire 1.0, the first officially stable release of this noteworthy inter-process multimedia streaming framework after many years of development. View the full article

Update maintainers and board status synced status from the database rename to .csc where we don't have anyone If you want to become a board maintainer, adjust data here. Ref: Board Maintainers Procedures and Guidelines View the full article

Description Add windows dev kit 2023 support Jira reference number [AR-9999] How Has This Been Tested? Tested on windows dev kit 2023 [X] installed on sd card and device is booting fine 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 Xiaomi Pad 5 pro is using pm8150b to support typec pd with volt up to 13.2V and current up to 6A, so I set the max negotiation to 12V5A. 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] xiaomi-elish kernel build success [x] I can negotiate 12V2A. $ sensors tcpm_source_psy_c440000.spmi:pmic@2:typec@1500-isa-0000 tcpm_source_psy_c440000.spmi:pmic@2:typec@1500-isa-0000 Adapter: ISA adapter in0: 12.00 V (min = +12.00 V, max = +12.00 V) curr1: 2.00 A (max = +2.00 A) 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

WSL2 "boards" wsl2-x86/wsl2-arm64 with current (6.1.y) and edge (6.6.y) kernels with Microsoft patches WSL2 "boards" wsl2-x86/wsl2-arm64 with current (6.1.y) and edge (6.6.y) kernels with Microsoft patches tl,dr: add 4 small-ish UEFI-like kernels, with Microsoft patches & fixes, for use with Microsoft WSL2 on x86/arm64 and 6.1.y/6.6.y the boards are UEFI derivatives, using a common microsoft vendor include to modify KERNELPATCHDIR/LINUXFAMILY (for now, we don't want those patches in regular UEFI builds / .debs) disable EXTRAWIFI (kernel is for a VM, will never have wifi so doesn't need any drivers) LINUXCONFIG, so we can use Microsoft's own monolithic kernel, required for WSL2 (their initrd is a mistery) really, what we're mostly interested right now are the kernels (in the future we might have an "Armbian" WSL2 app in the Microsoft Store) current 6.1.y: rebased from https://github.com/microsoft/WSL2-Linux-Kernel/tree/linux-msft-wsl-6.1.y onto real 6.1.y using Microsoft's .config exactly (monolithic, there are no =m's) edge 6.6.y: also from https://github.com/microsoft/WSL2-Linux-Kernel/tree/linux-msft-wsl-6.1.y but rebased onto 6.6.y using updated Microsoft's .config (monolithic, there are no =m's) dropped 2 of 6.1.y's patches that were actually upstreamed in the meantime: mm-page_reporting-Add-checks-for-page_reporting_order-param - mainlined in https://lore.kernel.org/all/1664517699-1085-2-git-send-email-shradhagupta@linux.microsoft.com/ hv_balloon-Add-support-for-configurable-order-free-page-reporting - mainlined in https://lore.kernel.org/all/1664517699-1085-3-git-send-email-shradhagupta@linux.microsoft.com/ drop the arm64: hyperv: Enable Hyper-V synthetic clocks/timers patch, since it causes asm breakage on 6.6.y a shame, but I tried and can't fix it myself - @kelleymh ? add my own patch to fix: 1709-drivers-hv-dxgkrnl-restore-uuid_le_cmp-removed-from-upstream-in-f5b3c341a.patch due to https://lore.kernel.org/all/20230202145412.87569-1-andriy.shevchenko@linux.intel.com/ landing in 6.6 1710-drivers-hv-dxgkrnl-adapt-dxg_remove_vmbus-to-96ec29396-s-reality-void-return.patch to adapt to https://lore.kernel.org/all/TYCP286MB2323A93C55526E4DF239D3ACCAFA9@TYCP286MB2323.JPNP286.PROD.OUTLOOK.COM/ wsl2: detect Armbian-built wsl2 kernel as well as Microsoft's default kernel previous commit introduces Armbian wsl2 kernels, might as well detect them View the full article