This project is mirrored from https://github.com/luizluca/openwrt.git. Pull mirroring failed .
Last successful update .
  1. 23 Jan, 2021 15 commits
  2. 22 Jan, 2021 7 commits
  3. 21 Jan, 2021 7 commits
  4. 20 Jan, 2021 7 commits
    • Rafał Miłecki's avatar
      bcm4908: add pending mtd patches for BCM4908 partitioning · 20a0d435
      Rafał Miłecki authored
      
      
      BCM4908 can have multiple firmware partitions. MTD needs to detect which
      one is currently used.
      Signed-off-by: default avatarRafał Miłecki <rafal@milecki.pl>
      20a0d435
    • Rafał Miłecki's avatar
      kernel: backport mtd commit converting partitions doc syntax · 7495acb5
      Rafał Miłecki authored
      
      
      1. It's useful for developing & validating DTS files inside OpenWrt
      2. This will allow backporting later changes that depend on it
      Signed-off-by: default avatarRafał Miłecki <rafal@milecki.pl>
      7495acb5
    • John Audia's avatar
      kernel: bump 5.4 to 5.4.91 · 1bd005ea
      John Audia authored
      
      
      All modification made by update_kernel.sh in a fresh clone without
      existing toolchains.
      
      Build system: x86_64
      Build-tested: ipq806x/R7800, bcm27xx/bcm2711
      Run-tested: ipq806x/R7800
      
      No dmesg regressions, everything functional
      Signed-off-by: default avatarJohn Audia <graysky@archlinux.us>
      Tested-by: Curtis Deptuck <curtdept@me.com> [x86/64]
      1bd005ea
    • Sven Eckelmann's avatar
      ath79: Add support for OpenMesh MR1750 v2 · 0988e03f
      Sven Eckelmann authored
      Device specifications:
      ======================
      
      * Qualcomm/Atheros QCA9558 ver 1 rev 0
      * 720/600/240 MHz (CPU/DDR/AHB)
      * 128 MB of RAM
      * 16 MB of SPI NOR flash
        - 2x 7 MB available; but one of the 7 MB regions is the recovery image
      * 3T3R 2.4 GHz Wi-Fi (11n)
      * 3T3R 5 GHz Wi-Fi (11ac)
      * 6x GPIO-LEDs (2x wifi, 2x status, 1x lan, 1x power)
      * 1x GPIO-button (reset)
      * external h/w watchdog (enabled by default))
      * TTL pins are on board (arrow points to VCC, then follows: GND, TX, RX)
      * 1x ethernet
        - AR8035 ethernet PHY (RGMII)
        - 10/100/1000 Mbps Ethernet
        - 802.3af POE
        - used as LAN interface
      * 12-24V 1A DC
      * internal antennas
      
      Flashing instructions:
      ======================
      
      Various methods can be used to install the actual image on the flash.
      Two easy ones are:
      
      ap51-flash
      ----------
      
      The tool ap51-flash (https://github.com/ap51-flash/ap51-flash
      
      ) should be
      used to transfer the image to the u-boot when the device boots up.
      
      initramfs from TFTP
      -------------------
      
      The serial console must be used to access the u-boot shell during bootup.
      It can then be used to first boot up the initramfs image from a TFTP server
      (here with the IP 192.168.1.21):
      
         setenv serverip 192.168.1.21
         setenv ipaddr 192.168.1.1
         tftpboot 0c00000 <filename-of-initramfs-kernel>.bin && bootm $fileaddr
      
      The actual sysupgrade image can then be transferred (on the LAN port) to the
      device via
      
        scp <filename-of-squashfs-sysupgrade>.bin root@192.168.1.1:/tmp/
      
      On the device, the sysupgrade must then be started using
      
        sysupgrade -n /tmp/<filename-of-squashfs-sysupgrade>.bin
      Signed-off-by: default avatarSven Eckelmann <sven@narfation.org>
      [rebase, add LED migration]
      Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      0988e03f
    • Sven Eckelmann's avatar
      ath79: Add support for OpenMesh MR1750 v1 · ae7680dc
      Sven Eckelmann authored
      Device specifications:
      ======================
      
      * Qualcomm/Atheros QCA9558 ver 1 rev 0
      * 720/600/240 MHz (CPU/DDR/AHB)
      * 128 MB of RAM
      * 16 MB of SPI NOR flash
        - 2x 7 MB available; but one of the 7 MB regions is the recovery image
      * 3T3R 2.4 GHz Wi-Fi (11n)
      * 3T3R 5 GHz Wi-Fi (11ac)
      * 6x GPIO-LEDs (2x wifi, 2x status, 1x lan, 1x power)
      * 1x GPIO-button (reset)
      * external h/w watchdog (enabled by default))
      * TTL pins are on board (arrow points to VCC, then follows: GND, TX, RX)
      * 1x ethernet
        - AR8035 ethernet PHY (RGMII)
        - 10/100/1000 Mbps Ethernet
        - 802.3af POE
        - used as LAN interface
      * 12-24V 1A DC
      * internal antennas
      
      Flashing instructions:
      ======================
      
      Various methods can be used to install the actual image on the flash.
      Two easy ones are:
      
      ap51-flash
      ----------
      
      The tool ap51-flash (https://github.com/ap51-flash/ap51-flash
      
      ) should be
      used to transfer the image to the u-boot when the device boots up.
      
      initramfs from TFTP
      -------------------
      
      The serial console must be used to access the u-boot shell during bootup.
      It can then be used to first boot up the initramfs image from a TFTP server
      (here with the IP 192.168.1.21):
      
         setenv serverip 192.168.1.21
         setenv ipaddr 192.168.1.1
         tftpboot 0c00000 <filename-of-initramfs-kernel>.bin && bootm $fileaddr
      
      The actual sysupgrade image can then be transferred (on the LAN port) to the
      device via
      
        scp <filename-of-squashfs-sysupgrade>.bin root@192.168.1.1:/tmp/
      
      On the device, the sysupgrade must then be started using
      
        sysupgrade -n /tmp/<filename-of-squashfs-sysupgrade>.bin
      Signed-off-by: default avatarSven Eckelmann <sven@narfation.org>
      [rebase, apply shared DTSI/device node, add LED migration]
      Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      ae7680dc
    • Adrian Schmutzler's avatar
      ath79: make OpenMesh MR900 DTSI more general · 847cda16
      Adrian Schmutzler authored
      
      
      The OpenMesh MR900 and to-be-added MR1750 family are very similar.
      Make the existing MR900 DTSI more general so it can be used for
      the MR1750 devices as well.
      Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      847cda16
    • Adrian Schmutzler's avatar
      ath79: consolidate common definitions for OpenMesh devices · bcb31149
      Adrian Schmutzler authored
      
      
      The shared image definitions for OpenMesh devices are currently
      organized based on device families. This introduces some duplicate
      code, as the image creation code is mostly the same for those.
      
      This patch thus derives two basic shared definitions that work for
      all devices and only requires a few variables to be moved back to
      the device definitions.
      Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      bcb31149
  5. 19 Jan, 2021 4 commits
    • Sven Eckelmann's avatar
      ath79: apply Engenius ECB1750 style to OpenMesh MR900 RGMII cfg · 4fbdadc0
      Sven Eckelmann authored
      The OpenMesh MR900 is a modified version of the Exx900/Exx1750 family.
      These devices are shipped with an AR803x PHY and had various problems with
      the delay configuration in ar71xx. These problems are now in the past [1]
      and parts of the delay configuration should now be done in the PHY only.
      
      Just switch to the configuration of the ECB1750 to have an already well
      tested configuration for ath79 with the newer kernel versions.
      
      [1] https://github.com/openwrt/openwrt/pull/3505#issuecomment-716050292
      
      Reported-by: default avatarMichael Pratt <mcpratt@pm.me>
      Signed-off-by: default avatarSven Eckelmann <sven@narfation.org>
      4fbdadc0
    • Sven Eckelmann's avatar
      ath79: Add support for OpenMesh MR900 v2 · 31172e53
      Sven Eckelmann authored
      Device specifications:
      ======================
      
      * Qualcomm/Atheros QCA9558 ver 1 rev 0
      * 720/600/240 MHz (CPU/DDR/AHB)
      * 128 MB of RAM
      * 16 MB of SPI NOR flash
        - 2x 7 MB available; but one of the 7 MB regions is the recovery image
      * 3T3R 2.4 GHz Wi-Fi
      * 3T3R 5 GHz Wi-Fi
      * 6x GPIO-LEDs (2x wifi, 2x status, 1x lan, 1x power)
      * 1x GPIO-button (reset)
      * external h/w watchdog (enabled by default))
      * TTL pins are on board (arrow points to VCC, then follows: GND, TX, RX)
      * 1x ethernet
        - AR8035 ethernet PHY (RGMII)
        - 10/100/1000 Mbps Ethernet
        - 802.3af POE
        - used as LAN interface
      * 12-24V 1A DC
      * internal antennas
      
      Flashing instructions:
      ======================
      
      Various methods can be used to install the actual image on the flash.
      Two easy ones are:
      
      ap51-flash
      ----------
      
      The tool ap51-flash (https://github.com/ap51-flash/ap51-flash
      
      ) should be
      used to transfer the image to the u-boot when the device boots up.
      
      initramfs from TFTP
      -------------------
      
      The serial console must be used to access the u-boot shell during bootup.
      It can then be used to first boot up the initramfs image from a TFTP server
      (here with the IP 192.168.1.21):
      
         setenv serverip 192.168.1.21
         setenv ipaddr 192.168.1.1
         tftpboot 0c00000 <filename-of-initramfs-kernel>.bin && bootm $fileaddr
      
      The actual sysupgrade image can then be transferred (on the LAN port) to the
      device via
      
        scp <filename-of-squashfs-sysupgrade>.bin root@192.168.1.1:/tmp/
      
      On the device, the sysupgrade must then be started using
      
        sysupgrade -n /tmp/<filename-of-squashfs-sysupgrade>.bin
      Signed-off-by: default avatarSven Eckelmann <sven@narfation.org>
      [rebase, add LED migration]
      Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      31172e53
    • Sven Eckelmann's avatar
      ath79: Add support for OpenMesh MR900 v1 · e06c9eec
      Sven Eckelmann authored
      Device specifications:
      ======================
      
      * Qualcomm/Atheros QCA9558 ver 1 rev 0
      * 720/600/240 MHz (CPU/DDR/AHB)
      * 128 MB of RAM
      * 16 MB of SPI NOR flash
        - 2x 7 MB available; but one of the 7 MB regions is the recovery image
      * 3T3R 2.4 GHz Wi-Fi
      * 3T3R 5 GHz Wi-Fi
      * 6x GPIO-LEDs (2x wifi, 2x status, 1x lan, 1x power)
      * 1x GPIO-button (reset)
      * external h/w watchdog (enabled by default))
      * TTL pins are on board (arrow points to VCC, then follows: GND, TX, RX)
      * 1x ethernet
        - AR8035 ethernet PHY (RGMII)
        - 10/100/1000 Mbps Ethernet
        - 802.3af POE
        - used as LAN interface
      * 12-24V 1A DC
      * internal antennas
      
      Flashing instructions:
      ======================
      
      Various methods can be used to install the actual image on the flash.
      Two easy ones are:
      
      ap51-flash
      ----------
      
      The tool ap51-flash (https://github.com/ap51-flash/ap51-flash
      
      ) should be
      used to transfer the image to the u-boot when the device boots up.
      
      initramfs from TFTP
      -------------------
      
      The serial console must be used to access the u-boot shell during bootup.
      It can then be used to first boot up the initramfs image from a TFTP server
      (here with the IP 192.168.1.21):
      
         setenv serverip 192.168.1.21
         setenv ipaddr 192.168.1.1
         tftpboot 0c00000 <filename-of-initramfs-kernel>.bin && bootm $fileaddr
      
      The actual sysupgrade image can then be transferred (on the LAN port) to the
      device via
      
        scp <filename-of-squashfs-sysupgrade>.bin root@192.168.1.1:/tmp/
      
      On the device, the sysupgrade must then be started using
      
        sysupgrade -n /tmp/<filename-of-squashfs-sysupgrade>.bin
      Signed-off-by: default avatarSven Eckelmann <sven@narfation.org>
      [rebase, add LED migration]
      Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      e06c9eec
    • Sven Eckelmann's avatar
      ath79: apply Engenius EAP600 style to OpenMesh MR600 RGMII cfg · 7b772e07
      Sven Eckelmann authored
      The OpenMesh MR600 is a modified version of the EAP600 family. These
      devices are shipped with an AR803x PHY and had various problems with the
      delay configuration in ar71xx. These problems are now in the past [1] and
      parts of the delay configuration should now be done in the PHY only.
      
      Just switch to the configuration of the EAP600 to have an already well
      tested configuration for ath79 with the newer kernel versions.
      
      [1] https://github.com/openwrt/openwrt/pull/3505#issuecomment-716050292
      
      Reported-by: default avatarMichael Pratt <mcpratt@pm.me>
      Signed-off-by: default avatarSven Eckelmann <sven@narfation.org>
      7b772e07