aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* tools/libtool: fix hard-coded pathsSebastian Kemper2023-03-131-12/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | libtoolize hardcodes some paths. This is fine when building libtool and then using it (for example in OpenWrt's buildroot). But when using an SDK the paths are most likely different. For example, when building util-linux within an SDK we're greeted with the following message: libtoolize: error: $pkgauxdir is not a directory: '/path/to/openwrt/staging_dir/host/share/libtool/build-aux' This is because staging_dir/host/bin/libtoolize contains the following hard-coded paths from when the SDK was built in the first place: prefix="/path/to/openwrt/staging_dir/host" datadir="/path/to/openwrt/staging_dir/host/share" pkgauxdir="/path/to/openwrt/staging_dir/host/share/libtool/build-aux" pkgltdldir="/path/to/openwrt/staging_dir/host/share/libtool" aclocaldir="/path/to/openwrt/staging_dir/host/share/aclocal" This commits updates 000-relocatable.patch to correct the paths, relative to "$STAGING_DIR_HOST". Ref: 96e05e2e3 ("libtool: Revert "libtool: bump to 2.4.6"") Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net> [adapted to older libtool version before bumping, use STAGING_DIR_HOST] Signed-off-by: Michael Pratt <mcpratt@pm.me>
* tools/libtool: add commit messages to patchesMichael Pratt2023-03-136-0/+71
| | | | | | | | | | | | Add commit messages to patches as intended by the last bump to libtool which had to be reverted. This allows for a cleaner diff later, removing this clutter from the complex changes to patches that are required to bump to the latest libtool version. Ref: c377d874b ("libtool: bump to 2.4.6") Signed-off-by: Michael Pratt <mcpratt@pm.me>
* tools/libtool: refresh patchesMichael Pratt2023-03-133-11/+8
| | | | | | | | | Preparation for bumping libtool several versions at once, which includes some complex changes to patches. Remove an empty line change from a patch. Signed-off-by: Michael Pratt <mcpratt@pm.me>
* tools/automake: bump to 1.16.5Michael Pratt2023-03-133-65/+21
| | | | | | | | | | | | | | | | | | | | | Automake releases 1.16.2 to 1.16.5 are major releases, the two before are minor releases. The first patch needed rewriting, some lines moved to be consistent with the same change upstream in other files. This also simplifies the patch. Second patch refreshed. Links to changelogs in order, oldest to newest. Link: https://lists.gnu.org/archive/html/info-gnu/2018-02/msg00008.html Link: https://lists.gnu.org/archive/html/info-gnu/2018-03/msg00002.html Link: https://lists.gnu.org/archive/html/info-gnu/2020-03/msg00009.html Link: https://lists.gnu.org/archive/html/info-gnu/2020-11/msg00005.html Link: https://lists.gnu.org/archive/html/info-gnu/2021-07/msg00013.html Link: https://lists.gnu.org/archive/html/info-gnu/2021-10/msg00000.html Signed-off-by: Michael Pratt <mcpratt@pm.me>
* tools/autoconf: bump to 2.71Michael Pratt2023-03-134-128/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | Autoconf release 2.71 is a bugfix release of 2.70 Links provided are the changelog of 2.70 [1] [2] and the announcement of 2.71 [3] The first patch needed to be rewritten. Some of the lines in the patch were moved to be consistent with the same change added upstream in other similar files. Second and third patches are no longer needed, Emacs can now be disabled at the configure stage, and support for musl was added upstream. The patch now causes help2man to be required for installing man pages, but we don't need them. There is no way to disable man pages build with the configure script, so use make to touch the files with the build target install-man1. Link: https://lists.gnu.org/archive/html/autotools-announce/2020-12/msg00001.html Link: https://lwn.net/Articles/839395 Link: https://lists.gnu.org/archive/html/info-gnu/2021-01/msg00017.html Signed-off-by: Michael Pratt <mcpratt@pm.me>
* tools/autoconf-archive: bump to 2022.09.03Michael Pratt2023-03-131-2/+2
| | | | | | | | Changelog included in package. Link to announcement. Link: https://lists.gnu.org/archive/html/info-gnu/2022-09/msg00004.html Signed-off-by: Michael Pratt <mcpratt@pm.me>
* tools/automake: use make variable to generate aclocal symlinksMichael Pratt2023-03-131-5/+8
| | | | | | | | | | | | | Instead of having a somewhat random list of aclocal symlinks which are named with the API versioning scheme, install a symlink for every API version since 1.11 (the first release after Automake was moved to git) using the API version number from the version of automake that is currently in openwrt. Automake API versioning does not include the patch level number. Signed-off-by: Michael Pratt <mcpratt@pm.me>
* tools/automake: clean up build recipesMichael Pratt2023-03-131-4/+4
| | | | | | | | | | | | | | | | The configure option datarootdir defaults to PREFIX/share. The Host/Clean define should be Host/Uninstall otherwise it is removing the build directory before there is a chance to try "make uninstall" in that directory. Host/Clean/Default is no longer defined. Consolidate the install stage with Host/Uninstall, since it is essentially uninstalling before installing. Signed-off-by: Michael Pratt <mcpratt@pm.me>
* tools/autoconf: clean up build recipesMichael Pratt2023-03-131-12/+4
| | | | | | | | | | | | | | | | The configure option datarootdir defaults to PREFIX/share. The Host/Clean define should be Host/Uninstall otherwise it is removing the build directory before there is a chance to try "make uninstall" in that directory. Host/Clean/Default is no longer defined. Use default build recipes defined in host-build.mk instead of custom ones that are equivalent. Signed-off-by: Michael Pratt <mcpratt@pm.me>
* tools/autoconf-archive: clean up build recipesMichael Pratt2023-03-131-14/+2
| | | | | | | | | | | | | | | | The configure option datarootdir defaults to PREFIX/share. The Host/Clean define should be Host/Uninstall otherwise it is removing the build directory before there is a chance to try "make uninstall" in that directory. Host/Clean/Default is no longer defined. Use default build recipes defined in host-build.mk instead of custom ones that are equivalent. Signed-off-by: Michael Pratt <mcpratt@pm.me>
* build: disable automake dependency trackingMichael Pratt2023-03-132-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Recent versions of Automake have changed dependency tracking significantly (reference commit below) causing breakage in some package builds when using newer Automake with packages that need autoreconf that were bootstrapped with an old version of Automake. Those changes cause a great inconsistency between packages over time where some packages may or may not use this feature, and may or may not update the .ac and .am files to work with the new methods. This problem might exist in many packages where autoreconf is not currently required, but would cause build failure if autoreconf is used. Fortunately, this feature is practically useless for the purposes of Openwrt and the average developer, so we can disable it. GNU Automake manual states in part: "Because dependencies are only computed as a side-effect of compilation... no dependency information exists the first time a package is built... dependency tracking is completely useless for one-time builds..." A nice side-effect is that build times are slightly faster. Ref: 6a675ef17edf7109da189f5ae70e2dc6b7665896 (automake.git) Signed-off-by: Michael Pratt <mcpratt@pm.me>
* ath79: fix user LED glow on Mikrotik 911 Lite boardsLech Perczak2023-03-121-1/+1
| | | | | | | | | | GPIO3, to which the user LED is connected on RB911-Lite boards seems to still sink current, even when driven high. Enabling open drain for this pin fixes this behaviour and gets rid of the glow when LED is set to off, so enable it. Fixes: 43c7132bf8e7 ("ath79: add support for MikroTik RouterBOARD 911 Lite2/Lite5") Signed-off-by: Lech Perczak <lech.perczak@gmail.com>
* elfutils: update to 1.89Nick Hainke2023-03-122-4/+6
| | | | | | | | | | Release Notes: https://sourceware.org/pipermail/elfutils-devel/2023q1/006023.html Refresh patch: - 003-libintl-compatibility.patch Signed-off-by: Nick Hainke <vincent@systemli.org>
* tools/elfutils: update to 1.89Nick Hainke2023-03-121-2/+2
| | | | | | | Release Notes: https://sourceware.org/pipermail/elfutils-devel/2023q1/006023.html Signed-off-by: Nick Hainke <vincent@systemli.org>
* strace: update to 6.2Nick Hainke2023-03-101-2/+2
| | | | | | | Release Notes: https://github.com/strace/strace/releases/tag/v6.2 Signed-off-by: Nick Hainke <vincent@systemli.org>
* ath79: refactor devolo WiFi pro image definitionsDavid Bauer2023-03-101-18/+11
| | | | | | | | Reuse common parts for the devolo WiFi pro series. The series is discontinued and we support all existing devices, so changes due to new revisions or models are highly unlikely Signed-off-by: David Bauer <mail@david-bauer.net>
* kernel: modules: add missing kmod-mdio-devres for lan743xHauke Mehrtens2023-03-101-1/+1
| | | | | | | This fixes a build problem on some targets. Fixes: 3e9005546a ("kernel: modules: package Microchip LAN743x PCIe gigE driver") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* binutils: Deactivate msgpackHauke Mehrtens2023-03-091-0/+1
| | | | | | | | | | | | Deactivate the msgpack option. The binutils build might detect the libmsgpackc.so.2 library and will try to link against it, if it is not explicitly deactivated. This prevents the following build errors seen in the build bots. Package binutils is missing dependencies for the following libraries: libmsgpackc.so.2 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* bmips: dts: fix warningsÁlvaro Fernández Rojas2023-03-097-2/+22
| | | | | | | | - Add missing interrupt-parent to ext_intc. - Add missing #address-cells and #size-cells to gpio_cntl. - Use proper gpio handle for gpios (ar-5315u). Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: modules: add missing kmod-ptp for lan743xChuanhong Guo2023-03-091-1/+1
| | | | | Fixes: 3e9005546a ("kernel: modules: package Microchip LAN743x PCIe gigE driver") Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* kernel: modules: package Microchip LAN743x PCIe gigE driverTim Harvey2023-03-081-0/+16
| | | | | | Package the Microchip LAN743x PCIe gigE driver Signed-off-by: Tim Harvey <tharvey@gateworks.com>
* mvebu: add support for Fortinet FortiGate 50EINAGAKI Hiroshi2023-03-086-0/+588
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fortinet FortiGate 50E (FG-50E) is a UTM, based on Armada 385 (88F6820). Specification: - SoC : Marvell Armada 385 88F6820 - RAM : DDR3 2 GiB (4x Micron MT41K512M8DA-107, "D9SGQ") - Flash : SPI-NOR 128 MiB (Macronix MX66L1G45GMI-10G) - Ethernet : 7x 10/100/1000 Mbps - LAN 1-5 : Marvell 88E6176 - WAN 1, 2 : Marvell 88E1512 (2x) - LEDs/Keys : 18x/1x - UART : "CONSOLE" port (RJ-45, RS-232C level) - port : ttyS0 - settings : 9600bps 8n1 - assignment : 1:NC , 2:NC , 3:TXD, 4:GND, 5:GND, 6:RXD, 7:NC , 8:NC - note : compatible with Cisco console cable - HW Monitoring: nuvoTon NCT7802Y - Power : 12 VDC, 2 A - plug : Molex 5557-02R Flash instruction using initramfs image: 1. Power on FG-50E and interrupt to show bootmenu 2. Call "[R]: Review TFTP parameters.", check TFTP parameters and connect computer to "Image download port" in the parameters 3. Prepare TFTP server with the parameters obtained above 4. Rename OpenWrt initramfs image to "image.out" and put to TFTP directory 5. Call "[T]: Initiate TFTP firmware transfer." to download initramfs image from TFTP server 6. Type "r" key when the following message is showed, to boot initramfs image without flashing to spi-nor flash "Save as Default firmware/Backup firmware/Run image without saving:[D/B/R]?" 7. On initramfs image, backup mtd if needed minimum: - "firmware-info" - "kernel" - "rootfs" 7. On initramfs image, upload sysupgrade image to the device and perform sysupgrade 8. Wait ~200 seconds to complete flashing and rebooting. If the device is booted with stock firmware, login to bootmenu and call "[B]: Boot with backup firmware and set as default." to set the first OS image as default and boot it. Notes: - All "SPEED" LEDs(Green/Amber) of LAN and 1000M "SPEED" LEDs(Green) of WAN1/2 are connected to GPIO expander. There is no way to indicate link speed of networking device on Linux Kernel/OpenWrt, so those LEDs cannot be handled like stock firmware. On OpenWrt, use netdev(link) trigger instead. - Both colors of Bi-color LEDs on the front panel cannot be turned on at the same time. - "PWR" and "Logo" LEDs are connected to power source directly. - The following partitions are added for OpenWrt. These partitions are contained in "uboot" partition (0x0-0x1fffff) on stock firmware. - "firmware-info" - "dtb" - "u-boot-env" - "board-info" Image header for bootmenu tftp: 0x0 - 0xf : ? 0x10 - 0x2f : Image Name 0x30 - 0x17f: ? 0x180 - 0x183: Kernel Offset* 0x184 - 0x187: Kernel Length* 0x188 - 0x18b: RootFS Offset (ext2)* 0x18c - 0x18f: RootFS Length (ext2)* 0x190 - 0x193: DTB Offset 0x194 - 0x197: DTB Length 0x198 - 0x19b: Data Offset (jffs2) 0x19c - 0x19f: Data Length (jffs2) 0x1a0 - 0x1ff: ? *: required for initramfs image MAC addresses: (eth0): 70:4C:A5:xx:xx:7C (board-info, 0xd880 (hex)) WAN 1 : 70:4C:A5:xx:xx:7D WAN 2 : 70:4C:A5:xx:xx:7E LAN 1 : 70:4C:A5:xx:xx:7F LAN 2 : 70:4C:A5:xx:xx:80 LAN 3 : 70:4C:A5:xx:xx:81 LAN 4 : 70:4C:A5:xx:xx:82 LAN 5 : 70:4C:A5:xx:xx:83 Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* ramips: add support for SNR-CPE-ME2-SFPAleksey Nasibulin2023-03-084-0/+236
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | SNR-CPE-ME2-SFP is a wireless router with SFP cage manufactured by SNR/NAG company. Specification: - SoC: MediaTek MT7621A - CPU: 880MHz - Flash: 16 MB (GD25Q127CSIG) - RAM: 256 MB - WLAN: 2.4 GHz, 5 GHz (MediaTek MT7615DN) - Ethernet: 4x 10/100/1000 Mbps - SFP cage (using RTL8211FS-CG) - USB 3.0 port - Power: 12 VDC, 2 A Flash instruction via TFTP: 1. Boot SNR-CPE-ME2 to recovery mode (press reset button and power on device, hold button for ~10 seconds) 2. Send firmware via TFTP client: TFTP Server address: 192.168.1.1 TFTP Client address: 192.168.1.131 3. Wait ~120 seconds to complete flashing 4. Do sysupgrade using web-interface MAC Addresses(stock) -------------------- +----------+------------------+-------------------+ | use | address | example | +----------+------------------+-------------------+ | Device | label | 6A:C4:DD:xx:xx:28 | | Ethernet | + 1 | 6A:C4:DD:xx:xx:29 | | 2g | + 2 | 6A:C4:DD:xx:xx:2A | | 5g | + 3 | 6A:C4:DD:xx:xx:2B | +----------+------------------+-------------------+ Notes: - Reading sfp eeprom is not supported [1] (driver issue). Stock image has the same situation. References: 1. https://forum.openwrt.org/t/mt7621-and-reading-sfp-eeprom/152249 Signed-off-by: Aleksey Nasibulin <alealexpro100@ya.ru>
* ipq40xx: convert Netgear EX6100/EX6150 v2 to DSADavid Bauer2023-03-083-5/+19
| | | | Signed-off-by: David Bauer <mail@david-bauer.net>
* kernel: Fix perf build with binutils 2.40Hauke Mehrtens2023-03-075-0/+550
| | | | | | | | | | Backport patches from kernel 6.0 which are fixing building of perf with binutils 2.40. perf with kernel 5.10 is also not building but the backporting is more complicated and only a few targets are still using kernel 5.10. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* qosify: update to the latest versionFelix Fietkau2023-03-071-3/+3
| | | | | | | | | ca4509cf84d2 bpf: switch to using bpf_skb_utils.h d064439009d0 qosify-bpf: skip unnecessary flow lookups 9c625ae96f2d map: fix deleting port based rules 9a47ea4b683d map: fix return code check for bpf_map_get_next_key calls Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mpc85xx: add support for Watchguard Firebox T10David Bauer2023-03-0712-1/+440
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware -------- SoC: Freescale P1010 RAM: 512MB FLASH: 1 MB SPI-NOR 512 MB NAND ETH: 3x Gigabite Ethernet (Atheros AR8033) SERIAL: Cisco RJ-45 (115200 8N1) RTC: Battery-Backed RTC (I2C) Installation ------------ 1. Patch U-Boot by dumping the content of the SPI-Flash using a SPI programmer. The SHA1 hash for the U-Boot password is currently unknown. A tool for patching U-Boot is available at https://github.com/blocktrron/t10-uboot-patcher/ You can also patch the unknown password yourself. The SHA1 hash is E597301A1D89FF3F6D318DBF4DBA0A5ABC5ECBEA 2. Interrupt the bootmenu by pressing CTRL+C. A password prompt appears. The patched password is '1234' (without quotation marks) 3. Download the OpenWrt initramfs image. Copy it to a TFTP server reachable at 10.0.1.13/24 and rename it to uImage. 4. Connect the TFTP server to ethernet port 0 of the Watchguard T10. 5. Download and boot the initramfs image by entering "tftpboot; bootm;" in U-Boot. 6. After OpenWrt booted, create a UBI volume on the old data partition. The "ubi" mtd partition should be mtd7, check this using $ cat /proc/mtd Create a UBI partition by executing $ ubiformat /dev/mtd7 -y 7. Increase the loadable kernel-size of U-Boot by executing $ fw_setenv SysAKernSize 800000 8. Transfer the OpenWrt sysupgrade image to the Watchguard T10 using scp. Install the image by using sysupgrade: $ sysupgrade -n <path-to-sysupgrade> Note: The LAN ports of the T10 are 1 & 2 while 0 is WAN. You might have to change the ethernet-port. 9. OpenWrt should now boot from the internal NAND. Enjoy. Signed-off-by: David Bauer <mail@david-bauer.net>
* hostapd: enable radius server supportFelix Fietkau2023-03-071-1/+1
| | | | | | This is useful in combination with the built-in eap server support Signed-off-by: Felix Fietkau <nbd@nbd.name>
* hostapd: add missing return code for the bss_mgmt_enable ubus methodFelix Fietkau2023-03-071-0/+2
| | | | | | Fixes bogus errors on ubus calls Signed-off-by: Felix Fietkau <nbd@nbd.name>
* hostapd: add support for defining multiple acct/auth serversFelix Fietkau2023-03-071-25/+25
| | | | | | | This allows adding backup servers, in case the primary ones fail. Assume that port and shared secret are going to be the same. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* at91: switch to Kernel 5.15 by defaultPaul Spooren2023-03-071-2/+1
| | | | | | | | | | | Getting ready for the next release. Claudiu said: > I tested v5.15 on all targets I have access to previously, when > updating OpenWrt kernel for v5.15 and when preparing this PR. (#11918) Signed-off-by: Paul Spooren <mail@aparcar.org> Reviewed-by: Claudiu Beznea <claudiu.beznea@microchip.com>
* kernel: bump 5.10 to 5.10.172John Audia2023-03-073-101/+3
| | | | | | | | | | | Removed upstreamed: backport-5.10/804-0001-net-Remove-WARN_ON_ONCE-sk-sk_forward_alloc-from-sk_.patch[1] All other patches automatically rebased. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.10.171&id=3e4bbd1f38a8d35bd2d3aaffdb5f6ada546b669a Signed-off-by: John Audia <therealgraysky@proton.me>
* kernel: bump 5.10 to 5.10.170John Audia2023-03-071-2/+2
| | | | | | No patches modified for this bump Signed-off-by: John Audia <therealgraysky@proton.me>
* kernel: bump 5.10 to 5.10.169John Audia2023-03-0722-160/+166
| | | | | | | | | | | | | | | | | | | | Manually rebased: backport-5.10/811-v6.1-0001-nvmem-core-Fix-memleak-in-nvmem_register.patch Removed upstreamed: backport-5.10/811-v6.1-0003-nvmem-core-add-error-handling-for-dev_set_name.patch[1] patches-5.10/070-net-bgmac-fix-BCM5358-support-by-setting-correct-fla.patch[2] Add fix: target/linux/generic/backport-5.10/804-0001-net-Remove-WARN_ON_ONCE-sk-sk_forward_alloc-from-sk_.patch[3] All other patches automatically rebased. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.10.169&id=a19a0f67dbb89ad2bfc466f2003841acba645884 2. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.10.169&id=a5c51e0c3202820192db3f3809e072f3ca2b1177 3. https://lore.kernel.org/stable/20230227211548.13923-1-kuniyu@amazon.com Signed-off-by: John Audia <therealgraysky@proton.me>
* openssl: fix variable reference in conffilesEneas U de Queiroz2023-03-061-3/+3
| | | | | | | | | | | | Fix the trivial abscence of $() when assigning engine config files to the main libopenssl-config package even if the corresponding engines were not built into the main library. This is mostly cosmetic, since scripts/ipkg-build tests the file's presence before it is actually included in the package's conffiles. Fixes: 30b0351039 "openssl: configure engine packages during install" Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* openssl: fix sysupgrade failure with devcryptoEneas U de Queiroz2023-03-064-5/+73
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The bump to 3.0.8 inadvertently removed patches that are needed here, but were not adopted upstream. The most important one changes the default value of the DIGESTS setting from ALL to NONE. The absence of this patch causes a sysupgrade failure while the engine is in use with digests enabled. When this happens, the system fails to boot with a kernel panic. Also, explicitly set DIGESTS to NONE in the provided config file, and change the default ciphers setting to disable ECB, which has been recommended for a long time and may cause trouble with some apps. The config file change by itself is not enough because the config file may be preserved during sysupgrade. For people affected by this bug: You can either: 1. remove, the libopenssl-devcrypto package 2. disable the engine in /etc/config/openssl; 3. change /etc/ssl/engines.cnf.d/devcrypto.cnf to set DIGESTS=NONE; 4. update libopenssl-devcrypto to >=3.0.8-3 However, after doing any of the above, **you must reboot the device before running sysupgrade** to ensure no running application is using the engine. Running `/etc/init.d/openssl restart` is not enough. Fixes: 7e7e76afca "openssl: bump to 3.0.8" Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* binutils: Update to version 2.40Hauke Mehrtens2023-03-053-5/+97
| | | | | | | | | | | | | | | | | | | binutils 2.39: https://lists.gnu.org/archive/html/info-gnu/2022-08/msg00002.html binutils 2.40: https://lists.gnu.org/archive/html/info-gnu/2023-01/msg00003.html This version includes a new libsframe.so library, pack it into the libbfd package as it is used by this library. Also deactivate some optional configuration options for now. An extra patch to fix compile problem in AARCH64 is added. gprofng needs a C++ standard library, deactivate it for now. Activate feature-disassembler-init-styled in bpftools too to fix compilation with the updated binutils. An bpftool version 7.0 or later is needed for binutils 2.39 and later. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* bpftool: Update to version 7.1.0Hauke Mehrtens2023-03-053-11/+11
| | | | | | | | | | | | | | | | | | | bpftool changelog: https://github.com/libbpf/bpftool/releases libbpf changelog: https://github.com/libbpf/libbpf/releases This updates the bfptool to version 7.1.0. This also includes an update of the libbpf to version 1.1. This also adds some new feature options and removes some old ones which were also removed form the source code. zlib for example is now mandatory. Add -flto also to LD flags to make it really work. Before this change bpftool was on a git commit between version 6.7 and 6.8 and libbpf was on a commit between version 0.7 and 0.8. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mac80211: enable ATH9K_HWRNGRosen Penev2023-03-051-2/+2
| | | | | | | | | in kernel 5.17, fcd09c90c3c5254b18ef34e30c57c65d34290a84 integrated it better with thee random framework. Gives boot time randomness on supported devices. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* ksmbd: update to 3.4.7Rosen Penev2023-03-053-103/+4
| | | | | | | | Remove upstreamed patches. Switch to normal tarballs. Codeload recently had a reproducibility issue. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* bcm47xx: Refresh patchesHauke Mehrtens2023-03-054-10/+10
| | | | | | | | The kernel patches did not apply cleanly any more, refresh them automatically. Fixes: 26bc8f68767e ("generic: MIPS: Add barriers between dcache & icache flushes") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* sdk: expose PATENTED an NLS build optionsTomasz Maciej Nowak2023-03-051-0/+17
| | | | | | | | | Some packages offer functionalities guarded by these options and it'll be impossible to reach them without changing Config-build.in. So allow to toggle these in more friendly way, by exposing them in configuration menu. Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com>
* Remove ccache wrappersPaul Fertser2023-03-054-16/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | These wrappers are not needed as CC doesn't need to be a single word. a53b084e497a9f1629a2caada833ebe14a6838b7 which introduced the wrappers doesn't explain why they were really needed and why only for the target and not for the host. Moreover, name of the wrappers breaks a ccache assumption: since v4.0-3-g6a92b4cd3a67 it has special handling for "chained" invocation such as "ccache ccache gcc" where it skips all the "ccache*" names in the middle and proceeds to run as if it was started as "ccache gcc"[1][2]. This becomes important when a build system sees ccache in the PATH and automatically enables it by prepending to CC. An example of such a system would be autosetup as used by jimtcl. With the wrappers it breaks as the command line ends up being just "ccache -Os..." because "ccache_cc" gets skipped as it starts with "ccache". [1] https://github.com/ccache/ccache/blob/master/src/ccache.cpp#L2105 [2] https://github.com/ccache/ccache/blob/master/src/Util.cpp#L802 Reported-by: Karl Palsson <karlp@etactica.com> Signed-off-by: Paul Fertser <fercerpav@gmail.com>
* kernel: set default for KERNEL_BPF_KPROBE_OVERRIDEStijn Tintel2023-03-051-0/+1
| | | | | | | | | Without the default value this still causes a missing symbol. Disable by default as it depends on FUNCTION_ERROR_INJECTION, which is disabled in the generic config and we don't have a build symbol to enable that. Fixes: 500c37c56ff6 ("kernel: add missing symbol") Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* mediatek: backport more WED upstream fixesFelix Fietkau2023-03-052-0/+119
| | | | | | Fixes hang if the WO firmware can't be loaded Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ipq806x: Add buttons to OnHubAlan Luck2023-03-051-0/+28
| | | | | | | | | | | These are the factory reset button (external) and "developer mode" button (hidden inside the case (ASUS) or under a screw in the base (TP-Link)) found on the TP-Link and ASUS OnHub devices. Signed-off-by: Alan Luck <luckyhome2008@gmail.com> [Brian: add description; factor out for both ASUS and TP-Link; use existing pinmux definitions; add keycode for dev button] Signed-off-by: Brian Norris <computersforpeace@gmail.com>
* kernel: add kmod-hwmon-max6642 supportTim Harvey2023-03-051-0/+15
| | | | | | Add package for Maxim MAX6642 i2c based temperature sensor. Signed-off-by: Tim Harvey <tharvey@gateworks.com>
* uci: update to git HEADHauke Mehrtens2023-03-051-4/+4
| | | | | | | | | | | | | | | | 5de3871 cli: drop redundant uci_add_delta_path() call for -P f49a2fd delta: simplify uci_load_delta() by using a helper 9b6605e uci: fix use-after-free uci_set on update option b7ceda9 uci: maintain option position in uci_set 7e01d66 uci: optimize update option in uci_set 47697e6 uci: fix use-after-free uci_add_list 74f2797 uci: fix atomicity of uci_add_list b2f3417 uci: maintain option position in uci_add_list 16e8a3b uci: fix memory leak uci_set on update section ae61e1c uci: optimize update section in uci_set 04d0c46 uci: macro uci_alloc_element not in uci.h Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* Revert "bmips: add missing switch cpu label"Álvaro Fernández Rojas2023-03-055-5/+0
| | | | | | | | This reverts commit dc0de05e10a9c6e1ef66ca2934e8a0ff0d488943. As pointed out by @BKPepe and @arinc9 this was removed by 9df035b since it isn't needed. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* mediatek: add missing DTS entries for WED on MT7986Felix Fietkau2023-03-051-0/+65
| | | | | | Needed to support WLAN offloading Signed-off-by: Felix Fietkau <nbd@nbd.name>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 06:33:36 +0000