aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* brcm2708: fix build failureDavid Bauer2020-03-261-2/+2
| | | | | | | | | | | | | | | | | Build of the brcm2708 subtarget currently fails with the following error message: arch/arm/lib/memset_rpi.S: Assembler messages: arch/arm/lib/memset_rpi.S:65: Error: garbage following instruction -- `orr DAT0,DAT0,lsl#8' arch/arm/lib/memset_rpi.S:67: Error: garbage following instruction -- `orr DAT0,DAT0,lsl#16' scripts/Makefile.build:427: recipe for target 'arch/arm/lib/memset_rpi.o' failed Using the assembly notation from master fixes this error. Signed-off-by: David Bauer <mail@david-bauer.net>
* oxnas: yet another irqchip related patchDaniel Golle2020-03-221-0/+55
| | | | | | | | | This time DTS fix, again from Sungbo Eo <mans0n@gorani.run> ARM: dts: oxnas: Fix clear-mask property Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit 9e5a25846f501acfd4aedccae8cef31ad8f2c456) Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* oxnas: backport another fix for irqchipDaniel Golle2020-03-211-0/+58
| | | | | | | | | Sungbo Eo <mans0n@gorani.run> submitted another patch fixing an error on reboot: irqchip/versatile-fpga: Apply clear-mask earlier Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit 19af00850f63e0b53c081f6a57b134275fb6cafb)
* ath79: add support for TP-Link WDR3500 v1Adrian Schmutzler2020-03-206-132/+238
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware: SoC: AR9344 CPU: 560 MHz Flash: 8 MiB RAM: 128 MiB WiFi: Atheros AR9340 2.4GHz 802.11bgn Atheros AR9300 5GHz 802.11an Ethernet: AR934X built-in switch, WAN on separate physical interface USB: 1x 2.0 Flash instruction (WebUI): Download *-factory.bin image and upload it via the firmwary upgrade function of the stock firmware WebUI. Flash instruction (TFTP): 1. Set PC to fixed ip address 192.168.0.66 2. Download *-factory.bin image and rename it to wdr3500v1_tp_recovery.bin 3. Start a tftp server with the image file in its root directory 4. Turn off the router 5. Press and hold Reset button 6. Turn on router with the reset button pressed and wait ~15 seconds 7. Release the reset button and after a short time the firmware should be transferred from the tftp server 8. Wait ~30 second to complete recovery. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> [removed stray newline] Signed-off-by: David Bauer <mail@david-bauer.net> (backported from commit fbbb4eb8b41d59b38f41fe382c6e4108a36aa909) Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for TP-Link Archer C60 v3Adrian Schmutzler2020-03-208-12/+108
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link Archer C60 v3 is a dual-band AC1350 router, based on Qualcomm/Atheros QCA9561 + QCA9886. It seems to be identical to the v2 revision, except that it lacks a WPS LED and has different GPIO for amber WAN LED. Specification: - 775/650/258 MHz (CPU/DDR/AHB) - 64 MB of RAM (DDR2) - 8 MB of FLASH (SPI NOR) - 3T3R 2.4 GHz - 2T2R 5 GHz - 5x 10/100 Mbps Ethernet - 6x LED, 2x button - UART header on PCB Flash instruction (WebUI): Download *-factory.bin image and upload it via the firmwary upgrade function of the stock firmware WebUI. Flash instruction (TFTP): 1. Set PC to fixed IP address 192.168.0.66 2. Download *-factory.bin image and rename it to tp_recovery.bin 3. Start a tftp server with the file tp_recovery.bin in its root directory 4. Turn off the router 5. Press and hold reset button 6. Turn on router with the reset button pressed and wait ~15 seconds 7. Release the reset button and after a short time the firmware should be transferred from the tftp server 8. Wait ~30 second to complete recovery While TFTP works for OpenWrt images, my device didn't accept the only available official firmware "Archer C60(EU)_V3.0_190115.bin". In contrast to earlier revisions (v2), the v3 contains the (same) MAC address twice, once in 0x1fa08 and again in 0x1fb08. While the partition-table on the device refers to the latter, the firmware image contains a different partition-table for that region: name device firmware factory-boot 0x00000-0x1fb00 0x00000-0x1fa00 default-mac 0x1fb00-0x1fd00 0x1fa00-0x1fc00 pin 0x1fd00-0x1fe00 0x1fc00-0x1fd00 product-info 0x1fe00-0x1ff00 0x1fd00-0x1ff00 device-id 0x1ff00-0x20000 0x1ff00-0x20000 While the MAC address is present twice, other data like the PIN isn't, so with the partitioning from the firmware image the PIN on the device would actually be outside of its partition. Consequently, the patch uses the MAC location from the device (which is the same as for the v2). Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 646d95c374072598fab9e949ef4425177c5c7960)
* oxnas: backport patch fixing hang after rebootDaniel Golle2020-03-191-0/+77
| | | | | | | | | | | | Sungbo Eo <mans0n@gorani.run> posted a patch fixing the long-standing reboot problem on the OXNAS OX820 platform: irqchip/versatile-fpga: Handle chained IRQs properly It got queued for 5.7. Import it to oxnas target patches for now. Fixes: b4917fa907 ("oxnas: fix oxnas-rps-timer dt-match") Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit 67b04e767a0dcd01d39fe71eed9bdff7d5be72f0)
* layerscape: add kmod-i2c-mux to DEVICE_PACKAGES for traverse-ls1043Sungbo Eo2020-03-141-1/+1
| | | | | | | | kmod-i2c-mux-pca954x will not get into images unless kmod-i2c-mux is added to DEVICE_PACKAGES as well. Signed-off-by: Sungbo Eo <mans0n@gorani.run> (cherry picked from commit dffbe668ab321c76c041aa15ca8b753deab2c4c5)
* ath79: add support for TP-Link TL-WR740N v5Jun Su2020-03-144-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | This adds support for the TP-Link TL-WR740N v5, a clone of the v4 only with a different TPLINK_HWID. It was already supported in ar71xx as well. Specifications: SOC: Atheros AR9331 CPU: 400MHz Flash: 4 MiB RAM: 32 MiB WLAN: Atheros AR9330 bgn Ethernet: 5 ports (100M) Flashing instructions: - Flash factory image from OEM WebUI: openwrt-ath79-tiny-tplink_tl-wr740n-v5-squashfs-factory.bin - Sysupgrade from ar71xx image: openwrt-ath79-tiny-tplink_tl-wr740n-v5-squashfs-sysupgrade.bin Signed-off-by: Jun Su <howard0su@gmail.com> [commit title/message facelift, backport for 19.07] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit b9f4f1f97aeeec65a872c4c5b1a0528a69d16d7b)
* ar71xx: fix port order on TP-Link Archer C60 v1/v2Adrian Schmutzler2020-03-141-6/+2
| | | | | | | | | | The labels on the LAN ports of the TP-Link Archer C60 v1/v2 are actually inverted compared to the ports of the internal switch. Add this information to 02_network. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 14a07fa1f000f962d55bf53cfe9b128448b1f11f)
* ath79: fix port order on TP-Link Archer C60 v1/v2Adrian Schmutzler2020-03-141-6/+2
| | | | | | | | | | | | The labels on the LAN ports of the TP-Link Archer C60 v1/v2 are actually inverted compared to the ports of the internal switch. Add this information to 02_network. This is the same for to-be-supported v3 of this device. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit b054729899560aa9faea594dd7df573883f0cf3f)
* ar71xx: remove wrong MAC address adjustment for Archer C60 v2Adrian Schmutzler2020-03-141-2/+1
| | | | | | | | | | | | The adjustment of the MAC address for Archer C60 v2 in 10_fix_wifi_mac is broken since a "mac" partition is not set up for this device on ar71xx. Instead, the MAC address is already patched correctly in 11-ath10k-caldata. Remove the useless adjustment. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit cbdc91902466dd113b9680566abb2eb2f8022dd4)
* ar71xx: fix swapped LAN/WAN MAC address for Archer C60 v1/v2Adrian Schmutzler2020-03-142-5/+5
| | | | | | | | | | | | | | | | | | | | The MAC addresses for lan/wan are swapped compared to the vendor firmware. This adjusts to vendor configuration, which is: lan *:7b label wan *:7c label+1 2.4g *:7b label 5g *:7a label-1 Only one address is stored in <&mac 0x8>, corresponding to the label. This has been checked on revisions v1, v2 and v3. Since ar71xx calculates the ath10k MAC address based on the ethernet addresses, the number there is adjusted, too. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 14eb54938b525d4c2d2847a6fad7670ed944650c)
* ath79: fix swapped LAN/WAN MAC address for Archer C60 v1/v2Adrian Schmutzler2020-03-141-1/+1
| | | | | | | | | | | | | | | | | The MAC addresses for lan/wan are swapped compared to the vendor firmware. This adjusts to vendor configuration, which is: lan *:7b label wan *:7c label+1 2.4g *:7b label 5g *:7a label-1 Only one address is stored in <&mac 0x8>, corresponding to the label. This has been checked on revisions v1, v2 and v3. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 88aead0a665dd349af4fb8afcfe1a16cf90515ae)
* ar71xx/ath79: ew-dorin, fix the trigger level for WPS buttonCatrinel Catrinescu2020-03-112-2/+2
| | | | | | | | | | Because the WPS button had the wrong trigger level, the failsafe mode was triggered quite often, after this commit: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=27f3f493de Signed-off-by: Catrinel Catrinescu <cc@80211.de> (cherry picked from commit 3e03b7ac4ada4966d058871d0a1f67f1f0f408d4)
* kernel: backport out-of-memory fix for non-Ethernet devicesRafał Miłecki2020-03-111-0/+71
| | | | | | | | Doing up & down on non-Ethernet devices (e.g. monitor mode interface) was consuming memory. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit ec8e8e2ef0826d82b4dfbd567a073b31dc27b764)
* kernel: bump 4.14 to 4.14.172Koen Vandeputte2020-03-0913-18/+18
| | | | | | | | | Refreshed all patches. Compile-tested on: ar71xx, cns3xxx, imx6, x86_64 Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: add missing LED migration for Archer C7David Bauer2020-03-011-0/+3
| | | | | | | | | | | | | When changing the LED names for the Archer C7 to represent the correct color, a migration for existing UCI entries was not created. Add a migration to keep existing LED configurations working. Fixes commit c79c001b593b ("ar71xx: Archer C7 v1 LED names and RFKILL fixes") Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 4349d4c6823bfe09caabbdd3c9a65198addc76d6)
* ar71xx: correct AVM FRITZ Repeater 450E WPS button flagDavid Bauer2020-03-011-1/+1
| | | | | | | | | | The AVM FRITZ!WLAN Repeater 450E's WPS button is not active low. Correct the active low flag to avoid unintenional activation of failsafe mode on boot. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 1d4f2ca6105698fde3b997c32e7e41f080c79a15)
* ath79: add missing reset-gpios for NanoStation Loco M (XW)Roger Pueyo Centelles2020-02-261-0/+1
| | | | | | | | | When porting support from ar71xx to ath79, the reset-gpios option was missed. Due to a hardware bug, this would eventually leave the devices with RX-deaf Ethernet PHY. Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> (cherry picked from commit 6613a7f5cc8e1527671128d9479b3de78f7b4cdd)
* ath79: add support for Ubiquiti NanoStation Loco M (XW)Roger Pueyo Centelles2020-02-264-0/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit adds support for the NanoStation Loco M2/M5 XW devices on the ath79 target (support was long ago available on ar71xx). Specifications: - AR9342 SoC @ 535 MHz - 64 MB RAM - 8 MB SPI flash - 1x 10/100 Mbps Ethernet, 24 Vdc PoE-in - AR8032 switch - 2T2R 5 GHz radio, 22 dBm - 13 dBi built-in antenna - POWER/LAN green LEDs - 4x RSSI LEDs (red, orange, green, green) - UART (115200 8N1) on PCB Flashing via TFTP: - Use a pointy tool (e.g., pen cap, paper clip) and keep the reset button on the device or on the PoE supply pressed - Power on the device via PoE (keep reset button pressed) - Keep pressing until LEDs flash alternatively LED1+LED3 => LED2+LED4 => LED1+LED3, etc. - Release reset button - The device starts a TFTP server at 192.168.1.20 - Set a static IP on the computer (e.g., 192.168.1.21/24) - Upload via tftp the factory image: $ tftp 192.168.1.20 tftp> bin tftp> trace tftp> put openwrt-ath79-generic-xxxxx-ubnt_nanostation-loco-m-xw-squashfs-factory.bin Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> (backported from commit 633c4304ad42d18d180ba65a264ba668de445d91) Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: bump 4.14 to 4.14.171Koen Vandeputte2020-02-2429-64/+59
| | | | | | | | | | | | Refreshed all patches. Fixes: - CVE-2013-1798 Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ipq806x: fix bug in L2 cache scalingAnsuel Smith2020-02-231-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It has been notice a buf in L2 cache scaling where the scaling is not done proprely if the frequency is set to the initial state before the new frequency. From: https://patchwork.kernel.org/patch/10565443/ * The clocks are set to aux clock rate first to make sure the * secondary mux is not sourcing off of QSB. The rate is then set to * two different rates to force a HFPLL reinit under all * circumstances. In the initial stage of boot to force a new frequency to apply, is needed to first set the frequency back to the lowest one (aux_rate) and then to the target one. This force and make sure the controller actually switch the frequency to the right one. Apply the same mechanism to L2 frequency scaling. Before scaling to the target frequency, first set the frequency to the aux_rate to force the transition, then scale it to the target frequency. Doing the wrong way can produce unexpected results and could lock the scaling mechanism until a full reboot is done (Causing a full reset by the krait-cc driver) From: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=77612720a2362230af726baa4149c40ec7a7fb05 When the Hfplls are reprogrammed during the rate change, the primary muxes which are sourced from the same hfpll for higher frequencies, needs to be switched to the 'safe secondary mux' as the parent for that small window. This is done by registering a clk notifier for the muxes and switching to the safe parent in the PRE_RATE_CHANGE notifier and back to the original parent in the POST_RATE_CHANGE notifier. This should apply also to L2 scaling... as we can't relly use the notifier, we manually do this on L2 scaling. Tested-By: Marc Benoit <marcb62185@gmail.com> [19.07: R7800] Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com> (cherry picked from commit 5ab9c0b388e9cf2537ef23d6e9baaf5730a14a1c)
* ipq806x: add missing core1 voltage tolerancePavel Kubelun2020-02-231-0/+1
| | | | | | | | | | Voltage tolerance is accounted per core, not per cpu, so add missing DT entry. Tested-By: Marc Benoit <marcb62185@gmail.com> [19.07: R7800] Signed-off-by: Pavel Kubelun <be.dissent@gmail.com> Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com> (cherry picked from commit 77e7d6c20dc6d5e50600fb4d013f4b71341e4168)
* ath79: ar934x: use reset for usb-phy-analogJohann Neuhauser2020-02-231-2/+2
| | | | | | | | | | | | | | This was already available on ar71xx, but is missing on ath79. This solves the slow usb speed on TP-Link WDR3600/WDR4300 and similar, as reported in Flyspray [0], OpenWRT Forum [1] and GitHub PR [2]. [0] https://bugs.openwrt.org/index.php?do=details&task_id=2567 [1] https://forum.openwrt.org/t/usb-wdr4300-low-speed-on-external-storage/46794 [2] https://github.com/openwrt/openwrt/pull/964 Tested-By: Lech Perczak <lech.perczak@gmail.com> [TL-WDR4300] Signed-off-by: Johann Neuhauser <johann@it-neuhauser.de> (cherry picked from commit bda6b6144dbe3e12d128b500821799ef472de4cb)
* ath79: phy-ar7200-usb: adapt old behavior of arch/mips/ath79/dev-usb.cJohann Neuhauser2020-02-231-6/+18
| | | | | | | | | | | | | | | | | [ Upstream commit 6cca6fffa06b1996f9bcc280f766e8ba4fa97d45 ] Do not put usb-phy into reset if clearing the usb-phy reset or setting the suspend_override has failed. Reorder (de)asserts like in arch/mips/ath79/dev-usb.c. Add an optional reset_control "usb-phy-analog", which is needed for ar934x SoCs like in the old mach-driver arch/mips/ath79/dev-usb.c. Tested-By: Lech Perczak <lech.perczak@gmail.com> [TL-WDR4300] Signed-off-by: Johann Neuhauser <johann@it-neuhauser.de> [added reference to upstream commit, Tested-by] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* Revert "ath79: add support for Ubiquiti NanoStation Loco M (XW)"Adrian Schmutzler2020-02-224-39/+0
| | | | | | | | This reverts commit 21bf718b8c3b0fe1f13807aa5db16a2fb4f48120. Until the mdio-reset is solved, this is not ready for stable release. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for Ubiquiti NanoStation Loco M (XW)Roger Pueyo Centelles2020-02-224-0/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit adds support for the NanoStation Loco M2/M5 XW devices on the ath79 target (support was long ago available on ar71xx). Specifications: - AR9342 SoC @ 535 MHz - 64 MB RAM - 8 MB SPI flash - 1x 10/100 Mbps Ethernet, 24 Vdc PoE-in - AR8032 switch - 2T2R 5 GHz radio, 22 dBm - 13 dBi built-in antenna - POWER/LAN green LEDs - 4x RSSI LEDs (red, orange, green, green) - UART (115200 8N1) on PCB Flashing via TFTP: - Use a pointy tool (e.g., pen cap, paper clip) and keep the reset button on the device or on the PoE supply pressed - Power on the device via PoE (keep reset button pressed) - Keep pressing until LEDs flash alternatively LED1+LED3 => LED2+LED4 => LED1+LED3, etc. - Release reset button - The device starts a TFTP server at 192.168.1.20 - Set a static IP on the computer (e.g., 192.168.1.21/24) - Upload via tftp the factory image: $ tftp 192.168.1.20 tftp> bin tftp> trace tftp> put openwrt-ath79-generic-xxxxx-ubnt_nanostation-loco-m-xw-squashfs-factory.bin Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> (backported from commit 633c4304ad42d18d180ba65a264ba668de445d91) Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: append tail to WF2881 initramfs imageSungbo Eo2020-02-211-0/+8
| | | | | | | | | | | | | Stock firmware has a vendor-defined tail at the end of uImage for image validation. This patch enables OpenWrt installation from stock firmware without having to access the UART console. Installation via web interface: 1. Flash **initramfs** image through the stock web interface. 2. Boot into OpenWrt and perform sysupgrade with sysupgrade image. Signed-off-by: Sungbo Eo <mans0n@gorani.run> (cherry picked from commit be3e98ce26da5e737744427e1d59dd1c0508edef)
* ath79: add support for Ubiquiti Picostation M (XM)Adrian Schmutzler2020-02-215-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds support for the Ubiquiti Picostation M (XM), which has the same board/LEDs as the Bullet M XM, but different case and antennas. Specifications: - AR7241 SoC @ 400 MHz - 32 MB RAM - 8 MB SPI flash - 1x 10/100 Mbps Ethernet, 24 Vdc PoE-in - External antenna: 5 dBi (USA), 2 dBi (EU) - POWER/LAN green LEDs - 4x RSSI LEDs (red, orange, green, green) - UART (115200 8N1) on PCB Flashing via WebUI: Upload the factory image via the stock firmware web UI. Attention: airOS firmware versions >= 5.6 have a new bootloader with an incompatible partition table! Please downgrade to <= 5.5 _before_ flashing OpenWrt! Refer to the device's Wiki page for further information. Flashing via TFTP: Same procedure as other NanoStation M boards. - Use a pointy tool (e.g., pen cap, paper clip) and keep the reset button on the device or on the PoE supply pressed - Power on the device via PoE (keep reset button pressed) - Keep pressing until LEDs flash alternatively LED1+LED3 => LED2+LED4 => LED1+LED3, etc. - Release reset button - The device starts a TFTP server at 192.168.1.20 - Set a static IP on the computer (e.g., 192.168.1.21/24) - Upload via tftp the factory image: $ tftp 192.168.1.20 tftp> bin tftp> trace tftp> put openwrt-ath79-generic-xxxxx-ubnt_picostation-m-squashfs-factory.bin Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 6fdaf16dd0623db1a324d33fdf0bc1654365ee62)
* ath79: add support for Ubiquiti Nanostation Loco M (XM)Sven Roederer2020-02-215-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds support for the Ubiquiti Nanostation Loco M (XM), which has the same board/LEDs as the Bullet M XM, but different case and antennas. Specifications: - AR7241 SoC @ 400 MHz - 32 MB RAM - 8 MB SPI flash - 1x 10/100 Mbps Ethernet, 24 Vdc PoE-in - NS Loco M2: built-in antenna: 8 dBi; AR9287 - NS Loco M5: built-in antenna: 13 dBi; 2T2R 5 GHz radio - POWER/LAN green LEDs - 4x RSSI LEDs (red, orange, green, green) - UART (115200 8N1) on PCB Flashing via WebUI: Upload the factory image via the stock firmware web UI. Note that only certain firmware versions accept unsigned images. Refer to the device's Wiki page for further information. Flashing via TFTP: Same procedure as other NanoStation M boards. - Use a pointy tool (e.g., pen cap, paper clip) and keep the reset button on the device or on the PoE supply pressed - Power on the device via PoE (keep reset button pressed) - Keep pressing until LEDs flash alternatively LED1+LED3 => LED2+LED4 => LED1+LED3, etc. - Release reset button - The device starts a TFTP server at 192.168.1.20 - Set a static IP on the computer (e.g., 192.168.1.21/24) - Upload via tftp the factory image: $ tftp 192.168.1.20 tftp> bin tftp> trace tftp> put openwrt-ath79-generic-xxxxx-ubnt_nanostation-loco-m-squashfs-factory.bin Tested on NanoStation Loco M2. Signed-off-by: Sven Roederer <freifunk@it-solutions.geroedel.de> Co-developed-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit b56bcfe3be40493daecf13a4080920de2994ff54)
* ath79: add gpio4 pinmux on TL-WR841N/ND v8, WR842N v2, MR3420 v2Adrian Schmutzler2020-02-212-8/+16
| | | | | | | | | | | | | | | | | | | | | | | This adds a pinmux to the shared DTSI for TP-Link TL-WR841N/ND v8, TL-WR842N v2 and TL-MR3420 v2. It is supposed to be the equivalent of: /* config gpio4 as normal gpio function */ ath79_gpio_output_select(TL_MR3420V2_GPIO_USB_POWER,AR934X_GPIO_OUT_GPIO); This allows to enable USB power on these devices. While at it, move the jtag_disable_pins to &gpio node and remove the redundant status=okay there. Tested on TP-Link TL-WR842N v2. Fixes: FS#2753 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Tested-by: Armin Fuerst <armin@fuerst.priv.at> [backport: change individual DTS files, no mr3420-v2 present] (backported from commit 18c95c9d6ebea5cef1254ee917bff8aba993666d)
* ath79: enable forceless sysupgrade from ar71xx on fritz300eAdrian Schmutzler2020-02-211-0/+1
| | | | | | | | This adds the ar71xx board name to the SUPPORTED_DEVICES on ath79, so forceless sysupgrade on this device becomes possible. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 49ff00db340ea017c266ba37546c71209cfe3e26)
* ath79: add wmac migration for all ar93xx/qca95xx SoCsChuanhong Guo2020-02-111-5/+6
| | | | | | | | | Add migration for all ar71xx device path as well as previously incorrect ath79 path. Signed-off-by: Chuanhong Guo <gch981213@gmail.com> (cherry picked from commit d08b5bb344792bb82ccbcf3a0a8d25c79e72f4fe) Tested-by: Lech Perczak <lech.perczak@gmail.com> [TP-Link TL-WDR4300 v1]
* ath79: ar93xx/qca95xx: move gmac/wmac/pcie node out of apb busChuanhong Guo2020-02-115-123/+123
| | | | | | | | | | according to functional block diagram in datasheet, these devices don't belong to apb bus. Move these nodes out to match datasheet description. Signed-off-by: Chuanhong Guo <gch981213@gmail.com> (cherry picked from commit f65501e1c2fee17d61f047cee404ddf5f0caf31a) Tested-by: Lech Perczak <lech.perczak@gmail.com> [TP-Link TL-WDR4300 v1]
* ath79: fix DTS node names for Ubiquiti XW partitionsAdrian Schmutzler2020-02-071-2/+2
| | | | | | | | Some node names were inconsistent with the reg property. Fix it. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 1a0d6e1eba57d38c5ab6b0e8468188f09e45079d) [fixed XM->XW in commit title for backport]
* ath79: WNDR3700 v1/v2: make u-boot env partition writableMichal Cieslakiewicz2020-02-072-2/+0
| | | | | | | | Remove read-only flag from U-boot environment partition for Netgear WNDR3700 v1 and v2 so u-boot-envtools can modify data there. Signed-off-by: Michal Cieslakiewicz <michal.cieslakiewicz@wp.pl> (cherry picked from commit 6227c8d1bf41739586969c3102897a7ba179114d)
* bcm53xx: build images for Luxul ABR-4500 and XBR-4500 routersDan Haab2020-02-072-0/+36
| | | | | | | | | | | Luxul ABR-4500 and XBR-4500 devices are wired routers with 5 Ethernet ports and 1 USB 3.0 port. Flashing requires using Luxul firmware 6.4.0 or newer and uploading firmware using "Firmware Update" web UI page. Signed-off-by: Dan Haab <dan.haab@legrand.com> (cherry picked from commit 1d47f81581bcd476487e5b29314602167a843b99) [rmilecki: use DEVICE_TITLE for 19.07] Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: add missing symbolKoen Vandeputte2020-02-051-0/+1
| | | | | | | | | Reported by Buildbot: x86 instruction decoder selftest (X86_DECODER_SELFTEST) [N/y/?] (NEW) aborted! Fixes: eca8a2ee0d44 ("kernel: bump 4.14 to 4.14.169") Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: add support for GD25D05 SPI NORKoen Vandeputte2020-02-041-0/+29
| | | | | | | | | | | | | | | | | | | | | | This chip is used on newer RB912UAG-5HPnD r2 boards: Before: [ 0.642553] m25p80 spi0.0: unrecognized JEDEC id bytes: c8, 40, 10 [ 0.649381] NAND flash driver for the RouterBOARD 91x series After: [ 0.641714] m25p80 spi0.0: found gd25d05, expected m25p80 [ 0.649916] m25p80 spi0.0: gd25d05 (64 Kbytes) [ 0.655122] Creating 4 MTD partitions on "spi0.0": [ 0.660164] 0x000000000000-0x00000000c000 : "routerboot" [ 0.667782] 0x00000000c000-0x00000000d000 : "hard_config" [ 0.675073] 0x00000000d000-0x00000000e000 : "bios" [ 0.682613] 0x00000000e000-0x00000000f000 : "soft_config" [ 0.690304] NAND flash driver for the RouterBOARD 91x series Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.169Koen Vandeputte2020-02-0434-328/+86
| | | | | | | | | | | | | | | | | Refreshed all patches. Fixes: - CVE-2019-14896 - CVE-2019-14897 Remove upstreamed: - 023-0007-crypto-crypto4xx-Fix-wrong-ppc4xx_trng_probe-ppc4xx_.patch - 001-4.22-01-MIPS-BCM63XX-drop-unused-and-broken-DSP-platform-dev.patch Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ramips: reenable image creation for the D-Link DIR-645Mason Clarke2020-02-011-1/+0
| | | | | | | | | | | | | | | | | | | This commit reenables the image creation for the D-Link DIR-645. Images built for the D-Link DIR-645 work just fine, there is no reason to disable the image creation for it. I tested the OpenWrt 18.06.5 and 19.07.0-rc1 images, as well as an image I built from the current 19.07 branch (git HEAD 62d5ece) with the default 19.07 release config, and I cannot confirm the report that commit 2607c02ed599b6118ba26e2f35e7c828c21d7275 ("ramips: disable D-Link DIR-645 by default") references. Configuration changes were applied successfully and remained set after a reboot as well. The log also showed no anomalies. This reverts commit 2607c02ed599b6118ba26e2f35e7c828c21d7275. Signed-off-by: Mason Clarke <mclarke2355@gmail.com>
* ramips: use tpt DTS trigger for TP-Link TL-MR3020 v3 and TL-WA801ND v5Jan Alexander2020-01-303-6/+4
| | | | | | | | | | | | | | | | | This converts the TP-Link TL-MR3020v3 board to use the WLAN throughput LED trigger in order to react to all VAPs. It also moves the WLAN trigger config of the TP-Link TL-WA801NDv5 to the DTS and merges the now identical LAN LED configs. Verified these changes on a TL-MR3020v3 and TL-WA801NDv5. Signed-off-by: Jan Alexander <jan@nalx.net> [changed commit title and extended commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> [added comment about test result on TL-WA801ND v5] Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 20eb45da4fc19c12ea2073471992eeaf9d602fa5)
* ramips: remove duplicate DEVICE_PACKAGES for TP-Link Archer C20iAdrian Schmutzler2020-01-291-1/+0
| | | | | | | | | | DEVICE_PACKAGES is specified twice for the same device. Remove the first (=older) assignment. Fixes: 40692f0fb55c ("ramips: mt7620: select only the matching mt76 driver") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 4ecd6510bf8877dcd07561045852726ffbab8814)
* kernel: fix dst reference leak in flow offloadFelix Fietkau2020-01-281-11/+12
| | | | | | | | | | | Fixes a significant amount of leaked memory with lots of connections Ref: PR#2721 Tested-by: Jerome Benoit <jerome.benoit@sap.com> [WRT1900AC v1] Signed-off-by: Felix Fietkau <nbd@nbd.name> [removed 4.19 patch during cherry-pick] Signed-off-by: Petr Štetiar <ynezz@true.cz> (cherry picked from commit c6c4701def07cd01a1b077cee93f64a9b2e3b5be)
* ath79: fix SUPPORTED_DEVICES not matching ar71xx board namesAdrian Schmutzler2020-01-284-11/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Based on a script for comparison, this fixes (hopefully) all errors in SUPPORTED_DEVICES for ar71xx->ath79 upgrade. Devices where old string is removed as the device does not exist in ar71xx: - dlink_dir-859-a1 - tplink_archer-a7-v5 - tplink_cpe510-v3 [only in master] Devices where string is changed because it did not match the board name in ar71xx: - tplink_tl-mr3220-v1 - tplink_tl-mr3420-v1 - tplink_tl-wr2543-v1 - tplink_tl-wr741nd-v4 - tplink_tl-wr841-v7 - ubnt_unifiac-mesh - ubnt_unifiac-mesh-pro - ubnt_unifiac-pro For this device, the correct string could not be found, but we could not determine the correct one. Thus, the string is removed for now: - tplink_tl-wr740n-v4 The script for checking this is quite simple (note that newer entries, i.e. ath79->ath79 upgrade, are displayed as missing): newpath=target/linux/ath79/image/ oldpath=target/linux/ar71xx/base-files/lib/ar71xx.sh for s in $(grep -roh "SUPPORTED_DEVICES.*" $newpath | sed 's/SUPPORTED_DEVICES *.= *//'); do found="Missing" grep -q -r "\"$s\"" $oldpath && found="Found" echo "$s: $found." done The errors might be filtered by appending 'grep "Missing"' to the script. Fixes: FS#2751 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 07ce940b77e6aceb095b0a16dda41e190dfc5b87)
* ath79: remove SUPPORTED_DEVICES for TP-Link Archer D50 v1Adrian Schmutzler2020-01-281-1/+0
| | | | | | | | This device has not been supported in ar71xx, so there is no need for an explicit SUPPORTED_DEVICES entry. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 894bdee7563036d6627022d7f292e83241a807a7)
* kernel: bump 4.14 to 4.14.167Koen Vandeputte2020-01-245-5/+5
| | | | | | | | | Refreshed all patches. Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ramips: mt7621: ubnt-erx: allow sysupgrade from masterPetr Štetiar2020-01-241-0/+2
| | | | | | | | | | | | Currently it's not possible to downgrade from master: Device ubiquiti,edgerouterx not supported by this image Supported devices: ubnt-erx So fix it by adding a DTS based device name from master into SUPPORTED_DEVICES list. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ar71xx: change u-boot-env to read-write for gl-ar150/-domino/mifiKimmo Vuorinen2020-01-231-3/+3
| | | | | | | | | | Change u-boot-env partitions to be mounted as read-write for gl-ar150, gl-domino and gl-mifi so uboot-envtools support is possible. Signed-off-by: Kimmo Vuorinen <kimmo.vuorinen@gmail.com> [commit title/message facelift] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 2c1cfacddedc82c7a34eeb2a26529a5f3ab423d8)
* ar71xx: ubnt-rocket-m-ti: fix RSSI LED definitionsLech Perczak2020-01-212-6/+8
| | | | | | | | | | | | | | | | | When mapping for RSSI LEDs was defined for interface wlan0 on Ubiquiti Rocket M Titanium, it missed connection to actual interface. Therefore create the mapping to interface, so RSSI LEDs work without additional configuration, after starting rssileds service. While at that, split RSSI into ~equal intervals for 6 LEDs, and remove coefficients needed for PWM LEDs, as this board does not support PWM LEDs. Finally, for complete support, enable 'rssileds' package in per-device rootfs, so the indicator works out of box. Signed-off-by: Lech Perczak <lech.perczak@gmail.com> (cherry picked from commit 83708f233daceacebd1c49da44711cc87b49162a)
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 04:08:27 +0000