| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
fix(atf): move imx8m/imx93 ATF linker-flag patch to shared atf-tq dir ATF_SKIP_LDFLAGS_WL="yes" was not a substitute for 0001-fix-needed-by-armbian-build-system.patch: that patch strips the -Wl,-prefixed --no-warn-rwx-segment flag from TF_LDFLAGS because TQ's ATF build invokes the linker directly, while ATF_SKIP_LDFLAGS_WL only suppresses the -Wl, prefix on our side, leaving a flag the patch never matches. Without the patch applied, TF_LDFLAGS reaches the linker unfiltered and produces a BL31 that hangs on i.MX93 (MBa93xxCA) right after SPL hands off via ROM_API, before any ATF console output. Rename ATFPATCHDIR from the imx8-only 'atf-imx8' to 'atf-tq' and set it per-board-case in imx8m.conf/imx93.conf, since the same fix is needed by both families. Signed-off-by: Martin Schmiedel <Martin.Schmiedel@tq-group.com> | 3 天前 | |
OrangePi 3 LTS: Use pine_h64 crust defconfig It is identical to the one that was being created via patch. Signed-off-by: Patrick Yavitz <pyavitz@gmail.com> | 6 个月前 | |
Add Milk-V DuoS, an aarch64+riscv64 board (#10326) * Add Milk-V DuoS, an aarch64+riscv64 board * sophgo-sg200x: give our own patches real authorship headers The 34 patches written for this port carried the placeholder header the autopatcher emits - "From: Armbian <info@armbian.com>" over a made-up Date - which says nothing about who wrote them or when. Review asked for something meaningful. Each now names its real author and carries the date of the commit that last changed that patch's content on the development branch, so the header matches the history the patch actually has. Where a patch was revised after it was first written - 0044 and 0052/0053 for the DT changes, 0046 for the regenerated comment - the date is that of the revision, not the original. The all-zero commit hash on the first line stays: these patches have no upstream commit to point at, and that is what the rest of the tree uses to say so. Header lines only; no patch payload was touched. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * sophgo-sg200x: header the arm64 patches that had none Ten patches went in as bare diffs - no From, no Date, no Subject, just a blank line and the payload. They are the arm64 counterparts of 0040/0042/0044/0046/ 0048, written in the same commits as their riscv twins and touching only files this port creates, so they are ours to sign. Each now carries the same header its twin does, dated to the commit that last changed it - which for 0045 and 0047 is the commit that revised the pair, so the two architectures stay in step. The body is one line pointing at the riscv twin rather than a copy of its reasoning; the same change against the other DTS does not need the argument made twice. The two aic8800 patches had a real author but a placeholder Date of midnight UTC; they now carry the date they were written. Header lines only; no patch payload was touched. Every patch in this series now has a From, a Date and a Subject. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * sophgo-sg200x: cut the comment wall in the family include Review asked for the absolute minimum here, and it was fair: 515 of the file's 988 lines were comment, several blocks running twenty or thirty lines to argue a case rather than state one. What is left says what each line does, and nothing else. Where a value looks arbitrary the comment names the constraint behind it - boot.cmd rather than boot.scr, CHIP_ARCH through the environment, "riscv" rather than "riscv64" - in a clause, not a paragraph. The reasoning that was dropped is not lost; it belongs in the port documentation rather than in a config file. 135 comment lines remain, down from 515, and the file is 607 lines rather than 988. Comments only: stripping comments and blank lines from this revision and from the original gives identical files. shfmt and bash -n are clean. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * board: cut the Milk-V Duo S configs to the house format The first line of a board config is a one-line hardware description and nothing else. These carried a twelve-line preamble explaining the two-core split, the slide switch and how to read the boot log, plus a link to the vendor page. Both are now a single line in the form the rest of config/boards uses, with the core naming the only difference between them. The explanation of why one board ships as two configs is a thing to write down once, not in both files. * sophgo-sg200x: follow the tree's release candidate pin The bleedingedge branch pinned KERNELBRANCH to tag:v7.2-rc5 locally. That is the tree's decision, not a family's: config/sources/common.conf only calls the mainline_kernel_decide_version hooks when KERNELBRANCH is still empty, so the local pin suppressed the whole chain in mainline-kernel.conf.sh - including the hook that points KERNELSOURCE at Linus's tree when the stable mirrors have not caught up with the tag yet. Dropping it lets this family track the global pin, which is bumped weekly, instead of sitting on whichever candidate happened to be current the day it was written. * trim family config comments * remove nonexistent package removal from board configs * move kernel_comp_addr_r to 0x88000000 * implement a better fip.bin size guard. Unlikely to ever be needed * address Rabbit's concern * address Rabbit's concerns about USB gadget * fix btrfs potential failure * address the easy nitpick comments * reorder board family lines * Changes to the Bluetooth service addressing Rabbit's concerns * move the Duo S Bluetooth extension to a proper directory * address more of Rabbit's concerns about size | 24 天前 | |
uefi-x86-7.3: rewrite patches against 7.3-rc1 | 1 天前 | |
Add Milk-V DuoS, an aarch64+riscv64 board (#10326) * Add Milk-V DuoS, an aarch64+riscv64 board * sophgo-sg200x: give our own patches real authorship headers The 34 patches written for this port carried the placeholder header the autopatcher emits - "From: Armbian <info@armbian.com>" over a made-up Date - which says nothing about who wrote them or when. Review asked for something meaningful. Each now names its real author and carries the date of the commit that last changed that patch's content on the development branch, so the header matches the history the patch actually has. Where a patch was revised after it was first written - 0044 and 0052/0053 for the DT changes, 0046 for the regenerated comment - the date is that of the revision, not the original. The all-zero commit hash on the first line stays: these patches have no upstream commit to point at, and that is what the rest of the tree uses to say so. Header lines only; no patch payload was touched. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * sophgo-sg200x: header the arm64 patches that had none Ten patches went in as bare diffs - no From, no Date, no Subject, just a blank line and the payload. They are the arm64 counterparts of 0040/0042/0044/0046/ 0048, written in the same commits as their riscv twins and touching only files this port creates, so they are ours to sign. Each now carries the same header its twin does, dated to the commit that last changed it - which for 0045 and 0047 is the commit that revised the pair, so the two architectures stay in step. The body is one line pointing at the riscv twin rather than a copy of its reasoning; the same change against the other DTS does not need the argument made twice. The two aic8800 patches had a real author but a placeholder Date of midnight UTC; they now carry the date they were written. Header lines only; no patch payload was touched. Every patch in this series now has a From, a Date and a Subject. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * sophgo-sg200x: cut the comment wall in the family include Review asked for the absolute minimum here, and it was fair: 515 of the file's 988 lines were comment, several blocks running twenty or thirty lines to argue a case rather than state one. What is left says what each line does, and nothing else. Where a value looks arbitrary the comment names the constraint behind it - boot.cmd rather than boot.scr, CHIP_ARCH through the environment, "riscv" rather than "riscv64" - in a clause, not a paragraph. The reasoning that was dropped is not lost; it belongs in the port documentation rather than in a config file. 135 comment lines remain, down from 515, and the file is 607 lines rather than 988. Comments only: stripping comments and blank lines from this revision and from the original gives identical files. shfmt and bash -n are clean. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * board: cut the Milk-V Duo S configs to the house format The first line of a board config is a one-line hardware description and nothing else. These carried a twelve-line preamble explaining the two-core split, the slide switch and how to read the boot log, plus a link to the vendor page. Both are now a single line in the form the rest of config/boards uses, with the core naming the only difference between them. The explanation of why one board ships as two configs is a thing to write down once, not in both files. * sophgo-sg200x: follow the tree's release candidate pin The bleedingedge branch pinned KERNELBRANCH to tag:v7.2-rc5 locally. That is the tree's decision, not a family's: config/sources/common.conf only calls the mainline_kernel_decide_version hooks when KERNELBRANCH is still empty, so the local pin suppressed the whole chain in mainline-kernel.conf.sh - including the hook that points KERNELSOURCE at Linus's tree when the stable mirrors have not caught up with the tag yet. Dropping it lets this family track the global pin, which is bumped weekly, instead of sitting on whichever candidate happened to be current the day it was written. * trim family config comments * remove nonexistent package removal from board configs * move kernel_comp_addr_r to 0x88000000 * implement a better fip.bin size guard. Unlikely to ever be needed * address Rabbit's concern * address Rabbit's concerns about USB gadget * fix btrfs potential failure * address the easy nitpick comments * reorder board family lines * Changes to the Bluetooth service addressing Rabbit's concerns * move the Duo S Bluetooth extension to a proper directory * address more of Rabbit's concerns about size | 24 天前 | |
Add Milk-V DuoS, an aarch64+riscv64 board (#10326) * Add Milk-V DuoS, an aarch64+riscv64 board * sophgo-sg200x: give our own patches real authorship headers The 34 patches written for this port carried the placeholder header the autopatcher emits - "From: Armbian <info@armbian.com>" over a made-up Date - which says nothing about who wrote them or when. Review asked for something meaningful. Each now names its real author and carries the date of the commit that last changed that patch's content on the development branch, so the header matches the history the patch actually has. Where a patch was revised after it was first written - 0044 and 0052/0053 for the DT changes, 0046 for the regenerated comment - the date is that of the revision, not the original. The all-zero commit hash on the first line stays: these patches have no upstream commit to point at, and that is what the rest of the tree uses to say so. Header lines only; no patch payload was touched. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * sophgo-sg200x: header the arm64 patches that had none Ten patches went in as bare diffs - no From, no Date, no Subject, just a blank line and the payload. They are the arm64 counterparts of 0040/0042/0044/0046/ 0048, written in the same commits as their riscv twins and touching only files this port creates, so they are ours to sign. Each now carries the same header its twin does, dated to the commit that last changed it - which for 0045 and 0047 is the commit that revised the pair, so the two architectures stay in step. The body is one line pointing at the riscv twin rather than a copy of its reasoning; the same change against the other DTS does not need the argument made twice. The two aic8800 patches had a real author but a placeholder Date of midnight UTC; they now carry the date they were written. Header lines only; no patch payload was touched. Every patch in this series now has a From, a Date and a Subject. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * sophgo-sg200x: cut the comment wall in the family include Review asked for the absolute minimum here, and it was fair: 515 of the file's 988 lines were comment, several blocks running twenty or thirty lines to argue a case rather than state one. What is left says what each line does, and nothing else. Where a value looks arbitrary the comment names the constraint behind it - boot.cmd rather than boot.scr, CHIP_ARCH through the environment, "riscv" rather than "riscv64" - in a clause, not a paragraph. The reasoning that was dropped is not lost; it belongs in the port documentation rather than in a config file. 135 comment lines remain, down from 515, and the file is 607 lines rather than 988. Comments only: stripping comments and blank lines from this revision and from the original gives identical files. shfmt and bash -n are clean. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * board: cut the Milk-V Duo S configs to the house format The first line of a board config is a one-line hardware description and nothing else. These carried a twelve-line preamble explaining the two-core split, the slide switch and how to read the boot log, plus a link to the vendor page. Both are now a single line in the form the rest of config/boards uses, with the core naming the only difference between them. The explanation of why one board ships as two configs is a thing to write down once, not in both files. * sophgo-sg200x: follow the tree's release candidate pin The bleedingedge branch pinned KERNELBRANCH to tag:v7.2-rc5 locally. That is the tree's decision, not a family's: config/sources/common.conf only calls the mainline_kernel_decide_version hooks when KERNELBRANCH is still empty, so the local pin suppressed the whole chain in mainline-kernel.conf.sh - including the hook that points KERNELSOURCE at Linus's tree when the stable mirrors have not caught up with the tag yet. Dropping it lets this family track the global pin, which is bumped weekly, instead of sitting on whichever candidate happened to be current the day it was written. * trim family config comments * remove nonexistent package removal from board configs * move kernel_comp_addr_r to 0x88000000 * implement a better fip.bin size guard. Unlikely to ever be needed * address Rabbit's concern * address Rabbit's concerns about USB gadget * fix btrfs potential failure * address the easy nitpick comments * reorder board family lines * Changes to the Bluetooth service addressing Rabbit's concerns * move the Duo S Bluetooth extension to a proper directory * address more of Rabbit's concerns about size | 24 天前 | |
Restore the the E52C-specific reopen-disabled-nodes-for-rk3582 patch against v2026.01 | 2 天前 |