Skip to content
Snippets Groups Projects
  1. Jan 15, 2022
    • Michael Pratt's avatar
      ramips: fix reboot for remaining 32 MB boards · 74516f43
      Michael Pratt authored
      
      The following devices have a Winbond W25Q256FV flash chip,
      which does not have the RESET pin enabled by default,
      and otherwise would require setting a bit in a status register.
      
      Before moving to Linux 5.4, we had the patch:
      0053-mtd-spi-nor-add-w25q256-3b-mode-switch.patch
      which kept specific flash chips with explicit 3-byte and 4-byte address modes
      to stay in 3-byte address mode while idle (after an erase or write)
      by using a custom flag SPI_NOR_4B_READ_OP that was part of the patch.
      
      this was obsoleted by the patch:
      481-mtd-spi-nor-rework-broken-flash-reset-support.patch
      which uses the newer upstream flag SNOR_F_BROKEN_RESET
      for devices with a flash chip that cannot be hardware reset with RESET pin
      and therefore must be left in 3-byte address mode when idle.
      
      The new patch requires that the DTS of affected devices
      have the property "broken-flash-reset", which was not yet added for most of them.
      
      This commit adds the property for remaining affected devices in ramips target,
      specifically because of the flash chip model.
      
      However, it is possible that there are other devices
      where the flash chip uses an explicit 4-byte address mode
      and the RESET pin is not connected to the SOC on the board,
      and those DTS would also need this property.
      
      Ref: 22d982ea ("ramips: add support for switching between 3-byte and 4-byte addressing")
      Ref: dfa521f1 ("generic: spi-nor: rework broken-flash-reset")
      Signed-off-by: default avatarMichael Pratt <mcpratt@pm.me>
      74516f43
  2. Sep 25, 2020
    • Adrian Schmutzler's avatar
      ramips: move dts-v1 statement to top-level DTSI files · 621297e8
      Adrian Schmutzler authored
      
      The "/dts-v1/;" identifier is supposed to be present once at the
      top of a device tree file after the includes have been processed.
      
      In ramips, we therefore requested to have in the DTS files so far,
      and omit it in the DTSI files. However, essentially the syntax of
      the parent mtxxxx/rtxxxx DTSI files already determines the DTS
      version, so putting it into the DTS files is just a useless repetition.
      
      Consequently, this patch puts the dts-v1 statement into the top-level
      SoC-based DTSI files, and removes all other occurences.
      Since the dts-v1 statement needs to be before any other definitions,
      this also moves the includes accordingly where necessary.
      
      Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      621297e8
  3. Nov 03, 2019
    • Kristian Evensen's avatar
      ramips: add support for ZBT WE1026-H · 5f108bbc
      Kristian Evensen authored
      
      This commit adds support for the ZBT WE1026-H, an outdoor AP with
      support for adding an internal LTE modem. The detailed specs are:
      
      * CPU: MT7620A
      * 2x 10/100Mbps Ethernet (LAN port has passive PoE support).
      * 16/32 MB Flash.
      * 128/256 MB RAM.
      * 1x USB 2.0 port.
      * 1x mini-PCIe slot (only USB2.0 bus).
      * 1x SIM slot (standard size).
      * 1x 2.4Ghz WIFI (rt2800).
      * 1x button.
      * 6x LEDS (4 GPIO-controlled).
      * 1x micro-SD reader.
      
      The following have been tested and working:
      - Ethernet switch
      - Wifi
      - Mini-PCIe slot + SIM slot
      - USB port
      - microSD slot
      - sysupgrade
      - reset button
      
      Installation and recovery:
      
      In order to install OpenWRT the first time or ito recover the router,
      you can use the web-based recovery system. Keep the reset button pressed
      during boot and access 192.168.1.1 in your browser when your machine
      obtains an IP address. Upload the firmware to start the recovery
      process.
      
      Notes:
      
      * When binding the USB LED to a usbport, the LED is switched on all the
      time due to the presence of an internal hub. Thus, it does not really
      signal any USB-information.
      
      * I only have the 32MB version and have only added support for this
      device. However, the files are structured so that adding support for the
      16MB version should be easy.
      
      * Only the LAN port is accessible from the outside of the casing and LEDs
      are not visible.
      
      Signed-off-by: default avatarKristian Evensen <kristian.evensen@gmail.com>
      [rebased onto base-files split, minor style fixes, removed use of
      USB led as power LED]
      Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      5f108bbc
Loading