aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* 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
| | | | | | Improves indexing and searches Signed-off-by: Paul Donald <newtwen+github@gmail.com>
* lldpd: make management address advertisement controllablePaul Donald2024-04-12
| | | | | | | | | | Defaults to off. Available from >= 0.7.15 These are sent in TLV Signed-off-by: Paul Donald <newtwen+github@gmail.com>
* lldpd: make capabilities advertisement controllablePaul Donald2024-04-12
| | | | | | | | | | Defaults to off. Only available from >= 1.0.15 These capabilities are sent in TLV. Signed-off-by: Paul Donald <newtwen+github@gmail.com>
* qualcommax: enhance smp_affinity (log, uci, syntax)Sean Khan2024-04-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1.) Changed logic of `set_affinity` to now use physical cores rather than knowing the bitmask. Rather than having to know a bitmask, users can provide a numerical instance of one or more CPU cores (numbered 0-63). This is done via function `cpus_to_bitmask`. Functions Added: a.) bitmask_to_cpus - Takes a bitmask of CPUs and returns a list of CPU numbers. (i.e. `bitmask_to_cpus "f"` -> 0,1,2,3) b.) cpus_to_bitmask - Takes a comma/space or range list of CPUs and returns a bitmask. Example: `cpus_to_bitmask "2,3"` -> c `cpus_to_bitmask "0,1,2,3"` -> f `cpus_to_bitmask "1,3"` -> a With or without quotes `cpus_to_bitmask "1 3"` -> a `cpus_to_bitmask 1 3` -> a 2.) Added UCI options: enable - to enable/disable the script from running. [default 1 (on)] enable_log - to enable/disable logging output to `logger`.[default 1 (on)] Log output: ``` Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(87) reo2host-destination-ring1 to CPU 0 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(88) reo2host-destination-ring2 to CPU 1 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(89) reo2host-destination-ring3 to CPU 2 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(90) reo2host-destination-ring4 to CPU 3 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(79) wbm2host-tx-completions-ring1 to CPU 1 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(83) wbm2host-tx-completions-ring2 to CPU 2 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(85) wbm2host-tx-completions-ring3 to CPU 3 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(73) ppdu-end-interrupts-mac1 to CPU 1 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(77) ppdu-end-interrupts-mac2 to CPU 2 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(75) ppdu-end-interrupts-mac3 to CPU 3 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(32) edma_txcmpl to CPU 3 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(33) edma_rxfill to CPU 3 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(35) edma_rxdesc to CPU 3 Mon Apr 8 23:00:01 2024 user.notice smp_affinity: Pinning IRQ(36) edma_misc to CPU 3 ``` Output of `/proc/interrupts`: ``` 69: 0 0 0 0 GIC-0 209 Edge rxdma2host-destination-ring-mac1 70: 0 0 0 0 GIC-0 211 Edge rxdma2host-destination-ring-mac3 71: 0 0 0 0 GIC-0 210 Edge rxdma2host-destination-ring-mac2 72: 2435 0 0 0 GIC-0 321 Edge reo2host-status 73: 268427 8011 0 0 GIC-0 261 Edge ppdu-end-interrupts-mac1 74: 2 0 0 0 GIC-0 255 Edge rxdma2host-monitor-status-ring-mac1 75: 176169 0 4 10035 GIC-0 263 Edge ppdu-end-interrupts-mac3 76: 2 0 0 0 GIC-0 260 Edge rxdma2host-monitor-status-ring-mac3 77: 0 0 0 0 GIC-0 262 Edge ppdu-end-interrupts-mac2 78: 0 0 0 0 GIC-0 256 Edge rxdma2host-monitor-status-ring-mac2 79: 3428 3123 0 0 GIC-0 189 Edge wbm2host-tx-completions-ring1 80: 0 0 0 0 GIC-0 323 Edge reo2ost-exception 81: 178 0 0 0 GIC-0 322 Edge wbm2host-rx-release 82: 0 0 0 0 GIC-0 212 Edge host2rxdma-host-buf-ring-mac1 83: 6524 0 13712 0 GIC-0 190 Edge wbm2host-tx-completions-ring2 84: 4 0 0 0 GIC-0 235 Edge host2rxdma-host-buf-ring-mac3 85: 560 0 0 1979 GIC-0 191 Edge wbm2host-tx-completions-ring3 86: 0 0 0 0 GIC-0 215 Edge host2rxdma-host-buf-ring-mac2 87: 4520 0 0 0 GIC-0 267 Edge reo2host-destination-ring1 88: 2231 2811 0 0 GIC-0 268 Edge reo2host-destination-ring2 89: 2180 0 2512 0 GIC-0 271 Edge reo2host-destination-ring3 90: 1990 0 0 2321 GIC-0 320 Edge reo2host-destination-ring4 ``` 3.) Added `uci-defaults` script `15_smp_affinity` to configure defaults options on first boot. Signed-off-by: Sean Khan <datapronix@protonmail.com>
* lldpd: note about capabilitiesPaul Donald2024-04-12
| | | | | | | | | only available from >= 1.0.15 Comments are useful. Apparently this config parameter was committed when openwrt used an older version of lldpd which did not yet support it. Signed-off-by: Paul Donald <newtwen+github@gmail.com>
* lldpd: fix restartPaul Donald2024-04-12
| | | | | | | | | | | | | | | | | | | Redirection broke in 5364fe0f01ca ("lldpd: shellcheck fixes") redirects to /dev/null shall be handled correctly (i.e. last). This fixes these errors on `/etc/init.d/lldpd reload`: 2024-03-16T20:39:00 [WARN/lldpctl] unknown command from argument 1: `/dev/null` 2024-03-16T20:39:00 [WARN/lldpctl] unknown command from argument 1: `/dev/null` 2024-03-16T20:39:00 [WARN/lldpctl] unknown command from argument 1: `/dev/null` 2024-03-16T20:39:00 [WARN/lldpctl] unknown command from argument 1: `/dev/null` Tested-on: 22.03.6 Fixes: 5364fe0f01ca ("lldpd: shellcheck fixes") Signed-off-by: Paul Donald <newtwen+github@gmail.com> [ improve commit description, add fixes tag ] Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* package: kernel: leds-gca230718: fix build with Linux 6.6Daniel Golle2024-04-12
| | | | | | | | | | | Starting with Linux 6.3 the .probe call no longer got the id parameter, see also commit torvalds/linux@03c835f498b5 ("i2c: Switch .probe() to not take an id parameter"). As the parameter is anyway unused by the driver, drop it when building the GCA230718 LED driver for newer kernels. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* qualcommax: drop 6.1 supportRobert Marko2024-04-11
| | | | | | | We have defaulted to 6.6 for a while so its time to completely drop 6.1 so new devices dont have to include patches for 6.1. Signed-off-by: Robert Marko <robimarko@gmail.com>
* mediatek: filogic: add support for Edgecore EAP111Robert Marko2024-04-11
| | | | | | | | | | | | | | | | | | | HW specifications: * Mediatek MT7981A * 256MB SPI-NAND * 512MB DRAM * Uplink: 1 x 10/100/1000Base-T Ethernet, Auto MDIX, RJ-45 with 802.3at PoE (Built-in GBe PHY) * LAN: 1 x 10/100/1000Base-T Ethernet, Auto MDIX, RJ-45 (Airoha EN8801SC) * 1 Tricolor LED * Reset button * 12V/2.0A DC input Installation: Board comes with OpenWifi/TIP which is OpenWrt based, so sysupgrade can be used directly over SSH. Signed-off-by: Robert Marko <robert.marko@sartura.hr>
* mediatek: add Airoha EN8801SC PHY driverRobert Marko2024-04-11
| | | | | | | | | | | Airoha EN8801SC PHY is a gigabit PHY used on Edgecore EAP111 so, include the MTK driver with some cleanups. Unfortunatelly, there is no specification sheet nor datasheet available in order to demistify the magic PBUS writes and work on upstreaming this driver. Signed-off-by: Robert Marko <robert.marko@sartura.hr>
* generic: 6.1, 6.6: import two pending patches for mt7530 DSA driverDaniel Golle2024-04-10
| | | | | | | | | | | | | | | | First patch allows to inquire and modify Energy-Efficient-Ethernet (EEE) settings via ethtool and thereby override the default setting of a board done via bootstrap pins. The second patch fixes a long-standing issue with STP (and similar protocols) when using boards (or SoCs) governed by the mt7530 DSA driver. Both patches could also be (dirty-)applied to Linux 5.15, but I'd rather just wait for that to happen via linux-stable to avoid the mess. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* generic: 6.6: sync mt7530 DSA driver with upstreamDaniel Golle2024-04-10
| | | | | | | | | | | | | | | | | Backport lots upstream changes, many of them fixes, for the mt7530 DSA driver, similar to how it was done for Linux 6.1 in the previous commit. The remaining differences compared to the upstream driver are only the 'slave' -> 'user', 'master' -> 'conduit' language change in DSA and the rename of 'struct ethtool_eee' to 'struct ethtool_keee' as well as tree-wide replacement of ethtool_sprintf with ethtool_puts, all of them do not have any functional impact. Apart from some minor bug fixes and style improvements the switch should now behave more conformant when it comes to link-local frames, and we will again be able to cleanly pick patches from upstream. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* generic: 6.1: sync mt7530 DSA driver with upstreamDaniel Golle2024-04-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Backport lots upstream changes, many of them fixes, for the mt7530 DSA driver. Some of them may or may not find they way into Linux 6.1 stable, some certainly won't because they are fixes for backported commits which aren't even present in Linux 6.1 upstream. Apart from adding new patches, also remove mutated patch 723-net-mt7531-ensure-all-MACs-are-powered-down-before-r.patch which should never have been added for Linux 6.1 -- it was applied already upstream but coincidentally would fuzzy-apply in the wrong place as well (for MT7530 instead of MT7531). While that didn't really hurt anyone it is just unneeded. The other deleted patch 795-mt7530-register-OF-node-for-internal-MDIO-bus.patch has been replaced by an equivalent commit with a more complete patch description by upstream maintainer Arınç Ünal. The remaining differences compared to the upstream driver are: * C22/C45 MDIO ops aren't split Upstream did that, backporting it would require making changes to *all* DSA drivers * 'slave' -> 'user', 'master' -> 'conduit' language change in DSA * support for selecting preferred CPU port on MT7531 Also this would require too many DSA framework changes potentially affecting other devices. If we ever really use Linux 6.1 in a release (I hope not) we can still reconsider to make the effort to backport that. In addition to some minor bug fixes and style improvements the switch should now behave more conformant when it comes to link-local frames, and we will again be able to cleanly pick patches from upstream. MAINTAIERS NOTE: Three patches are already part of Linux stable and should be removed with the next minor kernel version bump: 789-STABLE-01-net-dsa-mt7530-prevent-possible-incorrect-XTAL-frequ.patch 789-STABLE-02-net-dsa-mt7530-fix-link-local-frames-that-ingress-vl.patch 789-STABLE-03-net-dsa-mt7530-fix-handling-of-all-link-local-frames.patch Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: add kmod-hwmon-emc2305 supportOleg S2024-04-10
| | | | | | | This module supports the Microchip Technology Inc (SMSC) EMC2301/EMC2302/EMC2303/EMC2305 fan speed PWM controller chips. Signed-off-by: Oleg S <remittor@gmail.com>
* ucode: update to Git HEAD (2024-04-07)Felix Fietkau2024-04-09
| | | | | | | | | | 1220992631d5 ubus: automatically clear error information d6fd94014eea uci: automatically clear error information 99837f280b61 uloop: automatically clear error information be767ae197ba vm: rework `in` operator semantics 4ade84e8fb81 ubus: add explicit support for deferring incoming requests Signed-off-by: Felix Fietkau <nbd@nbd.name>
* config: fix CONFIG_GDB appearing in main menuconfig menuRobert Marko2024-04-09
| | | | | | | | | | | | | | | I noticed that CONFIG_GDB was suddenly appearing in the main menuconfig menu despite the fact that it should be visible only when TOOLCHAINOPTS is selected and under a dedicated menu. After some trial and error, it seems that this was caused by the recent addition of GCC_USE_DEFAULT_VERSION, and after even more trial and error it gets fixed as soon GCC_USE_DEFAULT_VERSION is placed after GCC_VERSION. So, lets simply put GCC_USE_DEFAULT_VERSION after GCC_VERSION. Fixes: 501ef81040ba ("config: select KERNEL_WERROR if building with default GCC version") Signed-off-by: Robert Marko <robimarko@gmail.com>
* generic: add missing patch headersDaniel Golle2024-04-09
| | | | | | | Make sure all patches can be applied to a git tree using 'git am' by adding missing patch headers where needed. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* tools: zstd: dont override CLI max levelRobert Marko2024-04-09
| | | | | | | | Now that instead of relying on env variables for the GH download script invoking ZSTD tarball compression it passes the full arguments via tar -I we can drop the CLI max compression level override. Signed-off-by: Robert Marko <robimarko@gmail.com>
* scripts/dl_github_archive: use tar -I for ZSTDRobert Marko2024-04-09
| | | | | | | | | | | Instead of relying on env variables for setting the ZSTD compression configuration we can simply do what we do for IB, SDK and the rest and use tar -I to pass "zstd -T0 --ultra -20" directly. This makes it rather clear what is being done and allows to drop the zstd CLI max level override as its usually capped at level 19. Signed-off-by: Robert Marko <robimarko@gmail.com>
* mediatek: filogic: switch TP-LINK XDR series to fitblkDaniel Golle2024-04-09
| | | | | | | Instead of using the deprecated FIT partition parser, use the new fitblk driver instead. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mvebu: puzzle-m90x: wipe rootfs_data on sysupgradeDaniel Golle2024-04-09
| | | | | | | | | | | | | | | | | | | The sysupgrade formware of the Puzzle series is a slightly strange dual-boot approach while remaining compatible with Marvell's SDK firmware upgrade binary format -- which happens to be a full-disk image with GPT partition table. Hence that /lib/upgrade/emmc-puzzle.sh script is like an exotic disease which results from those decisions, and as we also want to somehow stay compatible with the IEI-World stock firmware we got to use it in that same way (we are not compatible with the QNAP-branded identical hardware device anyway). Currently, on sysupgrade the result is that one ends up with the old content of rootfs_data (a GPT partition on those devices) as nothing ever wipes or in any way re-creates the filesystem there. As a simple work-around, let's kill the filesystem on rootfs_data so fstools re-formats it on the next boot. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* sdk: include lib/crtsavres.o for powerpcRobert Marko2024-04-09
| | | | | | | | | | | | | | | | | | | | Trying to link certain kernel modules like dahdi-linux when building with the OpenWrt SDK will fail with: openwrt-sdk-apm821xx-sata_gcc-13.2.0_musl.Linux-x86_64/staging_dir/toolchain-powerpc_464fp_gcc-13.2.0_musl/bin/powerpc-openwrt-linux-musl-ld: cannot find arch/powerpc/lib/crtsavres.o: No such file or directory Previously this worked with the PowerPC SDK since we carried a hack that was passing --save-restore-funcs to module LDFLAGS so the linker provided the required functions automatically as without --save-restore-funcs it doesnt do so automatically on relocatable links and as a sideffect did not require the kernel provided crtsaves.o to link against. Now that hack has been removed as upstream kernel now compiles crtsaves.o by default so it can be linked against but its not included in the SDK. So, lets include lib/crtsavres.o when SDK is generated for PowerPC. Fixes: 99c9d8abd677 ("kernel: bump 5.15 to 5.15.148") Signed-off-by: Robert Marko <robimarko@gmail.com>
* qualcommax: Skip compiling unnecessary dtbsSean Khan2024-04-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently the compile phase of the kernel builds `Image dtbs modules`. However, none of the dtbs that get built are used for the final image. This ends up unnecessarily taking CPU cycles and produces a lot of `WARNINGS` that can lead users to believe there's cause for concern. I believe the same principle can be applied to other targets. ``` DTC arch/arm64/boot/dts/qcom/msm8996-mtp.dtb arch/arm64/boot/dts/qcom/msm8996.dtsi:2954.36-2962.5: Warning (clocks_property): /soc/clock-controller@6400000: Missing property '#clock-cells' in node /soc/mailbox@9820000 or bad phandle (referred from clocks[2]) DTC arch/arm64/boot/dts/qcom/msm8996-sony-xperia-tone-dora.dtb arch/arm64/boot/dts/qcom/msm8996.dtsi:2954.36-2962.5: Warning (clocks_property): /soc/clock-controller@6400000: Missing property '#clock-cells' in node /soc/mailbox@9820000 or bad phandle (referred from clocks[2]) DTC arch/arm64/boot/dts/qcom/msm8996-sony-xperia-tone-kagura.dtb arch/arm64/boot/dts/qcom/msm8996.dtsi:2954.36-2962.5: Warning (clocks_property): /soc/clock-controller@6400000: Missing property '#clock-cells' in node /soc/mailbox@9820000 or bad phandle (referred from clocks[2]) DTC arch/arm64/boot/dts/qcom/msm8996-sony-xperia-tone-keyaki.dtb arch/arm64/boot/dts/qcom/msm8996.dtsi:2954.36-2962.5: Warning (clocks_property): /soc/clock-controller@6400000: Missing property '#clock-cells' in node /soc/mailbox@9820000 or bad phandle (referred from clocks[2]) DTC arch/arm64/boot/dts/qcom/msm8996-xiaomi-gemini.dtb arch/arm64/boot/dts/qcom/msm8996.dtsi:2954.36-2962.5: Warning (clocks_property): /soc/clock-controller@6400000: Missing property '#clock-cells' in node /soc/mailbox@9820000 or bad phandle (referred from clocks[2]) DTC arch/arm64/boot/dts/qcom/msm8996-xiaomi-natrium.dtb arch/arm64/boot/dts/qcom/msm8996.dtsi:2954.36-2962.5: Warning (clocks_property): /soc/clock-controller@6400000: Missing property '#clock-cells' in node /soc/mailbox@9820000 or bad phandle (referred from clocks[2]) DTC arch/arm64/boot/dts/qcom/msm8996-xiaomi-scorpio.dtb arch/arm64/boot/dts/qcom/msm8996.dtsi:2954.36-2962.5: Warning (clocks_property): /soc/clock-controller@6400000: Missing property '#clock-cells' in node /soc/mailbox@9820000 or bad phandle (referred from clocks[2]) ``` Signed-off-by: Sean Khan <datapronix@protonmail.com>
* treewide: remove implicit SUBTARGETPaul Spooren2024-04-08
| | | | | | | | | | | | | | | | | | Historically it's possible to leave the `SUBTARGETS` undefined and automatically fallback to a "generic" subtarget. This however breaks various downstream scripts which may have expectations around filenames: While some targets with an explicit generic subtarget contain `generic` in the filenames of artifacts, implicit "subtargets" don't. Right now this breaks the CI[1], possibly also scripts using the ImageBuilders. This commit removes all code that support implicit handling of subtargets and instead requires every target to define "SUBTARGETS". [1]: https://github.com/openwrt/openwrt/actions/runs/8592821105/job/23548273630 Signed-off-by: Paul Spooren <mail@aparcar.org>
* d1: define subtarget specificallyPaul Spooren2024-04-08
| | | | | | | | | | | | | | | | | | Historically it's possible to leave the `SUBTARGETS` undefined and automatically fallback to a "generic" subtarget. This however breaks various downstream scripts which may have expectations around filenames: While some targets with an explicit generic subtarget contain `generic` in the filenames of artifacts, implicit "subtargets" don't. Right now this breaks the CI[1], possibly also scripts using the ImageBuilders. Do to the D1 target what's done to other target, explicitly define the "generic" subtarget. [1]: https://github.com/openwrt/openwrt/actions/runs/8592821105/job/23548273630 Signed-off-by: Paul Spooren <mail@aparcar.org>
* realtek: add support for switch Zyxel GS1900-24EPMirko Vogt2024-04-08
| | | | | | | | | | | This device is very similar to the GS1900-24E switch (added in b515ad1), except that the first 12 of 24 ethernet ports are capable of PoE and the physical jacks are in the right order - unlike for the GS1900-24E, where even and uneven ports are flipped (up <-> down on panel). Zyxel version code for this device (-24EP) is: ABTO Signed-off-by: Mirko Vogt <mirko-openwrt@nanl.de>
* config: select KERNEL_WERROR if building with default GCC versionDaniel Golle2024-04-08
| | | | | | | | | | | | | | | | At the moment we have to manually follow the default GCC version also in config/Config-kernel.in. This tends to be forgotten at GCC version bumps (just happened when switching from version 12 to 13). Instead, introduce a hidden Kconfig symbol which implies KERNEL_WERROR in toolchain/gcc/Config.in where it is visible for developers changing the default version. Also remove the explicit default on BUILDBOT to avoid a circular dependency and also because buildbots anyway implicitly always select the default GCC version. Reference: https://github.com/openwrt/openwrt/pull/15064 Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* uclient: update to Git HEAD (2024-04-05)Felix Fietkau2024-04-07
| | | | | | | | | | | | | | e209a4ced1d8 add strdupa macro for compatibility af1962b9a609 uclient: add helper function for getting ustream-ssl context/ops 488f1d52cfd2 http: add helper function for checking redirect status b6e5548a3ecc uclient: defer read notifications to uloop timer 352fb3eeb408 http: call ustream_poll if not enough read data is available e611e6d0ff0b add ucode binding ddb18d265757 uclient: add function for getting the amount of pending read/write data 980220ad1762 ucode: fix a few ucode binding issues 6c16331e4bf5 ucode: add support for using a prototype for cb, pass it to callbacks Signed-off-by: Felix Fietkau <nbd@nbd.name>
* bcm27xx: bcm2712: backport RP1 interrupt affinityÁlvaro Fernández Rojas2024-04-07
| | | | | | Support for setting the CPU affinity on RP1 has been added to RPi linux v6.6 Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: update 6.1 patches from RPi foundationÁlvaro Fernández Rojas2024-04-07
| | | | | | | | Sync 6.1 patches with the RPi foundation. Since rpi-6.6.y is now the main branch of the RPi foundation, there won't be any new patches for linux 6.1. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* base-files: minor fix to mmc_get_mac_ascii functionRodrigo Balerdi2024-04-07
| | | | | | | This is mostly a cosmetic cleanup. The absence of the return statement was not causing any problems. Signed-off-by: Rodrigo Balerdi <lanchon@gmail.com>
* ustream-ssl: update to Git HEAD (2024-04-07)Felix Fietkau2024-04-07
| | | | | | | | | | | 7621339d7694 mbedtls: fix build on non-linux systems 268050964b08 ustream-mbedtls: add missing psa_crypto_init call 956fba242ac0 add callbacks for debug messages 9fdf3fb87af5 mbedtls: add TLS 1.3 ciphers 28c4c1e6471b mbedtls: disable TLS 1.3 in client mode when skipping verification d61493a44204 mbedtls: add missing ifdef for build with disabled debug Signed-off-by: Felix Fietkau <nbd@nbd.name>
* at91bootstrap: update PKG_MIRROR_HASH to zstd for v3 at91bootstrapRobert Marko2024-04-07
| | | | | | | | | | | | So, when updating the hash for at91bootstrap it was done via CHECK_ALL=1 so that updated the PKG_MIRROR_HASH for the main v4 version hash, but at91bootstrap checkout version depends on the subtarget as well. Choosing to build for sam9x will change the at91bootstrap version to v3 and this hash was not refreshed thus causing the CI to fail. Fixes: 6918c637b797 ("treewide: package: update missed hashes after switch to ZSTD") Signed-off-by: Robert Marko <robimarko@gmail.com>
* generic: backport at803x kernel panic fixChristian Marangi2024-04-07
| | | | | | Backport at803x kernel panic fix merged upstream for kernel 6.1 and 6.6. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* treewide: package: update missed hashes after switch to ZSTDRobert Marko2024-04-07
| | | | | | | | With the switch to ZSTD for git clone packaging, hashes have changed so fixup remaining package hashes that were missed in the inital update. Fixes: b3c1c57 ("treewide: update PKG_MIRROR_HASH to zst") Signed-off-by: Robert Marko <robimarko@gmail.com>
* generic: 6.6: backport arm64 swiotlb default size reductionRobert Marko2024-04-07
| | | | | | | | | | | | | | Kernel 6.6 added dynamic SWIOTLB allocation, but with it also started allocating 64MB of the SWIOTLB bounce buffer by default which is quite a lot of memory on most OpenWrt devices. Luckily in kernel 6.7 arm64 received an optimization that reduces that default size to 1MB per 1GB of RAM if certain criteria was met. So in order to reclaim back 63MB of RAM which brought some ipq807x devices close to OOM under load lets backport the upstream commit. Signed-off-by: Robert Marko <robimarko@gmail.com>
* nu801: update PKG_MIRROR_HASH to zstRobert Marko2024-04-07
| | | | | | | | When using zst instead of xz, the hash changes. This was missed in the initial treewide updated. Fixes: b3c1c57a35a0 ("treewide: update PKG_MIRROR_HASH to zst") Signed-off-by: Robert Marko <robimarko@gmail.com>
* x86: geode: 6.6: add missing kernel optionsMieczyslaw Nalewaj2024-04-07
| | | | | | | Add options removed by `make kernel_oldconfig CONFIG_TARGET=subtarget', missing which causes compilation to stop and cause an error. Fixes: 2a86425de107 ("x86: 6.6: refresh kernel config") Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
* wifi-scripts: fix creation of IBSS in legacy (non-HT) modeAlexandru Gagniuc2024-04-07
| | | | | | | | | | | | | | | | | | | | | When an IBBS interface is configured for IBSS legacy mode, wdev.htmode is empty. This is empty string results in an empty positional argument to the "ibbs join" command, for example: iw dev phy0-ibss0 ibss join crymesh 2412 '' fixed-freq beacon-interval 100 This empty argument is interpreted as an invalid HT mode by 'iw', causing the entire command to fail and print a "usage" message: daemon.notice netifd: radio0 (4527): Usage: iw [options] \ dev <devname> ibss join <SSID> <freq in MHz> ... Although nobody will ever need more than 640K of IBSS, explicitly use "NOHT" if an HT mode is not given. This fixes the problem. Fixes: e56c5f7b276a ("hostapd: add ucode support, use ucode for the main ubus object") Signed-off-by: Alexandru Gagniuc <mr.nuke.me@gmail.com> Signed-off-by: Felix Fietkau <nbd@nbd.name> [extend to cover more cases]
* scripts: add .tar.zst to dl_cleanup extensionsStijn Tintel2024-04-06
| | | | Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* tools: zstd: add patch fixing wrong generated .pc with lib-mtChristian Marangi2024-04-06
| | | | | | | | | | | | | The current .pc generated by make build system for zstd is wrong and always assume a single-threaded library is used. This wasn't the case for the meson build system that used his own logic to generate the pkg-config file. Add a patch to fix this by introducing install-mt-pc make target to generate the correct pkg-config gile. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* Revert "tools/mkimage: update to v2024.04"Nick Hainke2024-04-06
| | | | | | | | | | | This reverts commit 8d934c11968de49ad17bc62366a88230e47b4f56. The update seems to be causing issues that need to be further explored [0]. Let's revert it. [0] - https://github.com/openwrt/openwrt/pull/15078 Signed-off-by: Nick Hainke <vincent@systemli.org>
* tools: zstd: install headers as wellRobert Marko2024-04-06
| | | | | | | | We forgot to make sure install-includes is called for the libzstd in order for it to install the required headers. Fixes: 4b920e799fba ("tools: zstd: convert to make and drop meson dependency") Signed-off-by: Robert Marko <robimarko@gmail.com>
* treewide: update PKG_MIRROR_HASH to zstPaul Spooren2024-04-06
| | | | | | | When using zst instead of xz, the hash changes. This commit fixes the hash for packages and tools in core. Signed-off-by: Paul Spooren <mail@aparcar.org>
* tools: prefer gz or bz2 tarballsRobert Marko2024-04-06
| | | | | | | | | | | | | | In the light of recent XZ events, and fundamental XZ issues lets work on moving away from using XZ. So, use gz compressed tarballs as sources whenever possible. dwarves only offers bz2 compressed tarballs, so use those as size difference is minor compared to XZ. Signed-off-by: Robert Marko <robimarko@gmail.com> dwarves
* tools: libdeflate: fetch source as tarballRobert Marko2024-04-06
| | | | | | | | | | | | | libdeflate is currently intentionally being fetched via GIT. However, with the move to using ZSTD to compress the cloned GIT repo tarballs it means that we would first need to compile ZSTD. But that means that we need to be able to unpack gzipped tarballs first which we currently do by using libdeflate-gzip. So, in order to do so lets fetch libdeflate as a tarball, use gzip to extract it and then use libdeflate as regular for all other tools. Signed-off-by: Robert Marko <robimarko@gmail.com>
* tools: rework tools-core dependeciesRosen Penev2024-04-06
| | | | | | | | | | | | ZSTD and libdeflate do not depend on SED nor flock, so instead of the whole for loop that will filter 2 out of 4 core packages just specify that patch and tar depend on sed explicitly. ZSTD now depends on libdeflate since libdeflate-gzip will then be used to unpack ZSTD as well as most tool archives. Signed-off-by: Rosen Penev <rosenp@gmail.com> Signed-off-by: Robert Marko <robimarko@gmail.com>
* tools: make zstd tool core and xz tool non-coreChristian Marangi2024-04-06
| | | | | | | Make zstd tool core and xz tool non-core since zstd is the new default for compression format. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* tools: zstd: dont override ZSTD_LEGACY_SUPPORTRobert Marko2024-04-06
| | | | | | | | We dont really have a reason to deviate from the upstream default for ZSTD_LEGACY_SUPPORT value of 5, as it will save a bit of space but prevent decompressing data compressed with legacy ZSTD versions. Signed-off-by: Robert Marko <robimarko@gmail.com>