1. 27 Feb, 2020 1 commit
  2. 26 Feb, 2020 5 commits
  3. 24 Feb, 2020 1 commit
  4. 23 Feb, 2020 4 commits
  5. 22 Feb, 2020 2 commits
    • Adrian Schmutzler's avatar
      Revert "ath79: add support for Ubiquiti NanoStation Loco M (XW)" · b2660e67
      Adrian Schmutzler authored
      This reverts commit 21bf718b
      
      .
      
      Until the mdio-reset is solved, this is not ready for stable release.
      Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      b2660e67
    • Roger Pueyo Centelles's avatar
      ath79: add support for Ubiquiti NanoStation Loco M (XW) · 21bf718b
      Roger Pueyo Centelles authored
      
      
      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: default avatarRoger Pueyo Centelles <roger.pueyo@guifi.net>
      (backported from commit 633c4304
      
      )
      Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      21bf718b
  6. 21 Feb, 2020 5 commits
    • Sungbo Eo's avatar
      ramips: append tail to WF2881 initramfs image · 2d3a9333
      Sungbo Eo authored
      
      
      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: default avatarSungbo Eo <mans0n@gorani.run>
      (cherry picked from commit be3e98ce)
      2d3a9333
    • Adrian Schmutzler's avatar
      ath79: add support for Ubiquiti Picostation M (XM) · 8fa6107a
      Adrian Schmutzler authored
      
      
      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: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      (cherry picked from commit 6fdaf16d)
      8fa6107a
    • Sven Roederer's avatar
      ath79: add support for Ubiquiti Nanostation Loco M (XM) · 6a950afd
      Sven Roederer authored
      
      
      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: default avatarSven Roederer <freifunk@it-solutions.geroedel.de>
      Co-developed-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      (cherry picked from commit b56bcfe3)
      6a950afd
    • Adrian Schmutzler's avatar
      ath79: add gpio4 pinmux on TL-WR841N/ND v8, WR842N v2, MR3420 v2 · 7cbd3942
      Adrian Schmutzler authored
      
      
      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: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      Tested-by: default avatarArmin Fuerst <armin@fuerst.priv.at>
      [backport: change individual DTS files, no mr3420-v2 present]
      (backported from commit 18c95c9d)
      7cbd3942
    • Adrian Schmutzler's avatar
      ath79: enable forceless sysupgrade from ar71xx on fritz300e · 085f3835
      Adrian Schmutzler authored
      
      
      This adds the ar71xx board name to the SUPPORTED_DEVICES on ath79,
      so forceless sysupgrade on this device becomes possible.
      Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      (cherry picked from commit 49ff00db)
      085f3835
  7. 20 Feb, 2020 1 commit
  8. 11 Feb, 2020 2 commits
  9. 08 Feb, 2020 1 commit
  10. 07 Feb, 2020 6 commits
  11. 05 Feb, 2020 1 commit
  12. 04 Feb, 2020 2 commits
    • Koen Vandeputte's avatar
      kernel: add support for GD25D05 SPI NOR · 2a844349
      Koen Vandeputte authored
      
      
      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: default avatarKoen Vandeputte <koen.vandeputte@ncentric.com>
      2a844349
    • Koen Vandeputte's avatar
      kernel: bump 4.14 to 4.14.169 · eca8a2ee
      Koen Vandeputte authored
      
      
      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: default avatarKoen Vandeputte <koen.vandeputte@ncentric.com>
      eca8a2ee
  13. 01 Feb, 2020 1 commit
    • Mason Clarke's avatar
      ramips: reenable image creation for the D-Link DIR-645 · 3d1c84d4
      Mason Clarke authored
      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 62d5ece7) with
      the default 19.07 release config, and I cannot confirm the report that
      commit 2607c02e
      ("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 2607c02e
      
      .
      Signed-off-by: default avatarMason Clarke <mclarke2355@gmail.com>
      3d1c84d4
  14. 30 Jan, 2020 1 commit
  15. 29 Jan, 2020 4 commits
  16. 28 Jan, 2020 3 commits
    • Felix Fietkau's avatar
      kernel: fix dst reference leak in flow offload · 8ab2b42f
      Felix Fietkau authored
      
      
      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: default avatarFelix Fietkau <nbd@nbd.name>
      [removed 4.19 patch during cherry-pick]
      Signed-off-by: default avatarPetr Štetiar <ynezz@true.cz>
      (cherry picked from commit c6c4701d)
      8ab2b42f
    • Adrian Schmutzler's avatar
      ath79: fix SUPPORTED_DEVICES not matching ar71xx board names · 47935940
      Adrian Schmutzler authored
      
      
      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: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      (cherry picked from commit 07ce940b)
      47935940
    • Adrian Schmutzler's avatar
      ath79: remove SUPPORTED_DEVICES for TP-Link Archer D50 v1 · da5b5ae9
      Adrian Schmutzler authored
      
      
      This device has not been supported in ar71xx, so there is no need
      for an explicit SUPPORTED_DEVICES entry.
      Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      (cherry picked from commit 894bdee7)
      da5b5ae9