aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* kernel: Add missing devm_regulator_get_exclusive()Hauke Mehrtens2022-05-171-0/+79
| | | | | | | | | | | This backports a patch from Linux 5.10.116 to fix a compile problem introduced in 5.10.114. drivers/usb/phy/phy-generic.c could not find devm_regulator_get_exclusive(). Fixes: 8592df67f40b ("kernel: bump 5.10 to 5.10.114") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 5.15 to 5.15.40John Audia2022-05-166-12/+7
| | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: bcm2711/RPi4B, mt7622/RT3200 Run-tested: bcm2711/RPi4B, mt7622/RT3200 Signed-off-by: John Audia <therealgraysky@proton.me>
* kernel: bump 5.15 to 5.15.39John Audia2022-05-1633-1824/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Removed upstreamed: backport-5.15/850-v5.17-0001-PCI-pci-bridge-emul-Add-description-for-class_revisi.patch backport-5.15/850-v5.17-0002-PCI-pci-bridge-emul-Add-definitions-for-missing-capa.patch backport-5.15/850-v5.17-0003-PCI-aardvark-Add-support-for-DEVCAP2-DEVCTL2-LNKCAP2.patch backport-5.15/850-v5.17-0004-PCI-aardvark-Clear-all-MSIs-at-setup.patch backport-5.15/850-v5.17-0005-PCI-aardvark-Comment-actions-in-driver-remove-method.patch backport-5.15/850-v5.17-0006-PCI-aardvark-Disable-bus-mastering-when-unbinding-dr.patch backport-5.15/850-v5.17-0007-PCI-aardvark-Mask-all-interrupts-when-unbinding-driv.patch backport-5.15/850-v5.17-0008-PCI-aardvark-Fix-memory-leak-in-driver-unbind.patch backport-5.15/850-v5.17-0009-PCI-aardvark-Assert-PERST-when-unbinding-driver.patch backport-5.15/850-v5.17-0010-PCI-aardvark-Disable-link-training-when-unbinding-dr.patch backport-5.15/850-v5.17-0011-PCI-aardvark-Disable-common-PHY-when-unbinding-drive.patch pending-5.15/850-0001-PCI-aardvark-Replace-custom-PCIE_CORE_INT_-macros-wi.patch pending-5.15/850-0004-PCI-aardvark-Rewrite-IRQ-code-to-chained-IRQ-handler.patch pending-5.15/850-0005-PCI-aardvark-Check-return-value-of-generic_handle_do.patch pending-5.15/850-0006-PCI-aardvark-Make-MSI-irq_chip-structures-static-dri.patch pending-5.15/850-0007-PCI-aardvark-Make-msi_domain_info-structure-a-static.patch pending-5.15/850-0008-PCI-aardvark-Use-dev_fwnode-instead-of-of_node_to_fw.patch pending-5.15/850-0009-PCI-aardvark-Refactor-unmasking-summary-MSI-interrup.patch pending-5.15/850-0010-PCI-aardvark-Add-support-for-masking-MSI-interrupts.patch pending-5.15/850-0011-PCI-aardvark-Fix-setting-MSI-address.patc pending-5.15/850-0012-PCI-aardvark-Enable-MSI-X-support.patch pending-5.15/850-0013-PCI-aardvark-Add-support-for-ERR-interrupt-on-emulat.patch pending-5.15/850-0015-PCI-aardvark-Optimize-writing-PCI_EXP_RTCTL_PMEIE-an.patch pending-5.15/850-0016-PCI-aardvark-Add-support-for-PME-interrupts.patch pending-5.15/850-0017-PCI-aardvark-Fix-support-for-PME-requester-on-emulat.patch pending-5.15/850-0018-PCI-aardvark-Use-separate-INTA-interrupt-for-emulate.patch pending-5.15/850-0019-PCI-aardvark-Remove-irq_mask_ack-callback-for-INTx-i.patch pending-5.15/850-0020-PCI-aardvark-Don-t-mask-irq-when-mapping.patch pending-5.15/850-0021-PCI-aardvark-Drop-__maybe_unused-from-advk_pcie_disa.patch pending-5.15/850-0022-PCI-aardvark-Update-comment-about-link-going-down-af.patch All patches automatically rebased. Build system: x86_64 Build-tested: bcm2711/RPi4B, mt7622/RT3200 Run-tested: bcm2711/RPi4B, mt7622/RT3200 Signed-off-by: John Audia <therealgraysky@proton.me>
* kernel: bump 5.10 to 5.10.115John Audia2022-05-1628-161/+45
| | | | | | | | | | | | | Removed upstreamed: backport-5.10/850-v5.17-0004-PCI-aardvark-Clear-all-MSIs-at-setup.patch pending-5.10/850-0002-PCI-aardvark-Fix-reading-MSI-interrupt-number.patch All other patches automatically rebased. Build system: x86_64 Build-tested: bcm2711/RPi4B Signed-off-by: John Audia <therealgraysky@proton.me>
* kernel: bump 5.10 to 5.10.114John Audia2022-05-1617-32/+32
| | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: bcm2711/RPi4B Run-tested: bcm2711/RPi4B Signed-off-by: John Audia <therealgraysky@proton.me>
* ramips: Add support for SERCOMM NA502SAndreas Böhler2022-05-164-0/+379
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The SERCOMM NA502s is a smart home gateway manufactured by SERCOMM and sold under different brands (among others, A1 Telekom Austria SmartHome Premium Gateway). It has multi-protocol radio support in addition to LAN and WiFi. Note: BLE and audio are currently unsupported. Specifications -------------- - MT7621ST 880MHz, Single-Core, Dual-Thread - MT7603EN 2.4GHz WiFi - MT7662EN 5GHz WiFi + BLE - 128MiB NAND - 256MiB DDR3 RAM - SD3503 ZWave Controller - EM357 Zigbee Coordinator - Telit UMTS module - Rechargeable battery - speaker and microphone MAC address assignment ---------------------- LAN MAC is read from the config partition, WiFi 2.4GHz is LAN+2 and matches the OEM firmware. WiFi 5GHz with LAN+1 is an educated guess since the OEM firmware does not enable 5GHz WiFi. Installation ------------ Attach serial console, then boot the initramfs image via TFTP. Once inside OpenWrt, run sysupgrade -n with the sysupgrade file. Attention: The device has a dual-firmware design. We overwrite kernel2, since kernel1 contains an automatic recovery image. If you get NAND ECC errors and are stuck with bad eraseblocks, try to erase the mtd partition first with mtd unlock ubi mtd erase ubi This should only be needed once. Signed-off-by: Andreas Böhler <dev@aboehler.at>
* ramips: add led_source for Asus RT-AC1200 devicesTamas Balogh2022-05-151-0/+1
| | | | | | | | | | | | | | | this adds the mediatek,led_source dts binding for Asus RT-AC1200 devices' dtsi, for correct switch LED behavior. The dts-binding is introduced in commit: 65dc9e0980255b15402c45b840f239b85be59b3d Without this, we only have constantly very fast blinking LEDs, which don't react on any traffic or LAN events at all. Signed-off-by: Tamas Balogh <tamasbalogh@hotmail.com>
* wolfssl: bump to v5.3.0-stableEneas U de Queiroz2022-05-153-45/+2
| | | | | | | | | This is mostly a bug fix release, including two that were already patched here: - 300-fix-SSL_get_verify_result-regression.patch - 400-wolfcrypt-src-port-devcrypto-devcrypto_aes.c-remove-.patch Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* IPQ4019: AVM FRITZ!Box 7530: Remove NAND ECC restrictions from DTSAndreas Böhler2022-05-151-0/+3
| | | | | | | | | Some revisions of the FRITZ!7530 use a Toshiba NAND with 8 bit ECC in contrast to the Macronix NAND with 4 bit ECC. This removes the hardcoded ECC strength and step size as set in qcom-ipq4019.dtsi, thus relying on the kernel NAND detection routines to correclty set up the ECC parameters. Signed-off-by: Andreas Böhler <dev@aboehler.at>
* kernel: add support for Toshiba TC58NVG0S3HTA00 NAND flashAndreas Böhler2022-05-152-0/+72
| | | | | | | The Toshiba TC58NVG0S3HTA00 is detected with 64 byte OOB while the flash has 128 byte OOB. This adds a static NAND ID entry to correct this. Signed-off-by: Andreas Böhler <dev@aboehler.at>
* openssl: bump to 1.1.1oEneas U de Queiroz2022-05-152-6/+6
| | | | | | | | | | This release comes with a security fix related to c_rehash. OpenWrt does not ship or use it, so it was not affected by the bug. There is a fix for a possible crash in ERR_load_strings() when configured with no-err, which OpenWrt does by default. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* util-linux: use meson to buildRosen Penev2022-05-1516-51/+384
| | | | | | | | | Compiles faster, is PIC by default, and does not have pkgconfig files with wrong paths. Add various fixes to it as it seems cross compilation was never tested. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* util-linux: update to 2.38Rosen Penev2022-05-151-3/+3
| | | | | | Various fixes. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* ath79: ZTE MF286[A,R]: add "Power button blocker" GPIO switchLech Perczak2022-05-151-0/+20
| | | | | | | | | | | | | | | ZTE MF286A and MF286R feature a "power switch override" GPIO in stock firmware as means to prevent power interruption during firmware update, especially when used with internal battery. To ensure that this GPIO is properly driven as in stock firmware, configure it with userspace GPIO switch. It was observed that on some units, the modem would not be restarted together with the board itself on reboot, this should help with that as well. Signed-off-by: Lech Perczak <lech.perczak@gmail.com>
* ipq40xx: revert Cell-C RTL30VW to legacy caldata extractionPawel Dembicki2022-05-152-15/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This partially reverts commit cfc13c44595d ("ipq40xx: utilize nvmem-cells for macs & (pre-)calibration data"). After switching to nvmem RTL30VW, wifi was broken: [ 19.118319] ath10k_ahb a000000.wifi: qca4019 hw1.0 target 0x01000000 chip_id 0x003b00ff sub 0000:0000 [ 19.118377] ath10k_ahb a000000.wifi: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0 [ 19.130285] ath10k_ahb a000000.wifi: firmware ver 10.4b-ct-4019-fW-13-5ae337bb1 api 5 features mfp,peer-flow-ctrl,txstatus-noack,wmi-10.x-CT,ratemask-CT,regdump-CT,txrate-CT,flush-all-CT,pingpong-CT,ch-regs-CT,nop-CT,set-special-CT,tx-rc-CT,cust-stats-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT,wmi-bcn-rc-CT crc32 6b2b5c5b [ 19.159092] ath10k_ahb a000000.wifi: failed to fetch board data for bus=ahb,vendor=0000,device=0000,subsystem-vendor=0000,subsystem-device=0000,variant=cellc,rtl30vw from ath10k/QCA4019/hw1.0/board-2.bin [ 19.238764] ath10k_ahb a000000.wifi: failed to fetch board-2.bin or board.bin from ath10k/QCA4019/hw1.0 [ 19.238847] ath10k_ahb a000000.wifi: failed to fetch board file: -12 [ 19.247362] ath10k_ahb a000000.wifi: could not probe fw (-12) [ 20.190797] ath10k_ahb a800000.wifi: qca4019 hw1.0 target 0x01000000 chip_id 0x003b00ff sub 0000:0000 [ 20.190853] ath10k_ahb a800000.wifi: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0 [ 20.202893] ath10k_ahb a800000.wifi: firmware ver 10.4b-ct-4019-fW-13-5ae337bb1 api 5 features mfp,peer-flow-ctrl,txstatus-noack,wmi-10.x-CT,ratemask-CT,regdump-CT,txrate-CT,flush-all-CT,pingpong-CT,ch-regs-CT,nop-CT,set-special-CT,tx-rc-CT,cust-stats-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT,wmi-bcn-rc-CT crc32 6b2b5c5b [ 20.231357] ath10k_ahb a800000.wifi: failed to fetch board data for bus=ahb,vendor=0000,device=0000,subsystem-vendor=0000,subsystem-device=0000,variant=cellc,rtl30vw from ath10k/QCA4019/hw1.0/board-2.bin [ 20.317318] ath10k_ahb a800000.wifi: failed to fetch board-2.bin or board.bin from ath10k/QCA4019/hw1.0 [ 20.317399] ath10k_ahb a800000.wifi: failed to fetch board file: -12 [ 20.326098] ath10k_ahb a800000.wifi: could not probe fw (-12) Bootloader mangles in NAND partitions and removes precal@X nodes in working system: root@OpenWrt:~# echo $(cat /sys/firmware/devicetree/base/soc/spi@78b5000/flash@0/partitions/partition@170000/label) 0:ART root@OpenWrt:~# ls /sys/firmware/devicetree/base/soc/spi@78b5000/flash@0/partitions/partition@170000/ label name reg Revert to legacy method fixed the problem. Fixes: cfc13c44595d ("ipq40xx: utilize nvmem-cells for macs & (pre-)calibration data") Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* ath79: fix I2C on GL-AR300M devicesPtilopsis Leucotis2022-05-151-0/+9
| | | | | | | | | | | On GL-AR300M Series GPIO17 described as I2C SDA in Device Tree. Because of GPIO_OUT_FUNCTION4 register was not initialized on start, GPIO17 was uncontrollable, it always in high state. According to QCA9531 documentation, default setting of GPIO17 is SYS_RST_L. In order to make GPIO17 controllable, it should write value 0x00 on bits [15:8] of GPIO_OUT_FUNCTION4 register, located at 0x1804003C address. Signed-off-by: Ptilopsis Leucotis <PtilopsisLeucotis@yandex.com>
* libubox: update to the latest versionFelix Fietkau2022-05-151-3/+3
| | | | | | | | | f2d6752901f2 blob: clear buf->head when freeing a buffer 45210ce14136 list.h: add container_of_safe macro cfa372ff8aed blobmsg: implicitly reserve space for 0-terminator in string buf alloc d2223ef9da71 blobmsg: work around false positive gcc -Warray-bounds warnings Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mpc85xx: enable error reporting for RAM and PCIeJosef Schlehofer2022-05-141-0/+4
| | | | | | | | | | | | | | | | | | | | All Freescale processors used in this target are capable to detect error and correction. [1] It can not be used as kernel module. [2] This is helpful to report hardware errors. It enables three kernel options: - EDAC, which is a subsystem - EDAC_LEGACY_SYSFS, it enables sysfq nodes - MP85XX, support for Freescale MPC8349, MPC8560, MPC8540, MPC8548, T4240 EDAC is already enabled for following targets: qoriq, octeon, octeontx and zynq. [1] https://cateee.net/lkddb/web-lkddb/EDAC.html [2] https://patchwork.ozlabs.org/patch/554908/ Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* uboot-fritz4040: Add support for Toshiba NANDChristian Lamparter2022-05-141-3/+3
| | | | | | | | | | | | From Andreas Böhler: "Some revisions of the FRITZ!7530 use a Toshiba NAND with 8 bit ECC in contrast to the Macronix NAND with 4 bit ECC.". Uboot needs to know this in order to have a chance to load from the NAND. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq-wifi: drop upstreamed board-2.binChristian Lamparter2022-05-1428-59/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The BDFs for the: Aruba AP-303 ASUS RT-AC42U AVM FRITZ!Repeater 1200 Buffalo WTR-M2133HP Cell C RTL30VW D-Link DAP-2610 EnGenius EAP2200 EnGenius EMD1 EnGenius EMR3500 EnGenius EMR5000 EZVIZ CS-W3-WD1200G EUP Google Wifi Linksys MR8300 V1.0 Luma WRTQ-329ACN MobiPromo CM520-79F NEC Platforms WG2600HP3 Plasma Cloud PA1200 (updated version) Plasma Cloud PA2200 ZTE MF286D were upstreamed to the ath10k-firmware repository and landed in linux-firmware.git. Furthermore the BDFs for the: 8devices Habanero OpenMesh A62 OpenMesh A42 AVM FRITZ!Box 4040 have been updated. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* linux-firmware: take linux-firmware.git's qca99x0 boardfileChristian Lamparter2022-05-141-12/+1
| | | | | | | | Kalle Valo managed to add the qca9980's boardfile in the upstream repository. Sourcing the file from his repository is no longer needed. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* linux-firmware: Update to version 20220509Christian Lamparter2022-05-141-2/+2
| | | | | | | | | | | | | | | | | | | | | | git log --pretty=oneline --abbrev-commit 20220411..20220509 (sorted) amdgpu: 480d6c2 amdgpu: update dcn_3_1_6_dmcub firmware b4994be amdgpu: update gc_10_3_7_rlc firmware 61eb408 amdgpu: update psp_13_0_8 firmware fcf9d8c amdgpu: update yellow carp DMCUB firmware ath10k: 73743b8 ath10k: QCA4019 hw1.0: update board-2.bin 6ad0930 ath10k: QCA6174 hw3.0: update board-2.bin 729bd7f ath10k: QCA6174 hw3.0: update firmware-6.bin to WLAN.RM.4.4.1-00288-QCARMSWPZ-1 9fce09f ath10k: QCA9888 hw2.0: update board-2.bin b155d85 ath10k: QCA9888 hw2.0: update firmware-5.bin to 10.4-3.9.0.2-00156 44b8aee ath10k: QCA9984 hw1.0: update board-2.bin 4ad3bd3 ath10k: QCA9984 hw1.0: update firmware-5.bin to 10.4-3.9.0.2-00156 1962cba ath10k: QCA99X0 hw2.0: add board-2.bin Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: Lyra: update RGB LED-Controller node for 5.10+Christian Lamparter2022-05-142-47/+78
| | | | | | | | | | | | | | | | | | | | | | Add the reg and color property to each channel node. This update is to accommodate the multicolor framework. Refer to: <https://lore.kernel.org/all/20200622185919.2131-9-dmurphy@ti.com> <https://lore.kernel.org/all/20210818070209.1540451-1-michal.vokac@ysoft.com> Note: There is only a single extremely bright RGB-LED. The RGB-color channels (i.e.: blue-0, blue-1 and blue-2) are running in parallel to increase the current delivery beyond what a single PWM-output on the LED controller could do. BugLink: https://github.com/openwrt/openwrt/issues/9851 Reported-By: Thomas Bøge <thomas@boegenielsen.dk> Tested-By: Thomas Bøge <thomas@boegenielsen.dk> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: use nested fixed-partitionsChristian Lamparter2022-05-142-24/+47
| | | | | | | | This makes it possible to fix Netgear WNDAP620+660 DTS ugliness. Bring back the dtb and firmware partitions for the WNDR4700. Thank you, mans0n. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* bcm53xx: remove MR32's specific get_leds_dt codeChristian Lamparter2022-05-142-31/+0
| | | | | | | the existing diag.sh code will pick up the LED by itself. This is not/no longer needed. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* lantiq: xway: disable unused switch driversAleksander Jan Bajkowski2022-05-141-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | None of the devices supported by target xway are using Realtek RTL8366S, RTL8367A and RTL8367B switches. The switches mentioned earlier were enabled when bumping the kernel version to 3.7 in commit 3a948770cf46 ("add linux-v3.7"). Switches used by individual devices are listed below. Device Switch PHY Arcadyan ARV4510PW Infineon ADM6996I int. switch Arcadyan ARV4519PW Atheros AR8216 int. switch Arcadyan ARV7506PW11 Realtek RTL8306G int. switch Arcadyan ARV7510PW22 Atheros AR8216 int. switch Arcadyan ARV7518PW Atheros AR8216 int. switch Arcadyan ARV7519PW Atheros RTL8306G int. switch Arcadyan ARV7525PW N/A IC+ IP101A Arcadyan ARV752DPW Realtek RTL8306G int. switch Arcadyan ARV752DPW22 Atheros AR8216 int. switch Arcadyan ARV8539PW22 Atheros AR8216 int. switch AVM Fritzbox 7312 int. SoC Atheros AR8030-A AVM Fritzbox 7320 int. SOC Lantiq PEF7071V AudioCodes MediaPack MP-252 Infineon ADM6996I int. switch BT Home Hub 2B Infineon ADM6996I int. switch BT Home Hub 3A Infineon PSB6972 Lantiq PEF7071V Buffalo WBMR-HP-G300H-A Atheros AR8316 int. switch Buffalo WBMR-HP-G300H-B Atheros AR8316 int. switch Lantiq EASY50712 Infinein ADM6996I int. switch Netgear DGN3500 Realtek RTL8366RB int. switch Netgear DGN3500B Realtek RTL8366RB int. switch Siemens Gigaset sx76x Infineon ADM6996I int. switch ZTE H201L Realtek RTL8306G int. switch ZyXEL P-2601HN-F1 Realtek RTL8306E int. switch ZyXEL P-2601HN-F3 Realtek RTL8306E int. switch Reduces uncompressed kernel size by 36 kB. Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl> Acked-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> (checkpatch.pl fixes) Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ramips: fix booting on Samknows SK-WB8Piotr Dymacz2022-05-131-0/+1
| | | | | | | | This fixes a well known "LZMA ERROR 1" error, reported previously on numerous of similar devices. Fixes: #9824 Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* image: drop unused 'BuildKernel/MkFIT'Piotr Dymacz2022-05-121-8/+0
| | | | | | The 'MkFIT' recipe is no longer used across whole codebase. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* realtek: do not reset SerDes on link changeBirger Koblitz2022-05-112-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Do not reset the RTL930x SerDes on link changes, instead set up the SDS with internal PHYs for the SFP+ ports only. This fixes the 8 1GBit ports on the Zyxel XGS1250 which do not work without this patch. A complete SerDes reset was performed on all SerDes links. For copper 1Gbit ports, this is commonly a single XGMII link to an RTL8218D. There is however no support for setting up the XGMII link on RTL9300/RTL9310, thereby wiping the (RX/TX) setup done by u-boot and breaking the 1GBit ports. No SerDes reset should be done for these links. The handling of SGMII/HiSGMII, 1000BX or 10GR links is actually entirely different. All these modes need to be suitably RX calibrated and the pre- main and post- amplifiers set up properly for TX. The 10GBit SFP+ fiber links are recalibrated instead of reset, which e.g. is necessary when someone pulls a module out and puts another in. This makes swapping out 10GBit fiber modules possible. 1GBit modules are not yet supported, nor any modules with an internal phy. Tested-by: Stijn Segers <foss@volatilesystems.org> Signed-off-by: Birger Koblitz <git@birger-koblitz.de> [rewrite commit message based on discussion] Link: http://lists.infradead.org/pipermail/openwrt-devel/2022-May/038623.html Signed-off-by: Sander Vanheule <sander@svanheule.net>
* kernel: bump 5.15 to 5.15.38Rui Salvaterra2022-05-097-101/+13
| | | | | | | | | | | Deleted (upstreamed): mediatek/patches-5.15/120-10-v5.18-mtd-nand-fix-ecc-parameters-for-mt7622.patch [1] Other patches automatically rebased. [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.15.38&id=3ec920d755ae69c201b358e8d8e96c32f51145d8 Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* kernel: bump 5.15 to 5.15.37Rui Salvaterra2022-05-092-3/+3
| | | | | | Patches automatically rebased. Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* kernel: bump 5.15 to 5.15.36Rui Salvaterra2022-05-0912-28/+28
| | | | | | Patches automatically rebased. Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* ramips: add support for Cudy X6Alessio Prescenzo2022-05-093-0/+192
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Specifications: SoC: MediaTek MT7621 RAM: 256 MB Flash: 32 MB WiFi: MediaTek MT7915E Switch: 1 WAN, 4 LAN (Gigabit) Ports: 1 USB 3.0 Buttons: Reset, WPS LEDs: Power, System, Wan, Lan 1-4, WiFi 2.4G, WiFi 5G, WPS, USB Power: DC 12V 1A tip positive Installation: Download and flash the manufacturer's built OpenWRT image available at http://www.cudytech.com/openwrt_software_download Install the new OpenWRT image via luci (System -> Backup/Flash firmware) Be sure to NOT keep settings. The force upgrade may need to be checked due to differences in router naming conventions. Recovery: Loads only signed manufacture firmware due to bootloader RSA verification serve tftp-recovery image as /recovery.bin on 192.168.1.88/24 connect to any lan ethernet port power on the device while holding the reset button wait at least 8 seconds before releasing reset button for image to download Signed-off-by: Alessio Prescenzo <alessioprescenzo@gmail.com> [ensure unique wireless MAC, fix GPIO pingroup] Signed-off-by: David Bauer <mail@david-bauer.net>
* realtek: Trap all frames with switch as destination to CPU-portBirger Koblitz2022-05-081-0/+9
| | | | | | | | | | | | This fixes a bug where frames sent to the switch itself were flooded to all ports unless the MAC address of the CPU-port was learned otherwise. Tested-by: Wenli Looi <wlooi@ucalgary.ca> Tested-by: Bjørn Mork <bjorn@mork.no> Signed-off-by: Birger Koblitz <git@birger-koblitz.de> [fix code formatting] Signed-off-by: Sander Vanheule <sander@svanheule.net>
* realtek: add support for ZyXEL GS1900-16Raylynn Knight2022-05-073-0/+45
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The ZyXEL GS1900-16 is a 16 port gigabit switch similar to other GS1900 switches. Specifications -------------- * Device: ZyXEL GS1900-16 * SoC: Realtek RTL8382M 500 MHz MIPS 4KEc * Flash: 16 MiB Macronix MX25L12835F * RAM: 128 MiB DDR2 SDRAM Nanya NT5TU128M8HE * Ethernet: 16x 10/100/1000 Mbps * LEDs: 1 PWR LED (green, not configurable) 1 SYS LED (green, configurable) 16 ethernet port link/activity LEDs (green, SoC controlled) * Buttons: 1 "RESET" button on front panel * Power 120-240V AC C13 * UART: 1 serial header (J12) with populated standard pin connector on the right back of the PCB. Pinout (front to back): + Pin 1 - VCC marked with white dot + Pin 2 - RX + Pin 3 - TX + PIn 4 - GND Serial connection parameters: 115200 8N1. Installation ------------ OEM upgrade method: * Log in to OEM management web interface * Navigate to Maintenance > Firmware * Select the HTTP radio button * Select the Active radio button * Use the browse button to locate the realtek-generic-zyxel_gs1900-16-initramfs-kernel.bin file amd select open so File Path is update with filename. * Select the Apply button. Screen will display "Prepare for firmware upgrade ...". *Wait until screen shows "Do you really want to reboot?" then select the OK button * Once OpenWrt has booted, scp the sysupgrade image to /tmp and flash it: > sysupgrade -n /tmp/realtek-generic-zyxel_gs1900-16-squashfs-sysupgrade.bin it may be necessary to restart the network (/etc/init.d/network restart) on the running initramfs image. U-Boot TFTP method: * Configure your client with a static 192.168.1.x IP (e.g. 192.168.1.10). * Set up a TFTP server on your client and make it serve the initramfs image. * Connect serial, power up the switch, interrupt U-boot by hitting the space bar, and enable the network: > rtk network on * Since the GS1900-16 is a dual-partition device, you want to keep the OEM firmware on the backup partition for the time being. OpenWrt can only boot from the first partition anyway (hardcoded in the DTS). To make sure we are manipulating the first partition, issue the following commands: > setsys bootpartition 0 > savesys * Download the image onto the device and boot from it: > tftpboot 0x84f00000 192.168.1.10:openwrt-realtek-generic-zyxel_gs1900-16-initramfs-kernel.bin > bootm * Once OpenWrt has booted, scp the sysupgrade image to /tmp and flash it: > sysupgrade -n /tmp/openwrt-realtek-generic-zyxel_gs1900-16-squashfs-sysupgrade.bin it may be necessary to restart the network (/etc/init.d/network restart) on the running initramfs image. Signed-off-by: Raylynn Knight <rayknight@me.com> [removed duplicate patch title, align RAM specification] Signed-off-by: Sander Vanheule <sander@svanheule.net>
* kernel: backports: add Huawei MA5671A tx-fault workaroundMatthew Hagan2022-05-072-0/+114
| | | | | | | | | This workaround will allow the MA5671A to function, ignoring the persistently asserted tx-fault. Signed-off-by: Matthew Hagan <mnhagan88@gmail.com> (added 5.15 backport) Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: add support for kernel 5.15 for testingChristian Lamparter2022-05-077-0/+536
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch copies over refreshed config and patches from 5.10 with the following changes: - dropped superfluous tc654/tc655 variant detection patch (tc654 support will become available upstream starting with 5.17-rc7+). - dropped xhci msi(x) workaround... as the broken MSI(X) is now gone. - dropped dwc2 workaround since the driver was fixed and it works without it. Please note: Netgear WNDAP660 & WNDAP620 users: Due to the kernel's size increase, uboot will likely break because it is overwrite the kernel during decompression. To fix this (and debrick affected devices, no reflash necessary), attach the RJ45-Serial-Console cable and enter the following in the uboot prompt during bootup: setenv kernel_addr_r 1100000 saveenv run bootcmd to restore the old/previous behavior: setenv kernel_addr_r 600000 saveenv run bootcmd Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* kernel: usb-xhci-pci-renesas: remove LINUX_5_10 dependency symbolChristian Lamparter2022-05-071-1/+0
| | | | | | | | With 5.4 out of the picture, remove LINUX_5_10 here. This is needed for the WNDR4700 as otherwise kmod-usb3 isn't available for 5.15. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* generic: 5.15: add missing symbolChristian Lamparter2022-05-071-0/+1
| | | | | | Found during apm821xx refresh. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* kernel/x86: move x86' specific watchdogs to the x86 targetChristian Lamparter2022-05-072-65/+67
| | | | | | | | | | | | | | | | | | | | | | | | | | | upstream linux have these watchdogs locked behind X86. These will not build on other architectures. So move them to target/linux/x86/modules.mk drivers/watchdog/Kconfig: |config F71808E_WDT | tristate "Fintek F718xx, F818xx Super I/O Watchdog" | depends on X86 |[...] |config IT87_WDT | tristate "IT87 Watchdog Timer" | depends on X86 |[...] |config ITCO_WDT | tristate "Intel TCO Timer/Watchdog" | depends on (X86 || IA64) && PCI |[...] |config W83627HF_WDT | tristate "Watchdog timer for W83627HF/W83627DHG and compatibles" | depends on X86 |[...] Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* x86: detangle meraki-mx100 / nu801 build confusionChristian Lamparter2022-05-071-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Grommish reported the dreaded build error that happend with 5.4 since the kernel didn't have the cgpio v2 interface. His reason for the removed 5.4 was that the octeon target had a memory leak issue, so he had to backport the removed 5.4 kernel for his tests. Chen Minqiang chimed in and noted that no matter what (i.e. @TARGET_x86 in depends) didn't prevent the package from being build on other targets. From what I can tell, the reason for this was that +nu801 meant that kmod-meraki-mx100 pulled in an unconditional dependency as part of to the kernel build. |scripts/package-metadata.pl mk tmp/.packageinfo | |$(curdir)/kernel/linux/compile += $(curdir)/firmware/linux-firmware/compile \ | $(curdir)/firmware/prism54-firmware/compile \ | $(curdir)/kernel/gpio-button-hotplug/compile \ | >>> $(curdir)/system/gpio-cdev/nu801/compile <<< change this by making the dependency conditional on the meraki-mx100 module itself. Note that the nu801 enables/sets the KCONFIG for the cgpio v2 interface itself, since the userspace program and not the kernel meraki-mx100 relies on it. Reference: <https://github.com/openwrt/openwrt/commit/eeb8fd4ce7e9> Reported-by: Grommish <grommish@gmail.com> Reported-by: Chen Minqiang <ptpt52@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* x86: add ib700wdt module for x86 qemu watchdogsChristian Lamparter2022-05-071-0/+18
| | | | | | | | QEMU+Libvirt can emulate the ib700wdt watchdogs which due to its I/O-Port mapping makes it x86 specific. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* armvirt: 64: enable driver for QEMU' supported watchdogChristian Lamparter2022-05-072-0/+4
| | | | | | | | | | | | QEMU can emulate several watchdogs: aspeed SoC, i6300esb, ib700wdt, imx2, cmsdk-apb and sbsa_gwdt. Out of these, the ARM SBSA Generic Watchdog (sbsa_gwdt) makes the most sense for the armvirt' 64 target. Both imx2 and aspeed are guarded by special vendor specific CONFIG_ in the upstream kernel. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* kernel: provide i6300esb for qemu/libvirtChristian Lamparter2022-05-071-0/+18
| | | | | | | | | | the Intel i6300esb is QEMU's default watchdog. And unlike the real "Intel i6300ESB I/O Controller hub" hardware, the i6300esb watchdog driver works on non-x86 targets like for ARM (armvirt 32bit) and potentially virtual PowerPC and MIPS targets (if there was any). Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* kernel: fix corrupted padding on small packets with mt753x dsaFelix Fietkau2022-05-062-0/+58
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: backport flow offload fixes to 5.10Felix Fietkau2022-05-066-150/+413
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: fix flow offload issues with pppoeFelix Fietkau2022-05-065-150/+368
| | | | | | sync xt_FLOWOFFLOAD code with latest version of nft_flow_offload Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ipq40xx: consolidate ar40xx driver filesSungbo Eo2022-05-054-2235/+0
| | | | | | | | | | Commit f4fb63d2ab4f ("ipq40xx: 5.10: move AR40xx to MDIO drivers") moved the ar40xx driver files to kernel version specific directories to place them in different subdirectory in kernel tree. But now kernel 5.4 is gone and there is no reason to keep them separate. Move them back to common files/ directory. Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* ipq40xx: 5.15: fix ar40xx driverNick Hainke2022-05-051-0/+3
| | | | | | | | | | | | | | | | Also apply commit ab7e53e5cce7 ("ipq40xx: 5.10: fix ar40xx driver") to 5.15 driver. The commit fixes the data corruption on TX packets. Packets are transmitted, but their contents are replaced with zeros. This error is caused by the lack of guard (50 ms) intervals between calibration phases. This error is treated by adding mdelay(50) to the calibration function code. In the original qca-ssda code, these mdelays were existing, but in the ar41xx.c they are gone. Fixes: 87318eb17936 ("ipq40xx: 5:15: copy config and patch from 5.10") Signed-off-by: Nick Hainke <vincent@systemli.org>
* ramips: add i2c in dts for GL-MT300N-V2Ptilopsis Leucotis2022-05-051-0/+4
| | | | | | | | According wiki https://docs.gl-inet.com/en/2/hardware/mt300n-v2/ GL-MT300N-V2 have I2C interface on GPIO4, GPIO5. Adding I2C in device tree make possible using I2C on this device. Signed-off-by: Ptilopsis Leucotis <PtilopsisLeucotis@yandex.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-14 16:21:17 +0000