aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* tools/dwarves: add myself as PKG_MAINTAINERTony Ambardar2024-04-15
| | | | | | Missed setting this when first adding package. Signed-off-by: Tony Ambardar <itugrok@yahoo.com>
* bridger: update to Git HEAD (2024-04-15)Felix Fietkau2024-04-15
| | | | | | | | 3159bbe0a2eb improve isolation when selecting a fixed output port c77a7a1ff74d nl: fix getting flow offload stats a08e51e679dd add support for disabling bridge-local flows via config Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ramips: Add support for D-Link DIR-3040 A1Vince McKinsey2024-04-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds support for the A1 hardware revision of the DIR-3040. It is an exact copy of the DIR-3060 save for some cosmetic changes to the housing. Even going so far as having the same FCC ID. Hardware specification: SoC: MediaTek MT7621AT Flash: Winbond W29N01HVSINA 128MB RAM: Micron MT41K128M16JT-125 256MB Ethernet: 5x 10/100/1000 Mbps WiFi1: MT7615DN 2.4GHz N 2x2:2 WiFi2: MT7615DN 5GHz AC 2x2:2 WiFi3: MT7615N 5GHz AC 4x4:4 Button: WPS, Reset Flash instructions: OpenWrt can be installed via D-Link Recovery GUI: NOTE: Seems to only work in Firefox on Windows. Tried with Chrome on Windows, Firefox in Linux, and Chromium in Linux. None of these other browsers worked. 1. Push and hold reset button (on the bottom of the device) until power led starts flashing (about 10 secs or so) while plugging in the power cable. 2. Give it ~30 seconds, to boot the recovery mode GUI 3. Connect your client computer to LAN1 of the device 4. Set your client IP address manually to 192.168.0.2 / 255.255.255.0. 5. Call the recovery page for the device at http://192.168.0.1/ 6. Use the provided emergency web GUI to upload and flash a new firmware to the device Thanks to @Lucky1openwrt and @iivailo for creating the DIR-3060 DTS file and related changes, so it was possible for me to adapt them to the DIR-3040, build images, test and fix minor issues. MAC Addresses: | use | address | example | | --- | --- | --- | | LAN | label | f4:*:61 | | WAN | label + 4 | f4:*:65 | | WI1/2g | label + 2 | f4:*:63 | | WI1/5g | label + 1 | f4:*:62 | | WI2/5g | label + 3 | f4:*:64 | The label MAC address was found in Factory, 0xe000 Checklist: ✓ nand ✓ ethernet ✓ button ✓ wifi2g ✓ wifi5g ✓ wifi5g ✓ mac ✓ led Signed-off-by: Vince McKinsey <vincemckinsey@gmail.com>
* tools: libdeflate: update to 1.20Robert Marko2024-04-14
| | | | | | | | | | | | | | | | | | | | | | | | | Changes: * Improved CRC-32 performance on recent x86 CPUs by adding VPCLMULQDQ-accelerated implementations using 256-bit and 512-bit vectors. * Improved Adler-32 performance on recent x86 CPUs by adding VNNI-accelerated implementations using 256-bit and 512-bit vectors. * Improved CRC-32 and Adler-32 performance on short inputs. * Optimized the portable implementation of Adler-32. * Added some basic optimizations for RISC-V. * Dropped support for gcc versions older than v4.9 (released in 2014) and clang versions older than v3.9 (released in 2016). * Dropped support for CRC-32 acceleration on 32-bit ARM using the ARMv8 pmull or crc32 instructions. This code only worked on CPUs that also have a 64-bit mode, and it was already disabled on many compiler versions due to compiler limitations. CRC-32 acceleration remains fully supported on 64-bit ARM. Signed-off-by: Robert Marko <robimarko@gmail.com>
* mvebu: fix LEDs on IIJ SA-W2INAGAKI Hiroshi2024-04-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On IIJ SA-W2, some multiple LEDs have no "function" property and only "color" property is available for the newer binding of LED on Linux Kernel. 9d93b6d091 ("mvebu: drop redundant label with new LED color/function format") removes "label" property from LEDs, then, multiple "<color>:" (ex.: "green:"/"red:") will be appeared and renamed to "<color>:_<num>" (ex.: "green:_1", "green:_2", ...) by kernel. log: [ 1.911118] leds-gpio leds: Led green: renamed to green:_1 due to name collision [ 1.918600] leds-gpio leds: Led red: renamed to red:_1 due to name collision [ 1.925727] leds-gpio leds: Led green: renamed to green:_2 due to name collision [ 1.933202] leds-gpio leds: Led red: renamed to red:_2 due to name collision [ 1.940321] leds-gpio leds: Led green: renamed to green:_3 due to name collision [ 1.947797] leds-gpio leds: Led red: renamed to red:_3 due to name collision [ 1.954939] leds-gpio leds: Led green: renamed to green:_4 due to name collision [ 1.962456] leds-gpio leds: Led green: renamed to green:_5 due to name collision /sys/class/leds: root@OpenWrt:/# ls /sys/class/leds/ green: green:_3 green:status red:_2 green:_1 green:_4 red: red:_3 green:_2 green:_5 red:_1 red:status Fix this issue by adding missing "function" (and "function-enumerator") property to those LEDs on IIJ SA-W2. Fixes: 9d93b6d091 ("mvebu: drop redundant label with new LED color/function format") Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* mvebu: fix LEDs on Fortinet FortiGate devicesINAGAKI Hiroshi2024-04-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On Fortinet FortiGate 30E/50E, some multiple LEDs have no "function" property and only "color" property is available for the new binding of LED on Linux Kernel. 9d93b6d091 ("mvebu: drop redundant label with new LED color/function format") removes "label" property from LEDs, then, multiple "<color>:" (ex.: "green:"/"red:"/"amber:") will be appeared as LED names and renamed to "<color>:_<num>" (ex.: "green:_1", "green:_2", ...) by kernel. log: [ 12.425170] leds-gpio gpio-leds: Led green: renamed to green:_1 due to name collision [ 12.520390] leds-gpio gpio-leds: Led amber: renamed to amber:_1 due to name collision [ 12.614931] leds-gpio gpio-leds: Led green: renamed to green:_2 due to name collision [ 12.709895] leds-gpio gpio-leds: Led green: renamed to green:_3 due to name collision [ 12.804439] leds-gpio gpio-leds: Led amber: renamed to amber:_2 due to name collision [ 12.898969] leds-gpio gpio-leds: Led green: renamed to green:_4 due to name collision [ 12.993504] leds-gpio gpio-leds: Led amber: renamed to amber:_3 due to name collision [ 13.088033] leds-gpio gpio-leds: Led green: renamed to green:_5 due to name collision [ 13.182570] leds-gpio gpio-leds: Led green: renamed to green:_6 due to name collision [ 13.277103] leds-gpio gpio-leds: Led amber: renamed to amber:_4 due to name collision [ 13.371636] leds-gpio gpio-leds: Led green: renamed to green:_7 due to name collision /sys/class/leds: root@OpenWrt:/# ls /sys/class/leds/ amber: amber:_4 green:_2 green:_6 red:alarm amber:_1 amber:alarm green:_3 green:_7 red:status amber:_2 green: green:_4 green:status amber:_3 green:_1 green:_5 red: Fix this issue by adding missing "function" (and "function-enumerator") property those to LEDs on Fortinet FortiGate devices. Note: there is no appropriate function for "ha" LEDs in dt-bindings/leds/common.h, so use the hardcoded string for them instead. Fixes: 9d93b6d091 ("mvebu: drop redundant label with new LED color/function format") Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* kernel: add pending patches for new LED_FUNCTION_* definitionsINAGAKI Hiroshi2024-04-14
| | | | | | | Add pending patches to add LED_FUNCTION_MOBILE and LED_FUNCTION_SPEED_* definitions for Fortinet FortiGate devices and IIJ SA-W2. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* ath79: add support for Comfast CF-EW71 v2Felix Golatofski2024-04-14
| | | | | | | | | | | | | | | | | | Specifications: Qualcomm/Atheros QCA9531 2x 10/100 Mbps Ethernet, with 48v PoE 2T2R 2.4 GHz, 802.11b/g/n 128MB RAM 16MB SPI Flash 4x LED (Always On Power, LAN, WAN, WLAN) Flashing instructions: The original firmware is based on OpenWrt, so flashing the sysupgrade image over the factory firmware is sufficient. The bootloader has a built-in recovery web-ui. This is the method I used to flash OpenWrt. You can get to the recovery web-ui by holding down the reset button for a few seconds (~5s) while pluggin in the router. The LEDs should start blinking fast and the router should be available on 192.168.1.1 for the recovery. Tested: Reset button, WAN LED, LAN LED, Power LED (always on, not much to test), WLAN LED, MAC addresses (same as factory firmware). Signed-off-by: Felix Golatofski <git@xdfr.de>
* uboot-rockchip: Update to 2024.04Tianling Shen2024-04-14
| | | | | | Removed upstreamed patch. Signed-off-by: Tianling Shen <cnsztl@immortalwrt.org>
* rkbin: bump to latest git HEADTianling Shen2024-04-14
| | | | | | | Fixed bugs for memory initialization/training, improved memory compatibility/stability. Signed-off-by: Tianling Shen <cnsztl@immortalwrt.org>
* kernel: bump 6.1 to 6.1.86Hauke Mehrtens2024-04-14
| | | | | | | | | | | Removed upstreamed: bcm27xx/patches-6.1/950-1235-drm-vc4-don-t-check-if-plane-state-fb-state-fb.patch [1] All other patches automatically rebased. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.86&id=48bfb4b03c5ff6e1fa1dc73fb915e150b0968c40 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 6.1 to 6.1.84Hauke Mehrtens2024-04-14
| | | | | | | | | | | Removed upstreamed: pistachio/patches-6.1/110-pwm-img-fix-clock-lookup.patch [1] All other patches automatically rebased. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.84&id=44b6fb6cdedb2c391a2da355521d4610b2645fcc Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 6.1 to 6.1.83Hauke Mehrtens2024-04-14
| | | | | | | | | | | | | | | | | | | | Removed upstreamed: generic/backport-6.1/789-STABLE-01-net-dsa-mt7530-prevent-possible-incorrect-XTAL-frequ.patch [1] generic/backport-6.1/789-STABLE-02-net-dsa-mt7530-fix-link-local-frames-that-ingress-vl.patch [2] generic/backport-6.1/789-STABLE-03-net-dsa-mt7530-fix-handling-of-all-link-local-frames.patch [3] generic/pending-6.1/735-net-mediatek-mtk_eth_soc-release-MAC_MCR_FORCE_LINK-.patch [4] generic/pending-6.1/736-net-ethernet-mtk_eth_soc-fix-PPE-hanging-issue.patch [5] Manual adjusted the following patches: mediatek/patches-6.1/100-dts-update-mt7622-rfb1.patch 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.83&id=be4512b9ac6fc53e1ca8daccbda84f643215c547 2. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.83&id=f1fa919ea59655f73cb3972264e157b8831ba546 3. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.83&id=86c0c154a759f2af9612a04bdf29110f02dce956 4. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.83&id=6b62bad2da1b338f452a9380639fc9b093d75a25 5. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.83&id=f78807362828ad01db2a9ed005bf79501b620f27 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: Reorder generic kernel 6.1 configHauke Mehrtens2024-04-14
| | | | | | | | This reordering was done using these commands: ./scripts/kconfig.pl '+' target/linux/generic/config-6.1 /dev/null > target/linux/generic/config-6.1-new mv target/linux/generic/config-6.1-new target/linux/generic/config-6.1 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 6.6 to 6.6.27John Audia2024-04-14
| | | | | | | | | | | | | | | | | Changelog: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.27 Removed upstreamed: pending-6.6/981-gcc-plugins-stackleak-Avoid-.head.txt.section.patch[1] All patches automatically rebased. 1. https://github.com/gregkh/linux/commit/9dff96b8b3a404d3b3581af46450f2efeb7d290a Build system: x86/64 Build-tested: flogic/xiaomi_redmi-router-ax6000-ubootmod, ramips/tplink_archer-a6-v3, x86/64/AMD Cezanne Run-tested: flogic/xiaomi_redmi-router-ax6000-ubootmod, ramips/tplink_archer-a6-v3, x86/64/AMD Cezanne Signed-off-by: John Audia <therealgraysky@proton.me>
* x86: generic: config-6.6: refreshJohn Audia2024-04-14
| | | | | | | | | | Ran `make kernel_menuconfig` Reference to CONFIG_SPECTRE_BHI_ON=y[1] 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/arch/x86/Kconfig?id=v6.6.26&id2=v6.6.25 Signed-off-by: John Audia <therealgraysky@proton.me>
* kernel: bump 6.6 to 6.6.26John Audia2024-04-14
| | | | | | | | | | | | | | | | | | Changelog: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.26 Manually rebased: generic/hack-6.6/210-darwin_scripts_include.patch Added pending: generic/pending-6.6/981-gcc-plugins-stackleak-Avoid-.head.txt.section.patch All other patches automatically rebased. Build system: x86/64 Build-tested: x86/64/AMD Cezanne, flogic/xiaomi_redmi-router-ax6000-ubootmod, ramips/tplink_archer-a6-v3, flogic/glinet_gl-mt6000 Run-tested: x86/64/AMD Cezanne, flogic/xiaomi_redmi-router-ax6000-ubootmod, ramips/tplink_archer-a6-v3, flogic/glinet_gl-mt6000 Signed-off-by: John Audia <therealgraysky@proton.me>
* toolchain/musl: Update to 1.2.5Hannu Nyman2024-04-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Update musl C library to 1.2.5 This release adds extension functions statx and preadv2/pwritev2, with fallback implementations for older kernels, and adds two new ports: loongarch64 and riscv32. Minor changes to the printf family of functions have been made for conformance to new standards interpretations/requirements. TLSDESC support for riscv64 has also been added. Bugs fixed include some DNS issues related to new TCP fallback functionality, several rare race conditions, potentially incorrect return value when glob aborts, and several signifiant arch-specific bugs affecting TLSDESC on arm, riscv64 icache flushing, and sh sigsetjmp and dlsym RTLD_NEXT. 1.2.5 release notes: new features: - statx function (linux extension; via syscall and fallback using fstatat) - clone function is now usable and gives _Fork-like consistency in child - statvfs now provides f_type result - preadv2 and pwritev2 (linux extension) syscall wrappers - riscv64 TLSDESC support new ports: - loongarch64 - riscv32 compatibility: - DNS resolver can now handle answers with long CNAME chains - string.h no longer provides (C23-incompat) non-prototype decl of basename - fstatat statx backend now matches stat syscall non-automounting behavior - mntent interfaces now handle escaped whitespace in paths/options standards updates: - printf %lc of nul wchar now produces output - snprintf and swprintf no longer fail on n > INT_MAX - ppoll is now exposed in default feature profile bugs fixed: - some long DNS answers were wrongly rejected despite new TCP support - glob could wrongly return GLOB_NOMATCH if aborted before any matches - multithreaded set*id could malfunction from thread sequencing logic bug - certain use of threads after fork could deadlock thread-list lock - posix_spawn child could deadlock in race with async parent death - mbrtowc return value was wrong if argument n exceeded UINT_MAX - 80-bit extended acoshl and powl got some corner cases wrong - syslog incorrectly generated localized timestamps arch-specific bugs fixed: - arm (32-bit) TLSDESC malfunctioned due to addends being processed wrong - riscv64 icache flush operation was non-functional - sh sigsetjmp failed to properly restore call-saved register r8 on return - sh dlsym RTLD_NEXT did not identify calling module correctly Signed-off-by: Hannu Nyman <hannu.nyman@iki.fi> [Removed patch adding basename hack again] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* elfutils: update to 1.91Tony Ambardar2024-04-14
| | | | | | | | | | Release Notes: https://sourceware.org/pipermail/elfutils-devel/2024q1/006876.html Refresh patch: - 005-build_only_libs.patch Signed-off-by: Tony Ambardar <itugrok@yahoo.com>
* netifd: rewrite packet steering scriptFelix Fietkau2024-04-14
| | | | | | | | | | | The new script uses a different strategy compared to the previous one. Instead of trying to split flows by hash and spread them to all CPUs, use RPS to redirect packets to a single core only. Try to spread NAPI thread and RPS target CPUs across available CPUs and try to ensure that the NAPI thread is on a different CPU than the RPS target. This significantly reduces cycles wasted on the scheduler. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ipq40xx: whw03v2: change LED color for 'running' state to blueRodrigo Balerdi2024-04-13
| | | | | | | | | | | | | | | | | | | | Change the RGB indicator LED color for the running state from green to blue. There are various reasons for this change: - In stock firmware, green means internet connection is up, red means it is down, and blue means indeterminate. To track stock behavior as closely as possible, OpenWrt should indicate blue by default. - In the current 23.x OpenWrt releases for this router, the led glows blue all the time -not green- because the bootloader sets it blue and there is an OpenWrt bug that makes it unable to control the LED. The bug is fixed in master, so without this commit there would be an unexpected change of behavior for this device in the next release. - The ports other closely related Linksys devices (such as EA8300 and MR8300) get this right and use blue for the running state. Signed-off-by: Rodrigo Balerdi <lanchon@gmail.com>
* ipq40xx: whw03v2: fix handling of RGB LEDRodrigo Balerdi2024-04-13
| | | | | | | The RGB LED should glow green in the 'running' state, but it was glowing cyan because the blue component defaulted to 'on'. Signed-off-by: Rodrigo Balerdi <lanchon@gmail.com>
* mac80211: ath11k: support DT property to limit channelsRobert Marko2024-04-13
| | | | | | | | Limiting allowed channels per device may be required and is commonly supported on other drivers, so include a pending patch to add support for the same. Signed-off-by: Robert Marko <robimarko@gmail.com>
* mediatek: fix DTS defining mt7530 switch phys but not referencing themDaniel Golle2024-04-13
| | | | | | | | | | | | | | | | | | | | | | | | The upstream solution to define the MDIO bus in DT is a bit more strict than our previous downstream solution doing the same thing and now requires switch PHYs to be referenced in DT as well. Arınç Ünal told us in #15141: "With [the now upstream patch written by him which we backported], the switch MDIO bus won't be assigned to ds->user_mii_bus when the switch MDIO bus is defined on the device tree anymore. This was not the case with the downstream patch. When ds->user_mii_bus is populated, DSA will 1:1 map the port with PHY. Meaning port with address 1 will be mapped to PHY with address 1. Because that ds->user_mii_bus is not populated when the switch MDIO bus is defined on the device tree, on every port node, the PHY address must be supplied by the phy-handle property." Add those phy-handles to affected devices' DT. Fixes: 4354b34f6f ("generic: 6.6: sync mt7530 DSA driver with upstream") Fixes: 401a6ccfaf ("generic: 6.1: sync mt7530 DSA driver with upstream") Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* ramips: add support for TP-Link EC220-G5 v2Mieczyslaw Nalewaj2024-04-13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link EC220-G5 v2 is a dual band router with 4 GbE ports Advertised as AC1200 for its 867Mbps (2x2) 5GHz band and 300 Mbps (2x2) 2.4GHz band. Specs: - SoC: MediaTek MT7620A - Ethernet: 4x GbE ports (Realtek RTL8367S) - Wireless 2.4GHz: MediaTek MT7620A - Wireless 5GHz: MediaTek MT7612E - RAM: 64MiB - ROM: 8MiB (W25Q64BV) - 2 Buttons (WPS and reset) - 7 LEDs Flash instructions via serial console: 1. Rename the factory.bin to to test.bin 2. start a TFTP server from IP address 192.168.0.225 and serve the image named test.bin 3. connect your device to the LAN port 4. power up the router and press 4 on the console to stop the boot process. 5. enter the following commands on the router console tftp 0x80060000 test.bin erase tplink 0x20000 0x7a0000 cp.b 0x80060000 0x20000 0x7a0000 reset Flash instructions via TFTP: 1. Update orginal firmware of the router to the latest one. 2. Rename openwrt-ramips-mt7620-tplink_ec220-g5-v2-squashfs-tftp-recovery.bin to tp_recovery.bin 3. Change computer IP to 192.168.0.66 4. Run TFTP serwer 5. Start the router with the reset button pressed, the file will be automatically downloaded and after a while the router will restart. 6. After updating, set your computer's IP to DHCP Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* ramips: mt7620a_tplink_archer.dtsi rename to mt7620a_tplink_8m.dtsiMieczyslaw Nalewaj2024-04-13
| | | | | | Change the name mt7620a_tplink_archer.dtsi to mt7620a_tplink_8m.dtsi because it will also be a base for TP-Link non-Archer routers. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* ramips: TP-Link Archer C2 v1: simplification of the dts definitionMieczyslaw Nalewaj2024-04-13
| | | | | | Import from the mt7620a_tplink_archer.dtsi file and thus simplify the rest of the definition. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* ramips: mt7620a_tplink_archer.dtsi - remove unnecessary nvmem-cells definitionsMieczyslaw Nalewaj2024-04-13
| | | | | | Remove unnecessary nvmem-cells definitions that are being redefined anyway. Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* mac80211: improve mesh fast tx patchFelix Fietkau2024-04-13
| | | | | | | Change hash key struct size for faster lookup. Fix clearing cache entries for forwarding Signed-off-by: Felix Fietkau <nbd@nbd.name>
* hostapd: fix a crash corner caseFelix Fietkau2024-04-13
| | | | | | On some setup failures, iface->bss can be NULL Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uboot-d1: define default BUILD_SUBTARGETTianling Shen2024-04-13
| | | | | | | | | As commit 3ce1e4c3d3da ("d1: define subtarget specifically") added the 'generic' subtarget, without 'BUILD_SUBTARGET' the correspond U-Boot package will be no longer selected automatically. Fixes: 3ce1e4c3d3da ("d1: define subtarget specifically") Signed-off-by: Tianling Shen <cnsztl@immortalwrt.org>
* realtek: fix filter_port_list_reverse callsStijn Tintel2024-04-13
| | | | | | | | | | | | | | The function introduced in commit 7cbfe5654d6e is named filter_port_list_reverse, not filter_port_list_reversed. Fixes the following error on hpe,1920-8g-poe-65w and hpe,1920-8g-poe-180w. /bin/board_detect: /etc/board.d/02_network: line 84: filter_port_list_reversed: not found Fixes: 7cbfe5654d6e ("realtek: move port filtering out of uci_set_poe()") Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> Acked-by: Sander Vanheule <sander@svanheule.net>
* CI: labeler: add d1 targetRobert Marko2024-04-13
| | | | | | Add support for 'd1' target and its specific packages in labeler. Signed-off-by: Robert Marko <robimarko@gmail.com>
* bpftool: Update to v7.4.0Tony Ambardar2024-04-13
| | | | | | | | | | Update to the latest upstream release to include recent improvements and bugfixes. Update copyright, fix typo in PKG_NAME, and remove unneeded use of MAKE_VARS definition in Makefile. Drop 001-cflags.patch and simplify 002-includes.patch after refreshing. Also simplify LTO/DCE build flags. Link: https://github.com/libbpf/bpftool/releases/tag/v7.4.0 Signed-off-by: Tony Ambardar <itugrok@yahoo.com>
* libbpf: Update to v1.4.0Tony Ambardar2024-04-13
| | | | | | | | | | Update to the latest upstream release to include recent improvements and bugfixes, and update copyright. Remove MAKE_VARS usage in Makefile and drop 001-cflags.patch which are no longer needed. Also add flags to disable LTO, mistakenly dropped earlier. Link: https://github.com/libbpf/libbpf/releases/tag/v1.4.0 Signed-off-by: Tony Ambardar <itugrok@yahoo.com>
* build: use zstd for IB, toolchain, SDK and LLVM compressionPaul Spooren2024-04-13
| | | | | | Use similar efficient but faster compression algorithm. Signed-off-by: Paul Spooren <mail@aparcar.org>
* scripts/kernel_bump: Delete merge commitOlliver Schinagl2024-04-12
| | | | | | | | While we have included the needed changes via a merge commit, there is no need to keep it. Lets drop the merge commit, which we can do as we haven't pushed anything. Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
* scripts/kernel_bump: Allow bumping sub-targetsOlliver Schinagl2024-04-12
| | | | | | | Some targets may need to bump specific sub-targets only. So lets offer this as an option. Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
* scripts/kernel_bump: Use the git index to find the needed config filesOlliver Schinagl2024-04-12
| | | | | | | | | | | | The current solution using `find` introduces a racecondition, where `find` and `git mv` get in each others way. While this could be fixed with more-utils sponge command (or even sort -u) to buffer the output of find. However, a much better approach, is to query the git index directly, which will not change, and is far more accurate. Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
* scripts/kernel_bump: Use git to obtain the list of filesOlliver Schinagl2024-04-12
| | | | | | | Instead of looping of a directory to find directories related to kernel changes, use the git index instead. Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
* scripts/kernel_bump: Allow for migrating only configuration filesOlliver Schinagl2024-04-12
| | | | | | | | In some cases, we want to only migrate configuration files, e.g. if the kernel was bumped already. Lets add a flag for this case to offer flexibility. By default we will migrate configuration flags as before. Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
* scripts/kernel_bump: Run script relative to the script dirOlliver Schinagl2024-04-12
| | | | | | | | Determine the target directory based on the script location, which might work better in some cases, but at least also allows the script to be ran from with any location in the OpenWRT repository. Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
* scripts/kernel_bump: Do no run on dirty repositoriesOlliver Schinagl2024-04-12
| | | | | | We want to avoid starting a process when we know it will fail later. Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
* scripts/kernel_bump: Improve omitted version errorOlliver Schinagl2024-04-12
| | | | | | | | If a version string was not supplied, we currently print an empty string. We can do better here. Also by popular demand, print the usage information in case of error. Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
* scripts/kernel_bump: Always drop v prefixOlliver Schinagl2024-04-12
| | | | | | | | | Naivly and lazyly the leading v was only dropped from optarg, not from any environment variable. Lets do this properly and ensure a leading 'v' is always dropped. Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
* scripts/kernel_bump: Drop unused functionOlliver Schinagl2024-04-12
| | | | | | No need to keep unused empty functions. A left over from early development. Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
* scripts/kernel_bump: Avoid potential copyright claimOlliver Schinagl2024-04-12
| | | | | | | | | | | Due to potential fears of copyright infringement noted by Elliott Mitchell [0], rewrite our message to belong to OpenWRT. Note, AI was used to aid in construction of this sentence. [0]: https://lists.openwrt.org/pipermail/openwrt-devel/2024-March/042422.html Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
* mediatek: mt7622: rtl8367c: source code spell fixesPaul Donald2024-04-12
| | | | | | Improves indexing and searches Signed-off-by: Paul Donald <newtwen+github@gmail.com>
* mediatek: mt7622: rtl8367c: source comment fixesPaul Donald2024-04-12
| | | | | | | | Fix also some Chinese -> UTF8 encoding problems Improves indexing and searches Signed-off-by: Paul Donald <newtwen+github@gmail.com>
* mediatek: mt7622: rtl8367c: source comment fixesPaul Donald2024-04-12
| | | | | | | | | | | | | | | | | | | | | | | | Fix also some Chinese GB18030 -> UTF-8 encoding problems (translated the Chinese strings to English): 修改 -> modification port8~port10的设置在另外一个register -> port8~port10 setup is done in a separate register You are in the correct (UTF-8) encoding when you see: * $Date: 2017-03-08 15:13:58 +0800 (週三, 08 三月 2017) $ e.g. week 3, 08 third month, 2017 But not if you see: * $Date: 2017-03-08 15:13:58 +0800 (閫变笁, 08 涓夋湀 2017) $ rtl8367c/rtl8367c_asicdrv_lut.c should be read as UTF-8, despite having some earlier Chinese text lost to GB18030 encoding. Improves indexing and searches Signed-off-by: Paul Donald <newtwen+github@gmail.com>