| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
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 | 26 天前 | |
rtl8723cs: stop including proprietary driver for kernel 6.19 onwards * rtw88 mainline driver has good enough support for rtl8723cs so stop patching the kernel with this ancient driver * fixes rtl8703b (same chip as 8723cs) bluetooth firmware name file | 7 个月前 | |
patch/misc: rtw88: rename and fix patch from 6.12.y It was never applied, therefore never recognized to fail, because there was a file name mismatch. Due to forward moving upstream minor changes were necessary to allow clean application | 4 个月前 | |
rtl8723cs: stop including proprietary driver for kernel 6.19 onwards * rtw88 mainline driver has good enough support for rtl8723cs so stop patching the kernel with this ancient driver * fixes rtl8703b (same chip as 8723cs) bluetooth firmware name file | 7 个月前 | |
Add gpio power reset for hci_h5 controllers in h5_btrtl_open (#3208) | 4 年前 | |
Merge neofetch to armbian-config (#2499) | 5 年前 | |
Add support for rtl8822cs (hci_ver 0x8) bluetooth (#3201) Signed-off-by: chbgdn <chbgdn@gmail.com> | 4 年前 | |
Move header revert patch under misc patches (#4128) * Move header revert patch under misc patches as its only related to extra wifi drivers * Update text | 3 年前 | |
Add Wi-Fi injection patch for Linux 6.12 kernels. | 10 个月前 | |
Add two popular MT7921U devices to the driver pid so they work OOB Signed-off-by: Igor <igor@armbian.com> | 2 年前 | |
Upgrade EDGE to 5.12.y (#2825) * Bump imx6 edge to 5.12.y * Bump odroid xu4 edge to 5.12.y * Bump Jetson nano edge to 5.12.y * WIP: Bump sunxi to 5.12.y - create a copy of patches and make a new link - wireless patches needs adjutement to 5.12 - some patches are still failing * Adjust wireless patches to build on 5.12.y * Remove template wireless patch * Move Espressobin edge to 5.12.y * Bump mvebu to 5.12 - patch 92-mvebu-gpio-remove-hardcoded-timer-assignment.patch was disabled @heisath - adjusted wireless driver for 8723ds * Adjust sunxi / sunxi64 edge to compile * Fix kernel config for Jetson nano edge * bump meson64 to 5.12.y * bump rockchip edge to 5.12.y * Bump rockchip64 to 5.12.y * Bump rk322x edge to 5.12.y @paolosabatino * Cleanup im6, re-add 5.10.y patches since one is missing in 5.12.y * Update odroidxu4 edge links * rk322x: moved rk322x-edge to kernel 5.12, fix overlay compilation, retouched included kernel modules * Cleanup: remove deprecated config Co-authored-by: Paolo Sabatino <paolo.sabatino@gmail.com> | 5 年前 | |
Split wireless VFS patches (#4775) | 3 年前 | |
Fix wireless modules indentation warnings | 3 年前 | |
rtlwifi: Fix p2p-go advertising (#4717) | 3 年前 | |
Fix uninitialized cfg80211_chan_def for rtlwifi (#4714) Co-authored-by: Igor Pečovnik <igorpecovnik@users.noreply.github.com> | 3 年前 | |
Fixing out of the tree wireless driver compilation (#2635) * Fix compilating on 5.10.y / 5.11.y for Realtek 8188EU * Cleanup | 5 年前 | |
drivers: fix cfg80211 set_monitor_channel build on 6.12.101 The cfg80211 ->set_monitor_channel() callback gained a `struct net_device *dev` argument in 6.13 mainline, which was backported into the 6.12.101 stable release. The out-of-tree Realtek drivers guard the new 3-arg prototype at KERNEL_VERSION(6, 13, 0), so on 6.12.101 they still emit the old 2-arg signature and fail to build. This breaks x86-legacy, mvebu64-current and every other family that tracks 6.12.101. Add one patch per affected driver under patch/misc/ (the hashed, per-driver convention already used by the wireless-*-Fix-*.patch files) lowering the guard to KERNEL_VERSION(6, 12, 101), and apply it from each driver function in drivers_network.sh. Affected drivers: rtl8189es, rtl8189fs, rtl8192eu, rtl8812au, rtl8811cu, rtl88x2bu. Signed-off-by: Igor Pecovnik <igor@armbian.com> | 30 天前 | |
drivers: fix cfg80211 set_monitor_channel build on 6.12.101 The cfg80211 ->set_monitor_channel() callback gained a `struct net_device *dev` argument in 6.13 mainline, which was backported into the 6.12.101 stable release. The out-of-tree Realtek drivers guard the new 3-arg prototype at KERNEL_VERSION(6, 13, 0), so on 6.12.101 they still emit the old 2-arg signature and fail to build. This breaks x86-legacy, mvebu64-current and every other family that tracks 6.12.101. Add one patch per affected driver under patch/misc/ (the hashed, per-driver convention already used by the wireless-*-Fix-*.patch files) lowering the guard to KERNEL_VERSION(6, 12, 101), and apply it from each driver function in drivers_network.sh. Affected drivers: rtl8189es, rtl8189fs, rtl8192eu, rtl8812au, rtl8811cu, rtl88x2bu. Signed-off-by: Igor Pecovnik <igor@armbian.com> | 30 天前 | |
drivers: fix cfg80211 set_monitor_channel build on 6.12.101 The cfg80211 ->set_monitor_channel() callback gained a `struct net_device *dev` argument in 6.13 mainline, which was backported into the 6.12.101 stable release. The out-of-tree Realtek drivers guard the new 3-arg prototype at KERNEL_VERSION(6, 13, 0), so on 6.12.101 they still emit the old 2-arg signature and fail to build. This breaks x86-legacy, mvebu64-current and every other family that tracks 6.12.101. Add one patch per affected driver under patch/misc/ (the hashed, per-driver convention already used by the wireless-*-Fix-*.patch files) lowering the guard to KERNEL_VERSION(6, 12, 101), and apply it from each driver function in drivers_network.sh. Affected drivers: rtl8189es, rtl8189fs, rtl8192eu, rtl8812au, rtl8811cu, rtl88x2bu. Signed-off-by: Igor Pecovnik <igor@armbian.com> | 30 天前 | |
wireless patches: fix build for kernel 6.13 | 1 年前 | |
rtlwifi: Fix p2p-go advertising (#4717) | 3 年前 | |
Remove deprecated patch (#4114) | 3 年前 | |
kernel: drivers: `wireless-rtl8723du-6.3.patch`: don't patch the same thing twice | 3 年前 | |
Split wireless VFS patches (#4775) | 3 年前 | |
rtlwifi: Fix p2p-go advertising (#4717) | 3 年前 | |
Fix uninitialized cfg80211_chan_def for rtlwifi (#4714) Co-authored-by: Igor Pečovnik <igorpecovnik@users.noreply.github.com> | 3 年前 | |
uefi-arm64: bump to 6.16 | 1 年前 | |
drivers: fix cfg80211 set_monitor_channel build on 6.12.101 The cfg80211 ->set_monitor_channel() callback gained a `struct net_device *dev` argument in 6.13 mainline, which was backported into the 6.12.101 stable release. The out-of-tree Realtek drivers guard the new 3-arg prototype at KERNEL_VERSION(6, 13, 0), so on 6.12.101 they still emit the old 2-arg signature and fail to build. This breaks x86-legacy, mvebu64-current and every other family that tracks 6.12.101. Add one patch per affected driver under patch/misc/ (the hashed, per-driver convention already used by the wireless-*-Fix-*.patch files) lowering the guard to KERNEL_VERSION(6, 12, 101), and apply it from each driver function in drivers_network.sh. Affected drivers: rtl8189es, rtl8189fs, rtl8192eu, rtl8812au, rtl8811cu, rtl88x2bu. Signed-off-by: Igor Pecovnik <igor@armbian.com> | 30 天前 | |
uefi-arm64: bump to 6.16 | 1 年前 | |
drivers: fix cfg80211 set_monitor_channel build on 6.12.101 The cfg80211 ->set_monitor_channel() callback gained a `struct net_device *dev` argument in 6.13 mainline, which was backported into the 6.12.101 stable release. The out-of-tree Realtek drivers guard the new 3-arg prototype at KERNEL_VERSION(6, 13, 0), so on 6.12.101 they still emit the old 2-arg signature and fail to build. This breaks x86-legacy, mvebu64-current and every other family that tracks 6.12.101. Add one patch per affected driver under patch/misc/ (the hashed, per-driver convention already used by the wireless-*-Fix-*.patch files) lowering the guard to KERNEL_VERSION(6, 12, 101), and apply it from each driver function in drivers_network.sh. Affected drivers: rtl8189es, rtl8189fs, rtl8192eu, rtl8812au, rtl8811cu, rtl88x2bu. Signed-off-by: Igor Pecovnik <igor@armbian.com> | 30 天前 | |
Split wireless VFS patches (#4775) | 3 年前 | |
Fix wireless modules indentation warnings | 3 年前 | |
rtlwifi: Fix p2p-go advertising (#4717) | 3 年前 | |
Fix uninitialized cfg80211_chan_def for rtlwifi (#4714) Co-authored-by: Igor Pečovnik <igorpecovnik@users.noreply.github.com> | 3 年前 | |
uefi-arm64: bump to 6.16 | 1 年前 | |
drivers: fix cfg80211 set_monitor_channel build on 6.12.101 The cfg80211 ->set_monitor_channel() callback gained a `struct net_device *dev` argument in 6.13 mainline, which was backported into the 6.12.101 stable release. The out-of-tree Realtek drivers guard the new 3-arg prototype at KERNEL_VERSION(6, 13, 0), so on 6.12.101 they still emit the old 2-arg signature and fail to build. This breaks x86-legacy, mvebu64-current and every other family that tracks 6.12.101. Add one patch per affected driver under patch/misc/ (the hashed, per-driver convention already used by the wireless-*-Fix-*.patch files) lowering the guard to KERNEL_VERSION(6, 12, 101), and apply it from each driver function in drivers_network.sh. Affected drivers: rtl8189es, rtl8189fs, rtl8192eu, rtl8812au, rtl8811cu, rtl88x2bu. Signed-off-by: Igor Pecovnik <igor@armbian.com> | 30 天前 | |
wireless patches: fix build for kernel 6.13 | 1 年前 | |
sunxi: xradio: Switching from del_timer_sync to timer_delete_sync This was introduced in 6.2 but was removed from the kernel code in 6.15. We are currently building cores for sunxi starting from 6.6. Therefore, a simple replacement without conditions. | 1 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 26 天前 | ||
| 7 个月前 | ||
| 4 个月前 | ||
| 7 个月前 | ||
| 4 年前 | ||
| 5 年前 | ||
| 4 年前 | ||
| 3 年前 | ||
| 10 个月前 | ||
| 2 年前 | ||
| 5 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 5 年前 | ||
| 30 天前 | ||
| 30 天前 | ||
| 30 天前 | ||
| 1 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 1 年前 | ||
| 30 天前 | ||
| 1 年前 | ||
| 30 天前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 3 年前 | ||
| 1 年前 | ||
| 30 天前 | ||
| 1 年前 | ||
| 1 年前 |