Skip to content
Snippets Groups Projects
  1. Mar 13, 2022
    • Dawsen Gao's avatar
      ramips: Add support for Dual-Q H721 · b3da44b6
      Dawsen Gao authored
      
      Dual-Q H721 is a router platform board, it is the smaller model of
      the U7621-06.
      
      The device has the following specifications:
      
      MT7621AT (880 MHz)
      256 of RAM (DDR3)
      16 MB of FLASH (MX25l12805d SPI)
      5x 1 Gbps Ethernet (MT7621 built-in switch)
      1x M.2 (NGFF) 3.7V 3A max for 5G M.2 Modem work at USB3.0 mode
      1x Minipcie 3.7V 3A max for LTE Modem work at USB2.0 Mode
      2x Minipcie for WIFI card
      4x Lan+1x Wan 10/100M/1000M RJ45 port
      14x LEDs (1x GPIO-controlled)
      1x reset button
      1x UART header (4-pins)
      1x mico SD-card reader
      1x DC jack for main power (5~27 V)
      
      The following has been tested and is working:
      
      Ethernet switch
      miniPCIe slots (tested with Wi-Fi cards and LTE modem cards)
      miniSIM slot (works with normal size simcard)
      sysupgrade
      reset button
      micro SD-card reader
      
      Installation:
      
      This board has no locked down bootloader. The seller can be asked to
      install openwrt, so upgrades are standard sysupgrade method.
      
      Recovery:
      
      This board contains a Chinese, closed-source bootloader called Breed
      (Boot and Recovery Environment for Embedded Devices). Breed supports web
      recovery and to enter it, you keep the reset button pressed for around
      5 seconds during boot. Your machine will be assigned an IP through DHCP
      and the router will use IP address 192.168.1.1. The recovery website is
      in Chinese, but is easy to use. Click on the second item in the list to
      access the recovery page, then the second item on the next page is where
      you select the firmware. In order to start the recovery, you click the
      button at the bottom.
      
      Signed-off-by: default avatarDawsen Gao <dawsen_gao@163.com>
      [change author name (used SoB one), add ethernet pinctrl,
       apply sorting to device recipe]
      Signed-off-by: default avatarSungbo Eo <mans0n@gorani.run>
      b3da44b6
  2. Feb 26, 2022
  3. Jul 19, 2021
  4. Oct 02, 2020
    • Adrian Schmutzler's avatar
      ramips: remove model name from LED labels · c846dd91
      Adrian Schmutzler authored
      
      Like in the previous patch for ath79 target, this will remove the
      "devicename" from LED labels in ramips as well.
      
      The devicename is removed in DTS files and 01_leds, consolidation
      of definitions into DTSI files is done where (easily) possible,
      and migration scripts are updated.
      
      For the latter, all existing definitions were actually just
      devicename migrations anyway. Therefore, those are removed and
      a common migration file is created in target base-files. This is
      actually another example of how the devicename removal makes things
      easier.
      
      Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      c846dd91
  5. 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
  6. May 09, 2020
  7. May 08, 2020
  8. Apr 04, 2020
  9. Dec 23, 2019
  10. Oct 21, 2019
  11. Sep 28, 2019
  12. Jul 11, 2019
  13. Jul 10, 2019
  14. Feb 05, 2019
  15. Nov 29, 2018
    • INAGAKI Hiroshi's avatar
      ramips: specify "firmware" partition format · d70ec300
      INAGAKI Hiroshi authored
      
      Specify firmware partition format by compatible string.
      
      formats in ramips:
      
      - denx,uimage
      - tplink,firmware
      - seama
      
      It's unlikely but the firmware splitting might not work any longer for
      the following boards, due to a custom header:
      
      - EX2700: two uImage headers
      - BR-6478AC-V2: edimax-header
      - 3G-6200N: edimax-header
      - 3G-6200NL: edimax-header
      - BR-6475ND: edimax-header
      - TEW-638APB-V2: umedia-header
      - RT-N56U: mkrtn56uimg
      
      But it rather looks like the uImage splitter is fine with the extra
      header.
      
      The following dts are not touched, due to lack of a compatible string in
      the matching firmware splitter submodule:
      
      - CONFIG_MTD_SPLIT_JIMAGE_FW
          DWR-116-A1.dts
          DWR-118-A2.dts
          DWR-512-B.dts
          DWR-921-C1.dts
          LR-25G001.dts
      - CONFIG_MTD_SPLIT_TRX_FW
          WCR-1166DS.dts
          WSR-1166.dts
      - CONFIG_MTD_SPLIT_MINOR_FW
          RBM11G.dts
          RBM33G.dts
      - CONFIG_MTD_SPLIT_LZMA_FW
          AR670W.dts
      - CONFIG_MTD_SPLIT_WRGG_FW
          DAP-1522-A1.dts
      
      Signed-off-by: default avatarINAGAKI Hiroshi <musashino.open@gmail.com>
      d70ec300
  16. Oct 07, 2018
  17. Aug 04, 2018
    • Alex Maclean's avatar
      ramips: move partitions into partition table node · 6031ab34
      Alex Maclean authored
      
      Starting with kernel 4.4, the use of partitions as direct subnodes of the
      mtd device is discouraged and only supported for backward compatiblity
      reasons.
      
      Signed-off-by: default avatarAlex Maclean <monkeh@monkeh.net>
      6031ab34
    • Mathias Kresin's avatar
      ramips: fix dtc warnings · 53624c17
      Mathias Kresin authored
      
      Fix individual boards dtc warnings or obvious mistakes.
      
      Signed-off-by: default avatarMathias Kresin <dev@kresin.me>
      53624c17
    • Mathias Kresin's avatar
      ramips: fix pci/pcie related dtc warnings · f9b8328d
      Mathias Kresin authored
      
      Add the ranges property to the PCI bridges where missing. Add the unit
      address to PCI bridge where missing.
      
      Rework the complete rt3883 pci node. Drop the PCI unit nodes from the
      dtsi. They are not used by any dts file and should be rather in the dts
      than in the SoC dtsi. Express the PCI-PCI bridge in a clean devicetree
      syntax. The ralink,pci-slot isn't used by any driver, drop it. Move the
      pci interrupt controller out of the pci node. It doesn't share the same
      reg and therefore should be an independent/SoC child node.
      
      Move the pci related rt3883 pinctrl setting to the dtsi instead of
      defining the very same for each rt3883 board.
      
      If the device_type property is used for PCI units, the unit is treated
      as pci bridge which it isn't. Drop it for PCI units.
      
      Reference pci-bridges or the pci node defined in the dtsi instead of
      recreating the whole node hierarchy. It allows to change the referenced
      node in the dtsi without the need to touch all dts.
      
      Fix the PCI(e) wireless unit addresses. All our PCI(e) wireless chips
      are the first device on the bus. The unit address has to be the bus
      address instead of the PCI vendor/device id.
      
      Signed-off-by: default avatarMathias Kresin <dev@kresin.me>
      f9b8328d
  18. Jul 16, 2018
  19. Jun 01, 2018
  20. May 30, 2018
    • Rosen Penev's avatar
      ramips: Fix WiFi after 5f7396eb · 02f815d1
      Rosen Penev authored
      
      That commit exposed a bug in the DTS files used by mt7621 where the wrong
      reg value for pcie1 (and potentially pcie2) was being used. This was
      causing WiFi failures for interfaces in pcie1.
      
      eg. 2.4GHz working but not 5GHz.
      
      As all of these dts entries are already specified in mt7621.dtsi, remove
      them.
      
      Signed-off-by: default avatarRosen Penev <rosenp@gmail.com>
      02f815d1
  21. Oct 25, 2017
  22. Aug 03, 2017
  23. Jul 29, 2017
  24. Feb 01, 2017
  25. Nov 23, 2016
    • Mathias Kresin's avatar
      ramips: cleanup dts files of mt7621 based boards · f1d0eba3
      Mathias Kresin authored
      
      Fix a typo in mt7621.dtsi compatible string. Disable spi, sdhci and pci
      in mt7621.dtsi and enable the nodes in the indiviual board dts files.
      The nodes require further device specific configuration anyway.
      
      Remove the m25p80@0 spi child node from mt7621.dtsi and add the
      chunked-io parameter to the individual board dts files. Fix the spi
      flash compatible string for the WNDR3700V5.
      
      Drop the mt7621-eval-board compatible string for all boards which are
      not the eval board.
      
      Drop the linux,modalias parameter from spi flash node.
      
      Remove the xhci node from board files, it is already enabled in dtsi.
      Disable xhci for boards not having usb ports populated.
      
      Signed-off-by: default avatarMathias Kresin <dev@kresin.me>
      f1d0eba3
  26. Nov 13, 2016
    • Mathias Kresin's avatar
      treewide: dts: use keycode defines from input dt-binding · 2b55c83e
      Mathias Kresin authored
      
      All compiled device tree files not mentioned are binary identical to the
      former ones.
      
      Fix the obvious decimal/hex confusion for the power key of ramips/M2M.dts.
      
      Due to the include of the input binding header, the BTN_* node names in:
      
        - ramips/GL-MT300A.dts
        - ramips/GL-MT300N.dts
        - ramips/GL-MT750.dts
        - ramips/Timecloud.dts
      
      will be changed by the compiler to the numerical equivalent.
      
      Move the binding include of lantiq boards to the file where they are
      used the first time to hint the user where the values do come from.
      
      Signed-off-by: default avatarMathias Kresin <dev@kresin.me>
      2b55c83e
  27. Jun 20, 2016
  28. May 18, 2016
  29. May 12, 2016
  30. Jan 19, 2016
  31. Dec 18, 2015
  32. Dec 11, 2015
Loading