aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* ipq806x: backport mtd adm and smem driverAnsuel Smith2021-05-0716-896/+806
| | | | | | | | | - Backport mtd adm driver from kernel 5.12 - Backport mtd parser smem from kernel 5.11 - Fix mtd rootfs patch - Update qcom,smem compatible to qcom,smem-parts Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: fix missing clk and resetAnsuel Smith2021-05-075-40/+629
| | | | | | | Patch 0030 wrongly disables gsbi1 instead of gsbi4. Fix the wrong patch and also include other fix from the original qsdk source. Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: use newer tsens patchAnsuel Smith2021-05-0714-1228/+973
| | | | | | Use improved tsens patch proposed upstream. Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: copy kernel 5.4 patches to 5.10Ansuel Smith2021-05-0748-0/+7939
| | | | | | Copy kernel 5.4 patches and config to 5.10 Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: improve system latencyAnsuel Smith2021-05-071-0/+17
| | | | | | | | | | | | | | Various report and data show that the freq 384000 is too low and cause some extra latency to the entire system. OEM qsdk code also set the min frequency for this target to 800 mhz. Also some user notice some instability with this idle frequency, solved by setting the min frequency to 600mhz. Fix all these kind of problem by introducing a boot init.d script that set the min frequency to 600mhz and set the ondemand governor to be more aggressive. The script set these value only if the ondemand governor is detected. 384 mhz freq is still available and user can decide to restore the old behavior by disabling this script. Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* realtek: add support for INABA Abaniact AML2-17GPINAGAKI Hiroshi2021-05-072-0/+173
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | INABA Abaniact AML2-17GP is a 17 port gigabit switch, based on RTL8382. Specification: - SoC : Realtek RTL8382 - RAM : DDR3 128 MiB (SK hynix H5TQ1G63EFR) - Flash : SPI-NOR 32 MiB (Macronix MX25L25635FZ2I-10G) - Ethernet : 10/100/1000 Mbps x17 - port 1-8 : RTL8218B (SoC) - port 8-16 : RTL8218D - port wan : RTL8214FC - LEDs/Keys : 1x, 1x - UART : pin header on PCB (Molex 530470410 compatible) - J14: 3.3V, GND, RX, TX from rear side - 115200n8 - Power : 100-240 VAC, 50/60 Hz, 0.21 A - Plug : IEC 60320-C13 Flash instruction using initramfs image: 1. Boot AML2-17GP normally 2. Set the IP address of computer to the range of 192.168.1.0/24, other than 192.168.1.248 and connect computer to "WAN/CONSOLE" port of AML2-17GP 3. Access to "http://192.168.1.248" and open firmware setting page -- UI Language: 日本語 -- "メンテナンス" -> "デュアルイメージ" -- UI Language: ENGLISH -- "Maintenance" -> "Dual Image" 4. Check "イメージ情報 (en: "Images Information")" and set the first image to active by choosing "アクティブイメージ" (en: "Active Image") in the partition "0" 5. open firmware upgrade page -- UI Language: 日本語 -- "メンテナンス" -> "アップグレードマネージャー" -- UI Language: ENGLISH -- "Maintenance" -> "Upgrade Manager" 6. Set the properties as follows -- UI Language: 日本語 -- "アップグレード方式" : "HTTP" "アップグレードタイプ" : "イメージ" "イメージ" : "アクティブ" "ブラウズファイル" : (select the OpenWrt initramfs image) -- UI Language: ENGLISH -- "Upgrade Method" : "HTTP" "Upgrade Type" : "Image" "Image" : "(Active)" "Browse file" : (select the OpenWrt initramfs image) 7. Press "アップグレード" (en: "Upgrade") button and perform upgrade 8. Wait ~150 seconds to complete flashing 9. After the flashing, the following message is showed and press "OK" button to reboot -- UI Language: 日本語 -- "成功!! 今すぐリブートしますか?" -- UI Language: ENGLISH -- "Success!! Do you want to reboot now?" 10. After the rebooting, reconnect the cable to other port (1-16) and open the SSH connection, download the sysupgrade image to the device and perform sysupgrade with it 11. Wait ~120 seconds to complete sysupgrade Note: - The uploaded image via WebUI will only be written with the length embedded in the uImage header. If the sysupgrade image is specified, only the kernel is flashed and lacks the rootfs, this causes a kernel panic while booting and bootloops. To avoid this issue, initramfs image is required for flashing on WebUI of stock firmware. - This device has 1x LED named as "POWER", but it's not connected to the GPIO of SoC and cannot be controlled. - port 17 is named as "WAN/CONSOLE". This port is for the upstream connection and console access (telnet/WebUI) on stock firmware. Back to stock firmware: 1. Set "bootpartition" variable in u-boot-env2 partition to "1" by fw_setsys fw_setsys bootpartition 1 2. Reboot AML2-17GP Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* realtek: Add support for Netgear S350 series switches GS308T and GS310TPRaylynn Knight2021-05-079-60/+173
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Netgear GS308T v1 is an 8 port gigabit switch. The GS310TP v1 is an 8 port POE+ gigabit switch with 2 SFP Ports (currently untested). The GS308T v1 and GS310TP v1 are quite similar to the Netgear GS1xx devices already supported. Theses two devices use the same Netgear firmware and are very similar to there corresponding GS1xx devices. For this reason they share a large portion of the device tree with the GS108T and GS110TP with exception of the uimage magic and model and compatible values. All of the above feature a dual firmware layout, referred to as Image0 and Image1 in the Netgear firmware. In order to manipulate the PoE+ on the GS310TP v1 , one needs the rtl83xx-poe package Specifications (GS308T) ---------------------- * RTL8380M SoC, 1 MIPS 4KEc core @ 500MHz * 128MB DDR3-1600 DRAM (Winbond W631GG8MB-12) * 32MB 3v NOR SPI Flash (Winbond W25Q256JVFQ) * RTL8231 GPIO extender to control the LEDs and the reset button * 8 x 10/100/1000BASE-T ports, internal PHY (RTL8218B) * UART (115200 8N1) via unpopulated standard 0.1" pin header marked J1 * Power is supplied via a 12V 1A barrel connector Specifications (GS310TP) ---------------------- * RTL8380M SoC, 1 MIPS 4KEc core @ 500MHz * Nuvoton M0516LDN for controlling PoE * 128MB DDR3-1600 DRAM (Winbond W631GG8MB-12) * 32MB 3v NOR SPI Flash (Winbond W25Q256JVFQ) * RTL8231 GPIO extender to control the LEDs and the reset button * 8 x 10/100/1000BASE-T PoE+ ports, 2 x Gigabit SFP ports, internal PHY (RTL8218B) * UART (115200 8N1) via unpopulated standard 0.1" pin header marked J1 * Power is supplied via a 54V 1.25A barrel connector Both devices have UART pinout ----------- J1 | [o]ooo ^ ||`------ GND | |`------- RX [TX out of the serial adapter] | `-------- TX [RX into the serial adapter] `---------- Vcc (3V3) [the square pin] The through holes are filled with PB-free solder which melts at 375C. They can also be drilled using a 0.9mm bit. Installation ------------ Instructions are identical to those for the similar Negear devices and apply both to the GS308T v1 and GS310TP v1 as well. ------------------- Boot initramfs image from U-Boot -------------------------------- 1. Press the Escape key at the `Hit Esc key to stop autoboot` prompt 2. Init network with `rtk network on` command 3. Load image with `tftpboot 0x8f000000 openwrt-realtek-generic-netgear_gs308t-v1-initramfs-kernel.bin` command 4. Boot the image with `bootm` command The switch defaults to IP 192.168.1.1 and tries to fetch the image via TFTP from 192.168.1.111. Updating the installed firmware ------------------------------- The OpenWRT ramdisk image can be flashed directly from the Netgear UI. The Image0 slot should be used in order to enable sysupgrade. As with similar switches, changing the active boot partition can be accomplished in U-Boot as follows: 1. Press the Escape key at the `Hit Esc key to stop autoboot` prompt 2. Run `setsys bootpartition {0|1}` to select the boot partition 3. Run `savesys` followed by `boota` to proceed with the boot process Signed-off-by: Raylynn Knight <rayknight@me.com>
* kernel: bump 5.4 to 5.4.116John Audia2021-05-072-3/+3
| | | | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: ipq806x/R7800 Run-tested: ipq806x/R7800 No dmesg regressions, everything functional Signed-off-by: John Audia <graysky@archlinux.us>
* ipq806x: Add "snps,dwmac" to all gmac compatible=Mark Mentovai2021-05-071-2/+2
| | | | | | | | | | | | | | | This was introduced to gmac2 and gmac3 in 57ea767a53c1 without fanfare. There's no indication of why it was added to those devices, but not to gmac0 or gmac1. It was probably an unintentional omission. It should be present on all four gmac devices. This property is considered by drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c stmmac_probe_config_dt. Signed-off-by: Mark Mentovai <mark@moxienet.com> Build-tested: ipq806x/ubnt,unifi-ac-hd Run-tested: ipq806x/ubnt,unifi-ac-hd
* ipq806x: ubnt,unifi-ac-hd: reorder eth0 and eth1Mark Mentovai2021-05-072-2/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | The Ubiquiti UniFi AC HD (UAP-AC-HD, UAP301) has two Ethernet ports, labeled MAIN and SECONDARY, connected to gmac2 and gmac1, respectively. The standard probe order results in gmac1/SECONDARY being eth0 and gmac2/MAIN being eth1. This does not match the stock firmware, is contrary to user expectation, causes the wrong (high) MAC address to be used in a bridged configuration (the default for this device), and makes the gmac2/MAIN port unusable in the preinit environment (such as for failsafe). Until a recent patch, gmac1/SECONDARY (eth0) was not even usable. This reorders the ports so that gmac2/MAIN is eth0, and the now-working gmac1/SECONDARY is eth1. eth0 has the low MAC address and eth1 has the high; when bridged, the bridge takes on the correct low MAC address. This matches the stock firmware. The MAIN port is usable for failsafe during preinit. This device does not have a switch on board, so there's no possibility to remap ports via switch configuration. "ip link set $interface name" is used instead, during preinit before networking is configured. Signed-off-by: Mark Mentovai <mark@moxienet.com> Build-tested: ipq806x/ubnt,unifi-ac-hd Run-tested: ipq806x/ubnt,unifi-ac-hd
* ipq806x: ubnt,unifi-ac-hd: use on-board PHYsMark Mentovai2021-05-071-19/+19
| | | | | | | | | | | | Unlike many ipq806x devices, Ubiquiti UniFi AC HD (UAP-AC-HD, UAP301) has no switch on board. Its two Ethernet ports are connected to Atheros AR8033 PHYs. It is not appropriate to use fixed-link in this configuration. Instead, configure the correct PHYs in the device tree configuration to allow the at803x driver to load. Signed-off-by: Mark Mentovai <mark@moxienet.com> Build-tested: ipq806x/ubnt,unifi-ac-hd Run-tested: ipq806x/ubnt,unifi-ac-hd
* ipq806x: dwmac: clear forced speed during probeMark Mentovai2021-05-071-0/+33
| | | | | | | | | | | | | | | | | | | | | | On a Ubiquiti UniFi AC HD (ubnt,unifi-ac-hd, UAP-AC-HD, UAP301), a forced speed on gmac1 is set in the QSGMII PCS_ALL_CH_CTL register, presumably by the bootloader (4.3.28), preventing the interface from being usable. The QSDK NSS GMAC driver takes care to clear the forced speed in nss_gmac_qsgmii_dev_init (https://source.codeaurora.org/quic/qsdk/oss/lklm/nss-gmac/tree/ipq806x/nss_gmac_init.c?h=nss at d5bb14925861). gmac1 is connected to the port on the device labeled SECONDARY, and is currently eth0 but will be switched to eth1 by a subsequent patch. By clearing the QSGMII PCS forced speed during dwmac initialization when SGMII is in use, this port becomes usable. This patch is upstreamable, and will be sent upstream after successful testing in OpenWrt. Signed-off-by: Mark Mentovai <mark@moxienet.com> Build-tested: ipq806x/ubnt,unifi-ac-hd Run-tested: ipq806x/ubnt,unifi-ac-hd
* kernel: fix parsing fixed subpartitionsRafał Miłecki2021-05-068-16/+168
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* tplink-safeloader: fix product_name of TP-Link AD7200Alex Henrie2021-05-061-1/+1
| | | | | | | | | | | | | | The stock firmware does not accept firmware with "Talon" in the name. Tested on firmware version 1.0.10 Build 20160902 rel. 57400 which came preinstalled, as well as latest firmware version 2.0.1 Build 20170103 rel.71053 flashed from AD7200v1-up-ver2-0-1-P1[20170103-rel71053]_2017-01-04_10.08.28.bin. Fixes: 1a775a4fd033 ("ipq806x: add support for TP-Link Talon AD7200") Signed-off-by: Alex Henrie <alexhenrie24@gmail.com> [added details about vendor firmware] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* procd: update to git HEADDaniel Golle2021-05-051-3/+3
| | | | | | 021ece8 procd: Use /dev/console for serial console if exists Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* base-files: upgrade: take down loop and LVM before upgradeDaniel Golle2021-05-051-0/+10
| | | | | | | | | | | | | | Users of devices with large block storage may choose to have an LVM partition on the same device which is used for booting OpenWrt. The presents a problem during sysupgrade as the root device is then still busy and changing partitions will not work as desired, leading to data corruption in case the newly flashed image is larger than the currently installed one. Having loop devices setup causes similar havoc. Make sure all volume groups are offline and all loop devices have been released before sysupgrade. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* dnsmasq: Update to version 2.85Alan Swanson2021-05-054-92/+6
| | | | | | | | | | | | | | | | | | | | | Fixes issue with merged DNS requests in 2.83/2.84 not being retried on the firsts failed request causing lookup failures. Also fixes the following security problem in dnsmasq: * CVE-2021-3448: If specifiying the source address or interface to be used when contacting upstream name servers such as: server=8.8.8.8@1.2.3.4, server=8.8.8.8@1.2.3.4#66 and server=8.8.8.8@eth0 then all would use the same socket bound to the explicitly configured port. Now only server=8.8.8.8@1.2.3.4#66 will use the explicitly configured port and the others random source ports. Remove upstreamed patches and update remaining patch. Signed-off-by: Alan Swanson <reiver@improbability.net> [refreshed old runtime support patch] Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* ltq-dsl-base: Make package nonshared to fix image builderHauke Mehrtens2021-05-041-0/+2
| | | | | | | | | | This package depends on the lantiq target and is only build for that target. A normal package would be build by the SDK builder probably under a different target and then this package will not be selected. Mark it as nonshared to build it when the lantiq target gets build. Fixes: FS#3773, FS#3774 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mac80211: Update to version 5.10.34-1Hauke Mehrtens2021-05-0421-188/+48
| | | | | | The removed patches were applied upstream and are not needed anymore. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* busybox: backport fix for CVE-2021-28831Hauke Mehrtens2021-05-022-1/+53
| | | | | | | | | This backports a fix for the low priority CVE-2021-28831: decompress_gunzip.c in BusyBox through 1.32.1 mishandles the error bit on the huft_build result pointer, with a resultant invalid free or segmentation fault, via malformed gzip data. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ath79: Deactivate ZyXEL NBG6716 by defaultHauke Mehrtens2021-05-021-0/+1
| | | | | | | | The kernel image is too big now and the build fails. WARNING: Image file zyxel_nbg6716-kernel.bin is too big: 4205404 > 4194304 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* iwinfo: update to latest Git HEADDavid Bauer2021-05-021-4/+4
| | | | | | c45f0b5 iwinfo: add 802.11ax HE rate information Signed-off-by: David Bauer <mail@david-bauer.net>
* uboot-mediatek: bpi-r64: add TFTP update options to eMMC bootmenuDaniel Golle2021-05-011-6/+14
| | | | | | | Just like on SPI-NAND, also allow updating the bootloader comfortably on eMMC installations. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mediatek: bpi-r64: add eMMC bootloader artifactsDaniel Golle2021-05-011-1/+3
| | | | | | | | In order to allow easily updating the bootloader on eMMC also provide artifacts for that. Support for updating bootloader via TFTP will be added to the loader CLI menu in a follow-up commit. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: add missing kernel config optionHauke Mehrtens2021-05-011-0/+1
| | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mediatek: Add missing config optionsHauke Mehrtens2021-05-012-0/+2
| | | | | | | | It is possible to select CONFIG_MTD_PARSER_TRX on the mediatek now. Add this option to the kernel configuration file. Fixes: 58c5e2566482 ("mediatek: support non standard trx magic values") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: Reorder kernel configuration optionsHauke Mehrtens2021-05-012-8/+8
| | | | | | | | | | | Reorder the options and remove double entries. This was generated by running this: $ ./scripts/kconfig.pl '+' target/linux/generic/config-5.10 /dev/null > target/linux/generic/config-5.10.new $ mv target/linux/generic/config-5.10.new target/linux/generic/config-5.10 $ ./scripts/kconfig.pl '+' target/linux/generic/config-5.4 /dev/null > target/linux/generic/config-5.4.new $ mv target/linux/generic/config-5.4.new target/linux/generic/config-5.4 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: partly revert: update mt7530 EEE patch from upstreamHauke Mehrtens2021-05-012-120/+121
| | | | | | | | | This partly reverts commit 20a924d2ae378fe35b74f81be3b7f58366472e80. This commit broke the build of the Mediatek target with kernel 5.4, for kernel 5.10 it is fine. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: qlcnic: fix typo in module descriptionChukun Pan2021-05-011-1/+1
| | | | | Fixes: f88c64d28ccf ("kernel: netdev: add qlcnic") Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
* glibc: update to latest 2.33 HEAD (bug 27744)Hans Dedecker2021-05-011-2/+2
| | | | | | | | | 3f5080aedd nptl: Do not build nptl/tst-pthread-gdb-attach as PIE 36783141cf nptl: Check for compatible GDB in nptl/tst-pthread-gdb-attach ea299b62e8 nptl_db: Support different libpthread/ld.so load orders (bug 27744) 162df872f0 x86: tst-cpu-features-supports.c: Update AMX check Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* mediatek: correct address of ethernet PHYDavid Bauer2021-05-011-2/+2
| | | | | | | We still have no driver for the PHY, however we can fix it's address. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: drop cs-gpios propertyDavid Bauer2021-05-014-7/+0
| | | | | | | | | The spi-ath79 driver performs the chipselect by writing to dedicated register in the SPI register block. So the GPIO numbers were not used. Tested-on: Enterasys WS-AP3705i Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: set number of chipselect linesDavid Bauer2021-05-011-0/+26
| | | | | | | | | All chipsets from AR7100 up to QCA9563 have three dedicated chipselect lines for the integrated SPI controller. Remove the number of chipselects from the platform data, as there is no need to manually set this to a different value. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: add SPI_MASTER_GPIO_SS flagDavid Bauer2021-05-011-0/+27
| | | | | | | | | Add the SPI_MASTER_GPIO_SS flag for the spi-ath79 driver. Otherwise, the custom chipselect function is never called. This breaks hardware, where the three dedicated chipselect lines are used instead of generic GPIO pins. Signed-off-by: David Bauer <mail@david-bauer.net>
* apm821xx: MBL: correct phy-mode delay settingsChristian Lamparter2021-05-011-0/+1
| | | | | | | | | | | | | | This came up in an upstream commit: " b1dd9bf688b0 "net: phy: broadcom: Fix RGMII delays for BCM50160 and BCM50610M" The PHY driver entry for BCM50160 and BCM50610M calls bcm54xx_config_init() but does not call bcm54xx_config_clock_delay() in order to configuration appropriate clock delays on the PHY, fix that." So the "rgmii" phy-mode has always been wrong, but went unnoticed since the broadcom phy driver didn't push the delay settings to the chip. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* kernel: qlcnic: add dependency to kmod-hwmon-coreHauke Mehrtens2021-05-011-2/+4
| | | | | | | | | QLCNIC_HWMON was activated when hwmon was set, but the dependency was missing. This broke the build bot builds. Fix this by explicitly activating HWMON support and adding a dependency. Fixes: f88c64d28ccf ("kernel: netdev: add qlcnic") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mac80211/rtl: backport a rtl8192cu AP mode fixRui Salvaterra2021-05-011-0/+118
| | | | | | | | | Running USB devices in AP mode is never a good idea. That said, fix the TIM issue in rtl8192cu [1], allowing these devices to "work" in AP mode. [1] https://patchwork.kernel.org/project/linux-wireless/patch/20210419065956.6085-1-pkshih@realtek.com/ Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* toolchain/binutils: add binutils 2.36.1DENG Qingfang2021-05-016-1/+91
| | | | | | Add binutils version 2.36.1 Signed-off-by: DENG Qingfang <dqfext@gmail.com>
* toolchain/binutils: update to 2.35.2DENG Qingfang2021-05-016-7/+7
| | | | | | Update binutils 2.35 to 2.35.2 Signed-off-by: DENG Qingfang <dqfext@gmail.com>
* mvebu: LS421DE: improve pin configurationDaniel González Cabanelas2021-05-011-3/+12
| | | | | | | | | | | | | The CLK125 output pin at the ethernet PHY is connected via capacitor to GND and nowhere else. Disable it. Also tune the LED masks. The MPP56 and MPP60 pins at the SoC are conected to the μPD720202 USB3.0 chip: - MPP56: wired to PCIe CLKREQ# (out) - MPP60: wired to PCIe RESET# (in) Configure the pcie pinmux for these pins. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* netfilter: remove no-op kconfig symbolsRui Salvaterra2021-05-013-10/+0
| | | | | | | | | | | | | | These have long been obsolete. For reference, here's the Linux version where each symbol has been dropped: CONFIG_IP6_NF_QUEUE - 3.5 CONFIG_IP6_NF_TARGET_LOG - 3.4 CONFIG_IP_NF_MATCH_DSCP - 2.6.19 CONFIG_NF_CONNTRACK_IPV4 - 4.19 CONFIG_NF_CONNTRACK_IPV6 - 4.19 CONFIG_NF_CONNTRACK_RTCACHE - out-of-tree, superseded by flow offloading Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* feeds: management: remove dead and out of project feedSven Roederer2021-05-011-1/+0
| | | | | | Remove management feed which has not been active since some years. Signed-off-by: Sven Roederer <devel-sven@geroedel.de>
* kernel: netdev: add qlcnicVieno Hakkerinen2021-05-011-0/+17
| | | | | | Add driver for QLogic QLE8240 and QLE8242 Converged Ethernet devices. Signed-off-by: Vieno Hakkerinen <vieno@hakkerinen.eu>
* kernel: add kmod-ipvlan supportChen Minqiang2021-04-303-0/+18
| | | | | | | | | | | | This kmod is similar to macvlan with the difference being that the endpoints have the same mac address. It is useful on cloud where only one mac address allowed on port, where macvlan not works but ipvlan would. One use case is where multiple IPs and gateways assign on one net port Signed-off-by: Chen Minqiang <ptpt52@gmail.com>
* uboot-envtools: add support for Buffalo WZR-HP-G300NHMauri Sandberg2021-04-301-0/+4
| | | | | | This adds an entries for wzr-hp-g300nh-rb and wzr-hp-g300nh-s. Signed-off-by: Mauri Sandberg <sandberg@mailfence.com>
* kernel: Activate FORTIFY_SOURCE for MIPS kernel 5.4Hauke Mehrtens2021-04-3012-117/+150
| | | | | | | | | | | | | | | | | | | | | | | | | CONFIG_FORTIFY_SOURCE=y is already set in the generic kernel configuration, but it is not working for MIPS on kernel 5.4, support for MIPS was only added with kernel 5.5, other architectures like aarch64 support FORTIFY_SOURCE already since some time. This patch adds support for FORTIFY_SOURCE to MIPS with kernel 5.4, kernel 5.10 already supports this and needs no changes. This backports one patch from kernel 5.5 and one fix from 5.8 to make fortify source also work on our kernel 5.4. The changes are not compatible with the 306-mips_mem_functions_performance.patch patch which was also removed with kernel 5.10, probably because of the same problems. I think it is not needed anyway as the compiler should automatically optimize the calls to memset(), memcpy() and memmove() even when not explicitly telling the compiler to use the build in variant. This increases the size of an uncompressed kernel by less than 1 KB. Acked-by: Rosen Penev <rosenp@gmail.com> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: update mt7530 EEE patch from upstreamDENG Qingfang2021-04-304-242/+240
| | | | | | | | The new EEE patch is accepted upstream, so backport it and replace the current one. Cc: René van Dorst <opensource@vdorst.com> Signed-off-by: DENG Qingfang <dqfext@gmail.com>
* kernel: backport mtk_soc_eth fixes from v5.13Ilya Lipnitskiy2021-04-3017-79/+375
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes logic that leads to this error when booting mt7621 and other devices that use the mediatek ethernet driver: [ 23.144378] mtk_soc_eth 1e100000.ethernet: PPE table busy The rest are mostly moved from pending-5.10 to backport-5.10 with a couple of cleanups and improvements from upstream. Refresh patches. Links: https://git.kernel.org/netdev/net-next/c/c5d66587b890 https://git.kernel.org/netdev/net-next/c/3f57d8c40fea https://git.kernel.org/netdev/net-next/c/5196c4178549 https://git.kernel.org/netdev/net-next/c/787082ab9f7b https://git.kernel.org/netdev/net-next/c/c30c4a827390 https://git.kernel.org/netdev/net-next/c/3630d519d7c3 https://git.kernel.org/netdev/net-next/c/16ef670789b2 https://git.kernel.org/netdev/net-next/c/59555a8d0dd3 https://git.kernel.org/netdev/net-next/c/6b4423b258b9 https://git.kernel.org/netdev/net-next/c/e9229ffd550b https://git.kernel.org/netdev/net-next/c/4e6bf609569c https://git.kernel.org/netdev/net-next/c/816ac3e6e67b https://git.kernel.org/netdev/net-next/c/16769a8923fa https://git.kernel.org/netdev/net-next/c/db2c7b353db3 https://git.kernel.org/netdev/net-next/c/fa817272c37e https://git.kernel.org/netdev/net-next/c/3bc8e0aff23b Fixes: f07fe36f22fc ("kernel: update flow offload patches to upstream version") Cc: Felix Fietkau <nbd@nbd.name> Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
* kernel: Move an upstreamed patch under backportsMauri Sandberg2021-04-306-12/+18
| | | | | | | This CFI patch was accepted upstream for 5.13. Move it away from under ath79 and place under backports to be removed in due time. Signed-off-by: Mauri Sandberg <sandberg@mailfence.com>
* kernel: bump 5.4 to 5.4.115John Audia2021-04-302-3/+3
| | | | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: ipq806x/R7800 Run-tested: ipq806x/R7800 No dmesg regressions, everything functional Signed-off-by: John Audia <graysky@archlinux.us>