aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* kernel: bump 5.4 to 5.4.162John Audia2021-11-2816-42/+43
| | | | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: ramips/mt7621* *I am hit with the binutils 2.37 bug so I had to revert 7f1edbd41295dff9f2127b169fbc086c0fb2c14e in order to downgrade to 2.35.1 Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: bump 5.4 to 5.4.161John Audia2021-11-2830-118/+64
| | | | | | | | | | | | | | | Removed upstreamed: ath79/patches-5.4/921-serial-core-add-support-for-boot-console-with-arbitr.patch[1] Manually rebased: layerscape/patches-5.4/804-crypto-0016-MLKU-114-1-crypto-caam-reduce-page-0-regs-access-to-.patch octeontx/patches-5.4/0004-PCI-add-quirk-for-Gateworks-PLX-PEX860x-switch-with-.patch All other patches automatically rebased. 1. Private email exchange with patch author, Hauke Mehrtens Signed-off-by: John Audia <graysky@archlinux.us>
* gemini: try fis-index-block with 128 KiB sectorsChristian Lamparter2021-11-281-0/+52
| | | | | | | | | | | | | Steven Maddox reported in the OpenWrt bugzilla, that his RaidSonic IB-NAS4220-B was no longer booting with the new OpenWrt 21.02 (uses linux 5.10's device-tree). However, it was working with the previous OpenWrt 19.07 series (uses 4.14). (This is still under investigation.) Bugzilla: https://bugs.openwrt.org/index.php?do=details&task_id=4137 Reported-by: Steven Maddox <s.maddox@lantizia.me.uk> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: utilize nvmem on Netgear EX61X0 v2 SeriesChristian Lamparter2021-11-282-10/+27
| | | | | | | | the Netgear EX6100v2 and EX6150v2 can utilize the nvmem for the pre-calibration and mac-address for both WIFI devices. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ath79: convert TP-Link Archer C7v1/2 Wifis to nvmem-cellsChristian Lamparter2021-11-283-10/+38
| | | | | | | | | | | | | | | For v2, both ath9k (2.4GHz Wifi) and ath10k (5 GHz) driver now pull the (pre-)calibration data from the nvmem subsystem. v1 is slightly different as only the ath9k Wifi is supported. This allows us to move the userspace caldata extraction and mac-address patching for the 5GHZ ath10k supported wifi into the device-tree definition of the device. ath9k's nodes are also changed over to use nvmem-cells over OpenWrt's custom mtd-cal-data property. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* mpc85xx: backport "fix oops when CONFIG_FSL_PMC=n"Christian Lamparter2021-11-281-0/+55
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Martin Kennedy reported: |Presently, I get this kernel panic on mpc85xx (Aerohive HiveAP 370) |on OpenWrt 'master' which occurs right as the second processor is |initialized: | |[ 0.478804] rcu: Hierarchical SRCU implementation. |[ 0.535569] dyndbg: Ignore empty _ddebug table in a CONFIG_DYNAMIC_DEBUG_CORE build |[ 0.627233] smp: Bringing up secondary CPUs ... |[ 0.681659] kernel tried to execute user page (0) - exploit attempt? (uid: 0) |[ 0.766618] BUG: Unable to handle kernel instruction fetch (NULL pointer?) |[ 0.848899] Faulting instruction address: 0x00000000 |[ 0.908273] Oops: Kernel access of bad area, sig: 11 [#1] |[ 0.972851] BE PAGE_SIZE=4K SMP NR_CPUS=2 P1020 RDB |[ 1.031179] Modules linked in: |[ 1.067640] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.80 #0 |[ 1.139507] NIP: 00000000 LR: c0021d2c CTR: 00000000 |[ 1.199921] REGS: c1051cf0 TRAP: 0400 Not tainted (5.10.80) |[...] |[ 1.758220] NIP [00000000] 0x0 |[ 1.794688] LR [c0021d2c] smp_85xx_kick_cpu+0xe8/0x568 |[ 1.856126] Call Trace: |[ 1.885295] [c1051da8] [c0021cb8] smp_85xx_kick_cpu+0x74/0x568 (unreliable) |[ 1.968633] [c1051de8] [c0011460] __cpu_up+0xc0/0x228 |[ 2.029038] [c1051e18] [c0031bbc] bringup_cpu+0x30/0x224 |[ 2.092572] [c1051e48] [c0031f3c] cpu_up.constprop.0+0x180/0x33c |[..] |[ 2.727952] ---[ end trace 9b796a4bafb6bc14 ]--- |[ 3.800879] Kernel panic - not syncing: Fatal exception |[ 3.862353] Rebooting in 1 seconds.. |[ 5.905097] System Halted, OK to turn off power | |I bisected this down to commit 3ae5da5adce9 ("kernel: bump 5.10 to 5.10.80"); |that is, I don't get the panic right before this commit, but I do after. He reported the issue upstream and Xiaoming Ni from huawei came up with the patch (that is on it's way to upstream). While the AP370 is not in Openwrt, this will likely affect other SMP P1020 devices OpenWrt ships with: like the AP330, Enterasys WS-AP3710i, etc. Reported-by: Martin Kennedy <hurricos@gmail.com> Tested-by: Martin Kennedy <hurricos@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: purge clk_ignore_unused bootargChristian Lamparter2021-11-272-2/+2
| | | | | | | | | these flags have been creeping in from the QSDK. All needed clocks should be accounted for, and if a device is broken due to this. It should be looked into. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: update 105-ipq40xx-fix-sleep-clock.patchChristian Lamparter2021-11-271-13/+10
| | | | | | Bjorn Anderson has suggestions which would help to upstream the patch. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* lantiq: set maximum kernel size for P2812HNUF3Mathias Kresin2021-11-271-0/+2
| | | | | | | | | | | The board has a fixed size kernel partition but do not limit the kernel size during image building. Disable image building for both boards as well, since the kernel of the last release as well as master are to big to fit into the 2 MByte kernel partition. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: drop kernel 5.4 supportAleksander Jan Bajkowski2021-11-2734-11702/+0
| | | | | | | | The current state of the kernel 5.4 support is in the openwrt-21.02 branch. No need to keep a not default used kernel in this branch. Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl> Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [VRX268/ bthub5]
* lantiq: switch to kernel 5.10Aleksander Jan Bajkowski2021-11-271-1/+1
| | | | | | | Use kernel 5.10 by default. Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl> Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [VRX268/ bthub5]
* lantiq: ar7: use okli loader for FRITZ!BoxMathias Kresin2021-11-274-3/+46
| | | | | | | | | | With Kernel 5.10 the ar7 FRITZ!Box are not booting the initramfs nor the sysupgrade image any more. Presumably due to the grown kernel. Use the okli preloader to workaround the bootloader issue. No solution so far for the initramfs. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: bring back okli loaderMathias Kresin2021-11-2719-0/+2004
| | | | | | | | | | | | | Removed due to being unused with 1f7a03a70603, but now required for the ar7 FRITZ!Box. Could be used for the ARV7519RW22 as well, for which the image generation was disabled due to a stock u-boot issue with kernel bigger than 2 MByte. The code is combination of the ath79 and ramips okli loader. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kernel: bump 5.10 to 5.10.82John Audia2021-11-2719-94/+38
| | | | | | | | | | | | | | | | Removed upstreamed: bcm53xx/patches-5.10/033-v5.16-0014-ARM-dts-NSP-Fix-mpcore-mmc-node-names.patch Manually rebased: ipq806x/patches-5.10/086-ipq8064-fix-duplicate-node.patch All other patches automatically rebased. Build system: x86_64 Build-tested: bcm2711/RPi4B, ipq806x/R7800 Run-tested: bcm2711/RPi4B, ipq806x/R7800 Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: bump 5.10 to 5.10.81John Audia2021-11-278-12/+12
| | | | | | | | | | | | | Manually rebased: octeontx/patches-5.10/0004-PCI-add-quirk-for-Gateworks-PLX-PEX860x-switch-with-.patch All other patches automatically rebased. Build system: x86_64 Build-tested: bcm2711/RPi4B, ipq806x/R7800 Run-tested: bcm2711/RPi4B, ipq806x/R7800 Signed-off-by: John Audia <graysky@archlinux.us>
* llvm-bpf: fix rebuild check for generating tarballFelix Fietkau2021-11-261-1/+1
| | | | | | Check the version file, as it will be regenerated on rebuild Signed-off-by: Felix Fietkau <nbd@nbd.name>
* llvm-bpf: use SOURCE_DATE_EPOCH for generated tarballFelix Fietkau2021-11-261-0/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* realtek: Remove _machine_restart and _machine_haltSander Vanheule2021-11-241-85/+0
| | | | | | | | | | | | | | By dropping _machine_restart, users can provide more reliable or device-specific restart modes. _machine_halt was already removed in commit f4b687d1f053 ("realtek: use kernel defined halt"), but quietly reintroduced in commit 8faffa00cb6b ("realtek: add support for the RTL9300 timer"). Let's remove it again. Signed-off-by: Sander Vanheule <sander@svanheule.net> Tested-by: Stijn Segers <foss@volatilesystems.org> Tested-by: Paul Fertser <fercerpav@gmail.com> Tested-by: Stijn Tintel <stijn@linux-ipv6.be>
* realtek: Add and enable watchdog nodeSander Vanheule2021-11-243-1/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Add and enable the Realtek Otto WDT peripheral found on these SoCs. Default all devices to use standard (cold) reboot and "soc" resets. Devices that require the PLL value fixup before restarting, should pick the "cpu" or "software" reset mode. These devices also need to provide a custom reboot mode, by adding the reboot argument to the kernel command line: WDT reset mode | kernel reboot mode ----------------+--------------------------------------- soc | reboot=cold (default if not specified) cpu | reboot=warm software | reboot=software Preferrably, these devices should use an alternative restart method like gpio-restart to provide reliable restarts. Note that watchdog restarts are not yet exposed, since the _machine_restart override is still present. Signed-off-by: Sander Vanheule <sander@svanheule.net> Tested-by: Stijn Segers <foss@volatilesystems.org> Tested-by: Paul Fertser <fercerpav@gmail.com> Tested-by: Stijn Tintel <stijn@linux-ipv6.be>
* realtek: Backport Realtek Otto WDT driverSander Vanheule2021-11-243-0/+486
| | | | | | | | | | | Add patch submitted upstream to linux-watchdog and replace the MIPS architecture symbols. Requires one extra patch for the DIV_ROUND_* macros, which have moved to a different header since 5.10. Signed-off-by: Sander Vanheule <sander@svanheule.net> Tested-by: Stijn Segers <foss@volatilesystems.org> Tested-by: Paul Fertser <fercerpav@gmail.com> Tested-by: Stijn Tintel <stijn@linux-ipv6.be>
* realtek: Add Lexra bus clockSander Vanheule2021-11-242-8/+13
| | | | | | | | | | | | | | | | | The CPU peripherals on RTL83xx/RTL930x are connected to the CPU via the Lexra bus. This bus can provide a clock signal to these peripherals, but no clock driver is currently available. Instead, use a fixed-clock to provide the clock frequency, and update the dependent peripherals. Lexra bus clock frequencies: - RTL838x: 200MHz - RTL839x: 200MHz - RTL930x: 175MHz Signed-off-by: Sander Vanheule <sander@svanheule.net> Tested-by: Stijn Segers <foss@volatilesystems.org> Tested-by: Paul Fertser <fercerpav@gmail.com> Tested-by: Stijn Tintel <stijn@linux-ipv6.be>
* realtek: Consolidate bootargsSander Vanheule2021-11-248-26/+2
| | | | | | | | | | All current devices use identical bootargs, so let's move that to the common devicetree includes. Signed-off-by: Sander Vanheule <sander@svanheule.net> Tested-by: Stijn Segers <foss@volatilesystems.org> Tested-by: Paul Fertser <fercerpav@gmail.com> Tested-by: Stijn Tintel <stijn@linux-ipv6.be>
* realtek: reset both ethernet NIC and queuesSander Vanheule2021-11-241-4/+7
| | | | | | | | | | | | | | | Recent versions of Realtek's SDK reset both the ethernet NIC and queues (SW_NIC_RST and SW_Q_RST bits) when initialising the hardware. Furthermore, when issuing a CPU reset on the Zyxel GS1900-8 (not supported by any current driver), the networking part of the SoC is not reset. This leads to unresponsive network after the restart. By resetting both the ethernet NIC and queues, networking always comes up reliably. Suggested-by: Birger Koblitz <mail@birger-koblitz.de> Signed-off-by: Sander Vanheule <sander@svanheule.net> Tested-by: Stijn Tintel <stijn@linux-ipv6.be>
* bcm53xx: fix platform clocks & USB 2.0 PHYRafał Miłecki2021-11-231-0/+62
| | | | | | | | This fixes WARNing, missing clocks and [ 10.422481] bcm_ns_usb2 1800c164.usb2-phy: Clock not defined Fixes: 5901917b936d ("bcm53xx: use more upsteam DT patches from 5.16 / 5.17") Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: use new USB 2.0 PHY bindingRafał Miłecki2021-11-232-0/+183
| | | | | | | | | | | This fixes: [ 10.440495] bcm_ns_usb2 1800c000.usb2-phy: can't request region for resource [mem 0x1800c000-0x1800cfff] [ 10.450039] bcm_ns_usb2 1800c000.usb2-phy: Failed to map DMU regs [ 10.456183] bcm_ns_usb2: probe of 1800c000.usb2-phy failed with error -16 caused by conflict in allocating resources. Fixes: f55f1dbaad33 ("bcm53xx: switch to the kernel 5.10") Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* Revert "ath79: add support for Mikrotik LHG 5"Hauke Mehrtens2021-11-236-177/+0
| | | | | | | | This reverts commit 48774decea9b42e97edd53ce33e574de7d85f3df. This commit does not contain a valid name in the Signed-off-by line. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* bcm53xx: specify switch ports on TP-LINK devicesRafał Miłecki2021-11-221-0/+92
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* tools/llvm-bpf: move tarball packing to target/llvm-bpfFelix Fietkau2021-11-222-2/+36
| | | | | | | This ensures that the tarball is regenerated after make clean or after switching to a different target Signed-off-by: Felix Fietkau <nbd@nbd.name>
* sunxi: build kernel with sun6i-rtc driverDaniel Golle2021-11-212-0/+2
| | | | | | | | | | | | | | | | | sun6i-rtc cannot be built as a module and the hardware is only present in some of the sunxi SoCs, see driver source: { .compatible = "allwinner,sun6i-a31-rtc" }, { .compatible = "allwinner,sun8i-a23-rtc" }, { .compatible = "allwinner,sun8i-h3-rtc" }, { .compatible = "allwinner,sun8i-r40-rtc" }, { .compatible = "allwinner,sun8i-v3-rtc" }, { .compatible = "allwinner,sun50i-h5-rtc" }, { .compatible = "allwinner,sun50i-h6-rtc" }, Set CONFIG_RTC_DRV_SUN6I=y in kernel config file for cortexa7 and cortexa53 subtargets which covers all of the above. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* Revert "sunxi: add rtc-sun6i driver package"Daniel Golle2021-11-211-18/+0
| | | | | | | sun6i-rtc is a builtin_platform_driver and cannot be built as a module. Hence this reverts commit e178d9a5494747a9b6ea34f2fc9e798b4b1ecc16. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* ramips: fix ralink_i2s_debugfs_remove declarationEneas U de Queiroz2021-11-202-2/+2
| | | | | | | Correct ralink_i2s_debugfs_remove declaration in ralink patches when CONFIG_DEBUG_FS is not selected. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* ramips: use lzma-loader on D-Link DIR-615 H1Mirko Parthey2021-11-201-0/+1
| | | | | | | Fixes the boot loader LZMA decompression issue: LZMA ERROR 1 - must RESET board to recover Signed-off-by: Mirko Parthey <mirko.parthey@web.de>
* ramips: add support for Wavlink WL-WN576A2Thomas Aldrian2021-11-204-2/+201
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit adds support for the Wavlink WL-WN576A2 wall-plug wireles repeater / router. It is also sold under the name SilverCrest SWV 733 B1. Device specs: - CPU: MediaTek MT7628AN - Flash: 8MB - RAM: 64MB - Bootloader: U-Boot - Ethernet: 1x 10/100 Mbps - 2.4 GHz: b/g/n SoC - 5 GHz: a/n/ac MT7610EN - Buttons: WPS, reset, sliding switch (ap/repeater) - LEDs: 5x wifi status, 1x LAN/WAN, 1x WPS Flashing: U-Boot launches a TFTP client if WPS button is held during boot. - Server IP: 192.168.10.100 - Firmware file name: firmware.bin Device will reboot automatically. First boot takes about 90s. Coelner (waenger@gmail.com) is the original author, but I have made some fixes. He does not wish to sign off using his real name. Signed-off-by: Thomas Aldrian <dev.aldrian@gmail.com>
* ath79: merge D-Link DAP-2695 with dtsiSebastian Schaper2021-11-202-81/+25
| | | | | | | | | | | | Further devices from the series have been added in the meantime, introducing `qca955x_dlink_dap-2xxx.dtsi`. Thus, merge support for DAP-2695 with the existing dtsi. This implies factory images can now be flashed via the regular OEM Web UI, as well as the bootloader recovery. Signed-off-by: Sebastian Schaper <openwrt@sebastianschaper.net>
* ath79: move cal-data extraction to dts for DAP-2695Sebastian Schaper2021-11-203-5/+2
| | | | | | | | | | This device can be merged with the existing dtsi, which declares the location of ath9k cal-data via devicetree, correcting the 2.4G mac address in `10_fix_wifi_mac` rather than `10-ath9k-eeprom`. To make these changes more visible, apply before merging with dtsi. Signed-off-by: Sebastian Schaper <openwrt@sebastianschaper.net>
* ath79: increase SPI frequency for D-Link DAP-2695Sebastian Schaper2021-11-201-1/+1
| | | | | | | | | This device can be merged with the existing dtsi, which will increase spi-max-frequency to 50 MHz. To make this change more visible, increase to 50 MHz before merging. Signed-off-by: Sebastian Schaper <openwrt@sebastianschaper.net>
* omap: switch to kernel 5.10Andre Heider2021-11-201-1/+1
| | | | Signed-off-by: Andre Heider <a.heider@gmail.com>
* omap: update kernel 5.10 configAndre Heider2021-11-201-88/+29
| | | | | | | | | | | | | | | | | | | Manually set toggles are: MMC_SDHCI_OMAP=y TI_PRUSS_INTC=y DRM_TI_TPD12S015=y (successor to DRM_OMAP_ENCODER_TPD12S015 [0] [1]) DRM_DISPLAY_CONNECTOR=y (for DRM_TI_TPD12S015 [1]) DRM_SIMPLE_BRIDGE=y (for DRM_TI_TPD12S015 [1]) Manually unset toggles are: SND_MIXER_OSS=y (disabled by generic config) The rest was automatically modified by the kernel_oldconfig make target. [0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cff5e6f7e83f6271ed75972e9a2920e2c7f62d6c [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e7e67d9a2f1dd2f938adcc219b3769f5cc3f0df7 Signed-off-by: Andre Heider <a.heider@gmail.com>
* omap: copy kernel 5.4 config for 5.10Andre Heider2021-11-201-0/+740
| | | | Signed-off-by: Andre Heider <a.heider@gmail.com>
* ath79: add support for Mikrotik LHG 5Jakob (Jack/XDjackieXD)2021-11-206-0/+177
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The MikroTik LHG 5 series (product codes RBLHG-5nD, RBLHG-5HPnD and RBLHG-5HPnD-XL) devices are an outdoor 5GHz CPE with a 24.5dBi or 27dBi integrated antenna built around the Atheros AR9344 SoC. It is very similar to the SXT Lite5 series which this patch is based upon. Specifications: - SoC: Atheros AR9344 - RAM: 64 MB - Storage: 16 MB SPI NOR - Wireless: Atheros AR9340 (SoC) 802.11a/n 2x2:2 - Ethernet: Atheros AR8229 switch (SoC), 1x 10/100 port, 8-32 Vdc PoE in - 8 user-controllable LEDs: - 1x power (blue) - 1x user (white) - 1x ethernet (green) - 5x rssi (green) See https://mikrotik.com/product/RBLHG-5nD for more details. Notes: The device was already supported in the ar71xx target. Flashing: TFTP boot initramfs image and then perform a sysupgrade. Follow common MikroTik procedure as in https://openwrt.org/toh/mikrotik/common. Signed-off-by: Jakob (Jack/XDjackieXD) <jakob@chaosfield.at>
* sunxi: add rtc-sun6i driver packageZhao Yu2021-11-201-0/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | AP6212 wifi need wifi_pwrseq, but from OrangePi Lite 2 dts : wifi_pwrseq: wifi_pwrseq { compatible = "mmc-pwrseq-simple"; clocks = <&rtc 1>; clock-names = "ext_clock"; reset-gpios = <&r_pio 1 3 GPIO_ACTIVE_LOW>; /* PM3 */ post-power-on-delay-ms = <200>; }; this pwrseq need rtc clock, or kernel won't find this device. but now rtc-sunxi.c only support A10/A20. Orangepi Lite 2 use H6 ,from rtc-sun6i.c show compatible is { .compatible = "allwinner,sun6i-a31-rtc" }, { .compatible = "allwinner,sun8i-a23-rtc" }, { .compatible = "allwinner,sun8i-h3-rtc" }, { .compatible = "allwinner,sun8i-r40-rtc" }, { .compatible = "allwinner,sun8i-v3-rtc" }, { .compatible = "allwinner,sun50i-h5-rtc" }, { .compatible = "allwinner,sun50i-h6-rtc" }, So it need this to let kernel find this mmc wifi device. As suggested by hauke, let it build as package. Signed-off-by: Zhao Yu <574249312@qq.com>
* ath79: mikrotik: enable USB module on RouterBoard wAPR-2nDRoger Pueyo Centelles2021-11-202-1/+9
| | | | | | | | | | | The MikroTik RouterBOARD wAPR-2nD (wAP R) router features a miniPCI-e slot with USB lines connected, which are used by some USB cards with miniPCI-e form factor, like the R11e-LR8. Enabling USB support is required for such cards to work. Tested on a MikroTik wAP LR8 kit (RB wAPR-2nD + R11e-LR8). Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
* octeon: add USB3 support (for Ubiquiti EdgeRouter 6P)Laurent DEBOMY2021-11-202-0/+4
| | | | | | Fixes: FS#4086 Signed-off-by: Laurent DEBOMY <laurent.debomy@canal-belletrud.fr>
* mvebu: backport mvneta basic MQPrio patchKabuli Chana2021-11-201-0/+109
| | | | | | | Implement a basic MQPrio support, inserting rules in RX that translate the TC to prio mapping into vlan prio to queues. Signed-off-by: Kabuli Chana <newtownBuild@gmail.com>
* kernel: bump 5.4 to 5.4.159John Audia2021-11-203-6/+6
| | | | | | | | | Manually rebased: generic-backport/850-v5.13-usb-ehci-add-spurious-flag-to-disable-overcurrent-ch.patch All other patches automatically rebased. Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: remove non-existent config symbolsJianhui Zhao2021-11-202-2/+0
| | | | | | | The crashlog patch as not ported to kernel 5.4. Fixes: 4e0c54bc5bc8 ("kernel: add support for kernel 5.4") Signed-off-by: Jianhui Zhao <zhaojh329@gmail.com>
* mediatek/mt7622: unifi-6-lr: fix ucidef network configuration typoMark Mentovai2021-11-191-1/+1
| | | | | | | | There's no such thing as ucidef_set_interfaces_lan. It's ucidef_set_interface_lan. Cc: David Bauer <mail@david-bauer.net> Signed-off-by: Mark Mentovai <mark@moxienet.com>
* bcm4908: build chk image for Netgear RAXE500Rafał Miłecki2021-11-191-1/+1
| | | | | Fixes: 63ba3eaccdde ("bcm4908: start working on Netgear RAXE500 image") Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm4908: start working on Netgear RAXE500 imageRafał Miłecki2021-11-192-0/+36
| | | | | | | | bootfs still needs more work before it's ready. For some unknown reason model RAXE500 uses board id RAX220. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm4908: enable MTD_CMDLINE_PARTSRafał Miłecki2021-11-192-0/+2
| | | | | | | It's needed to support devices with U-Boot. That bootloader passes MTD layout using cmdline. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>