aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ramips/dts
Commit message (Collapse)AuthorAgeFilesLines
* ramips: specify "firmware" partition formatINAGAKI Hiroshi2018-11-29246-0/+246
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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: INAGAKI Hiroshi <musashino.open@gmail.com>
* ramips: bdcom-wap2100: Change DTS license to GPL-2.0-or-later OR MITPetr Štetiar2018-11-291-0/+1
| | | | | | | | Having MIT as alternative is sometimes preferred by upstream maintainers and allows sharing that simple code with other projects. We don't really want multiple DTS versions for the same device. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: fix MTD EEPROM offset for TL-WR840N v5Felix Fietkau2018-11-291-1/+1
| | | | | | | The previous offset was invalid and pointed to the end of the partition, which was causing issues with mt76 Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ramips: bdcom-wap2100: Enable mt7610e 5GHz radioPetr Štetiar2018-11-281-0/+12
| | | | | | | | | | | | The 5GHz radio of this device uses an mt7610e PCI-E chip, which has been recently started to be supported. mt76x0e 0000:01:00.0: card - bus=0x1, slot = 0x0 irq=4 mt76x0e 0000:01:00.0: ASIC revision: 76100002 mt76x0e 0000:01:00.0: Firmware Version: 0.1.00 mt76x0e 0000:01:00.0: EEPROM ver:01 fae:00 Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: bdcom-wap2100: Set firmware partition format to denx,uimagePetr Štetiar2018-11-281-0/+1
| | | | | | | | | | | Specify firmware partition format to denx,uimage in compatible DTS property. 2 uimage-fw partitions found on MTD device firmware Creating 2 MTD partitions on "firmware": 0x000000000000-0x00000017f72b : "kernel" 0x00000017f72b-0x000000f70000 : "rootfs" Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: bdcom-wap2100: Fix boot failure by adding partitions compatible propertyPetr Štetiar2018-11-281-0/+1
| | | | | | | | | | | | | | Flash partitions were moved under partition table node, but addition of compatible property was omitted which lead to following boot failure: VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: 1f00 16384 mtdblock0 (driver?) Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Fixes: e4d9217f (ramips: improve BDCOM WAP2100-SK support) Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: mt7620: add DIR-810L's mt7610e 5 GHz radioRoger Pueyo Centelles2018-11-281-0/+8
| | | | | | | | | | The 5 GHz radio of this device uses an mt7610e pci-e chip, which has been recently added support. Tested on the actual device as AP and client, TCP throughput ~90 Mbps U/D. Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
* ramips: add support for UniElec U7621-06-512M-64M variantNishant Sharma2018-11-281-0/+92
| | | | | | | | | | | | | | | | | | | | | | Add support for UniElec U7621-06 variant with 512MB RAM and 64MB flash. Additional specs are below: CPU: MT7621 (880Mhz) Bootloader: Ralink U-Boot Flash: 64MB - U-Boot identifies as Macronix MX66L51235F - kernel identifies as MX66L51235l (65536 Kbytes) RAM: 512MB Rest of the details as per commit 46ab81e405d2 ("ramips add support for UniElec U7621-06") Signed-off-by: Nishant Sharma <nishant@unmukti.in> [use generic board detection, add firmware partition compatible, extend firmware partition to use all of the remaining flash space, add a maximum image size matching the firmware partition size] Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: add support for Wavlink WL-WN570HA1Thomas Vincent-Cross2018-11-281-0/+136
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit adds support for the Wavlink WL-WN570HA1, a dual-band PoE wireless router with the following specifications: - CPU: MediaTek MT7688AN 580MHz - Flash: 8MB - RAM: 64MB - Ethernet: 1x 10/100Mbps - 2.4 GHz: 802.11b/g/n SoC, 1T1R, 27 dBm - 5 GHz: 802.11a/n/ac MT7610E, 1T1R, 25 dBm - Antennas: 2x external (1 per radio), detachable - LEDs: 3 programmable + Wi-Fi, WAN/LAN, Power - Buttons: Reset Flashing instructions: Factory U-boot launches a TFTP client if reset button is pressed during power-on. Rename the sysupgrade file and configure TFTP as follows: - Client (WL-WN570HA1) IP: 192.168.10.101 - Server IP: 192.168.10.100 - Filename: firmware.bin Signed-off-by: Thomas Vincent-Cross <me@tvc.id.au> [use generic board detection, add firmware partition compatible] Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix RavPower WD03 SoC dtsi includeMatthias Badaire2018-11-271-1/+1
| | | | | | | | | The RavPower WD03 is a mt7620n based baord. With the change applied, I2C should work now with the RavPower WD03. Signed-off-by: Matthias Badaire <mbadaire@gmail.com> [reworded commit message] Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix GB-PC1/PC2 build errorMathias Kresin2018-11-262-10/+0
| | | | | | | | | | With ed25e3ac02d9 ("ramips: fix some clocks in mt7621.dtsi") the cpuclock node was dropped from the mt7621.dtsi without removing the references to this node from the GB-PC1/PC2 dts files. Remove them now, to fix the build error. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix Lava LR-25G001 invalid led namesMathias Kresin2018-11-261-6/+4
| | | | | | | | | | It has to be <board>:<colour>:<function> and is expected exactly this way by the userspace scripts. While at it, fix some whitespace issues in the dts file and rename the flash node as required upstream. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: rt2880: fix pci cells definitionMathias Kresin2018-11-261-2/+2
| | | | | | | Set the correct number of cells to fix "property has invalid length" dtc compiler warnings. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: improve BDCOM WAP2100-SK supportMathias Kresin2018-11-261-29/+37
| | | | | | | | | | | | | | | | | | | | | Use the generic board detection instead of the target specific one as all recent additions are doing. Setup the USB led via devicetree (a58535771f11) and include the required driver by default. Merge the led userspace setting with an existing identical case. Use the wps led for boot status indication. Move the partitions into a partition table node (6031ab345df8) and drop needless labels. Drop misplaced cells properties (53624c1702e6). Cleanup the pinmux and only switch pins to gpio functions which a referenced as gpio in the dts. Match the maximum image size with the size of the firmware partition. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: add Sanlinking Technologies D240 pinmux quirkMathias Kresin2018-11-261-0/+16
| | | | | | | | | | | | | | The sd function of the nd_sd group configures two of the groups pins as gpios. The pins are used as PCIe reset/power. Due to the driver load order, the pins are configured way to late if triggered by the sd-card driver. To not introduce another kind of driver load order dependency and configure the pins as early as possible, means during pinmux driver load. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: revert fix rt3883 pci pinmuxMathias Kresin2018-11-261-1/+1
| | | | | | | | | | | | | | | This reverts commit dcdc6d9dadf2f97253f7891dacdd5b581d7914b4. Even if described this way in the datasheet, it causes a bootloop on a RT-N56U (v1): of-flash 1c000000.nor-flash: do_map_probe() failed for type cfi_probe of-flash 1c000000.nor-flash: do_map_probe() failed VFS: Cannot open root device “(null)” or unknown-block(0,0): error -6 Fixes: FS#1930 Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: improve Skylab SKW92A supportMathias Kresin2018-11-261-7/+9
| | | | | | | | | | | | | | | | Use the generic board detection instead of the target specific one as all recent additions are doing. Add the wireless led according the gpio number from the datasheet. Rename the board part of the leds to match the name used for the compatible string. Finally, do not hijack the wps led for boot status indication longer than necessary. Merge userspace config into existing cases. Include the manufacture Name in the dts model string. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: add support for Lava LR-25G001Pawel Dembicki2018-11-261-0/+182
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Lava LR-25G001 Wireless Router is based on the MT7620A SoC. Specification: - MediaTek MT7620A (580 Mhz) - 64 MB of RAM - 16 MB of FLASH - 1x 802.11bgn radio - 1x 802.11ac radio (MT7610EN) - 5x 10/100/1000 Mbps AR8337 Switch (1 WAN AND 4 LAN) - 2x external, detachable antennas - 1x USB 2.0 - UART (J3) header on PCB (57600 8n1) - 8x LED (3x GPIO-controlled), 2x button - JBOOT bootloader Known issues: - Work only three Gigabit ports (3/5, 1 WAN and 2LAN) Installation: Apply factory image via http web-gui or JBOOT recovery page How to revert to OEM firmware: - push the reset button and turn on the power. Wait until LED start blinking (~10sec.) - upload original factory image via JBOOT http (IP: 192.168.123.254) Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* ramips: fix some clocks in mt7621.dtsiWeijie Gao2018-11-261-11/+2
| | | | | | | As the cpu clock calculation has been fixed, the clock for gic and spi should be also fixed. Signed-off-by: Weijie Gao <hackpascal@gmail.com>
* ramips: fix cpu clock of mt7621 and add dt clk devicesWeijie Gao2018-11-261-0/+8
| | | | | | | | | | For a long time the mt7621 uses a fixed cpu clock which causes a problem if the cpu frequency is not 880MHz. This patch fixes the cpu clock calculation and adds the cpu/bus clkdev which will be used in dts. Signed-off-by: Weijie Gao <hackpascal@gmail.com>
* ramips: fix register range of memc node in mt7621.dtsiWeijie Gao2018-11-261-1/+1
| | | | | | | The memc node from mt7621.dtsi has incorrect register resource. Fix it according to the programming guide. Signed-off-by: Weijie Gao <hackpascal@gmail.com>
* ramips: add mt76x0 node to RT-AC51U device treeLorenzo Bianconi2018-11-261-0/+11
| | | | | | | Introduce mt76x0e device tree node in RT-AC51U dts. Define mt76x0e mtd partition and offset Signed-off-by: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
* ramips: Add support for ZTE ZXECS EBG3130 aka BDCOM WAP2100-SKPetr Štetiar2018-11-261-0/+130
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On the bottom sticker it's branded as ZTE ZXECS EBG3130 device, but in factory OpenWrt image it's referenced as BDCOM WAP2100-SK device. Specifications: - SoC: MediaTek MT7620A - RAM: 128 MB - Flash: 16 MB - Ethernet: 5 FE ports - Wireless radio: 2T2R 2.4 GHz and 1T1R 5 GHz (MT7610EN, unsupported) - UART: 1 x UART on PCB marked as J2 (R=RX, T=TX, G=GND) with 115200 8N1 config - LEDs: Power, FE ports 1-5, WPS, USB, RF 2.4G, RF 5G - Other: USB port, SD card slot and 2x external antennas (non-detachable) Flashing instructions: A) The U-Boot has HTTP based firmware upgrade A1) Flashing notes We've identified so far two different batches of units, unfortunately each batch has different U-Boot bootloader flashed with different default environment variables, thus each batch has different IP address for accessing web based firmware updater. * First batch has web based bootloader IP address 1.1.1.1 * Second batch has web based bootloader IP address 192.168.1.250 In case you can't connect to either of those IPs, you can try to get the default IP address via two methods: A1.1) Serial console, then the IP address is visible during the boot ... HTTP server is starting at IP: 1.1.1.1 raspi_read: from:40004 len:6 HTTP server is ready! ... A1.2) Over telnet/SSH using this command: root@bdcom:/# grep ipaddr= /dev/mtd0 ipaddr=1.1.1.1 A2) Flashing with browser * Change IP address of PC to 1.1.1.2 with 255.255.255.0 netmask * Reboot the device and try to reach web based bootloader in the browser with the following URL http://1.1.1.1 * Quickly select the firmware sysupgrade file and click on the `Update firmware` button, this all has to be done within 10 seconds, bootloader doesn't wait any longer If done correctly, the web page should show UPDATE IN PROGRESS page with progress indicator. Once the flashing completes (it takes roughly around 1 minute), the device will reboot to the OpenWrt firmware A3) Flashing with curl sudo ip addr add 1.1.1.2/24 dev eth0 curl \ --verbose \ --retry 3 \ --retry-delay 1 \ --retry-max-time 30 \ --connect-timeout 30 \ --form "firmware=@openwrt-ramips-mt7620-BDCOM-WAP2100-SK-squashfs-sysupgrade.bin" \ http://1.1.1.1 Now power on the router. B) The U-boot is based on Ralink SDK so we can flash the firmware using UART. 1. Configure PC with a static IP address and setup an TFTP server. 2. Put the firmware into the tftp directory. 3. Connect the UART line as described on the PCB (G=GND, R=RX, T=TX) 4. Power up the device and press 2, follow the instruction to set device and tftp server IP address and input the firmware file name. U-boot will then load the firmware and write it into the flash. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: fix ethernet for f5d8235-v2 boardRoman Yeryomin2018-11-261-1/+12
| | | | | | | | | Belkin F5D8235 v2 has two ethernet switches on board. One internal rt3052 and rtl8366rb on rgmii interface. Looks like internal switch settings were lost in translation to device tree infrastructure. Signed-off-by: Roman Yeryomin <roman@advem.lv>
* ramips: add support for Skylab SKW92A in EVBRussell Senior2018-11-261-0/+120
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Specifically, SKW92A_E16, described here: http://www.skylabmodule.com/wp-content/uploads/SkyLab_SKW92A_V1.04_datasheet.pdf Specification: - MediaTek MT7628N/N (580 Mhz) - 64 MB of RAM - 16 MB of FLASH - 2T2R 2.4 GHz - 5x 10/100 Mbps Ethernet - 2x u.FL - Power by micro-USB connector at USB1 on EVB - UART via micro-USB connector at USB3 on EVB (57600 8n1) - 5x Ethernet LEDs - 1x WLAN LEDs - 1x WPS LED connected by jumper wire from I2S_CK on J20 to WPS_LED pin hole next to daughter board on EVB - WPS/Reset button (S2 on EVB) - RESET button (S1 on EVB) is *not* connected to RST hole next to daughter board Flash instruction: >From Skylab firmware: 1. Associate with SKYLAP_AP 2. In a browser, load: http://10.10.10.254/ 3. Username/password: admin/admin 4. In web admin interface: Administration / Upload Firmware, browse to sysupgrade image, apply, flash will fail with a message: Not a valid firmware. *** Warning: "/var/tmpFW" has corrupted data! 5. Telnet to 10.10.10.254, drops you into a root shell with no credentials 6. # cd /var 7. # mtd_write -r write tmpFW mtd4 Unlocking mtd4 ... Writing from tmpFW to mtd4 ... [e] 8. When flash has completed, you will have booted into your firmware. >From U-boot via TFTP and initramfs: 1. Place openwrt-ramips-mt76x8-skw92a-initramfs-kernel.bin on a TFTP server 2. Connect to serial console at USB3 on EVB 3. Connect ethernet between port 1 (not WAN) and your TFTP server (e.g. 192.168.11.20) 4. Start terminal software (e.g. screen /dev/ttyUSB0 57600) on PC 5. Apply power to EVB 6. Interrupt u-boot with keypress of "1" 7. At u-boot prompts: Input device IP (10.10.10.123) ==:192.168.11.21 Input server IP (10.10.10.3) ==:192.168.11.20 Input Linux Kernel filename (root_uImage) ==:openwrt-ramips-mt76x8-skw92a-initramfs-kernel.bin 8. Move ethernet to port 0 (WAN) on EVB 9. At new OpenWrt console shell, fetch squashfs-sysupgrade image and flash with sysupgrade. >From U-boot via TFTP direct flash: 1. Place openwrt-ramips-mt76x8-skw92a-squashfs-sysupgrade.bin on a TFTP server 2. Connect to serial console at USB3 on EVB (57600 8N1) 3. Connect ethernet between port 1 (not WAN) an your TFTP server (e.g. 192.168.11.20) 4. Start terminal software (e.g. screen /dev/ttyUSB0 57600) on PC 5. Apply power to EVB 6. Interrupt u-boot with keypress of "2" 7. At u-boot prompts: Warning!! Erase Linux in Flash then burn new one. Are you sure?(Y/N) Y Input device IP (10.10.10.123) ==:192.168.11.21 Input server IP (10.10.10.3) ==:192.168.11.20 Input Linux Kernel filename (root_uImage) ==:openwrt-ramips-mt76x8-skw92a-squashfs-sysupgrade.bin 8. When transfer is complete or as OpenWrt begins booting, move ethernet to port 0 (WAN). Signed-off-by: Russell Senior <russell@personaltelco.net>
* ramips: add missing DTS frequency limit for the 5 GHz radio on Archer C20iFelix Fietkau2018-11-061-0/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ramips: fix leds on GL.iNet GL-MT300N-V2Martin Weinelt2018-11-021-1/+1
| | | | | | | The WAN LED now shows the link state. It's color is green, not blue. Signed-off-by: Martin Weinelt <hexa@darmstadt.ccc.de>
* ramips: move status led unset to devicetreeMathias Kresin2018-10-077-14/+0
| | | | | | | Release the led used for boot status indication via devicetree instead of setting a default off trigger in userspace. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: add support for indicating the boot state using multiple ledsMathias Kresin2018-10-07213-213/+852
| | | | | | | | | Use diag.sh version used for other targets supporting different leds for the different boot states. The existing led sequences should be the same as before. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: set F5D8235 v1 usb led trigger via devicetreeMathias Kresin2018-10-071-0/+26
| | | | | | | Assign the usbdev trigger via devicetree and drop the userspace handling of the usb leds. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: set usb led trigger via devicetreeMathias Kresin2018-10-0769-5/+235
| | | | | | | | | | Assign the usbdev trigger via devicetree for all subtargets and drop the userspace handling of the usb leds. With the change all usb ports are triggering the usb led instead of only usb 1.1 XOR usb 2.0 XOR usb 3.0 as it was before. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix power LED DTB for wt3020Emil Muratov2018-09-261-1/+1
| | | | | | | Since c134210 power LED is no longer lights after boot-up. Reversing gpio polarity makes it work as it should be. Signed-off-by: Emil Muratov <gpm@hotplug.ru>
* ramips: add support for TP-Link TL-MR3020 v3Carlo Nel2018-09-061-0/+144
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link TL-MR3020 v3 is a pocket-size router based on MediaTek MT7628N. This PR is based on the work of @meyergru[1], with his permission. Specification: - MediaTek MT7628N/N (575 Mhz) - 64 MB of RAM - 8 MB of FLASH - 2T2R 2.4 GHz - 1x 10/100 Mbps Ethernet Flash instruction: The only way to flash the image in TL-MR3020 v3 is to use tftp recovery mode in U-Boot: 1. Configure PC with static IP 192.168.0.225/24 and tftp server. 2. Rename "openwrt-ramips-mt76x8-tplink_tl-mr3020-v3-squashfs-tftp-recovery.bin" to "tp_recovery.bin" and place it in tftp server directory. 3. Connect PC with the LAN port, press the reset button, power up the router and keep button pressed for around 6-7 seconds, until device starts downloading the file. 4. Router will download file from server, write it to flash and reboot. [1] https://github.com/meyergru/lede-source/commits/TL-MR3020-V3 Signed-off-by: Carlo Nel <carlojnel@gmail.com>
* ramips: add mt7620/1 sdhci pinmuxMathias Kresin2018-09-068-16/+13
| | | | | | | Set the pins to the required mode via the pinmux driver. It allows to get rid of the pinmux related code in the sd card driver. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix mt7620a ND/SD pins pinmuxesMathias Kresin2018-09-064-4/+4
| | | | | | | | | | Drop the nd_sd gpio pinmux in case sdcard is used. They're mutually exclusive and for most of the boards not even used as GPIOs. If the pins are in sdcard mode, the pins ND_WE_N and ND_CS_N are still GPIOs (#45 and #46). Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: reference node by labelMathias Kresin2018-09-061-4/+4
| | | | | | Reference the HC5661A sdhci node by label instead of by the full path. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix rt3883 pinmux for second SPIMathias Kresin2018-08-291-2/+2
| | | | | | | The rt3883 doesn't have a pinmux group named spi_cs1. The cs1 is part of the pci group. The function pci-func enables the second chip select. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix rt3883 pci pinmuxMathias Kresin2018-08-291-1/+1
| | | | | | | | | | The PCI pins need to be set to "PCI Host support one device" to allow the use of one PCI device and flash memory. The pci-fnc function is intended to be used if no PCI is used but flash, nand or the codec functionality is. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: add missing zbt-cpe102 diag ledMathias Kresin2018-08-291-1/+6
| | | | | | | Based on the userspace led configuration it's quite obvious that the 4g-0 led should be used for boot status indication. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: express diag led handling via devicetreeMathias Kresin2018-08-295-3/+12
| | | | | | | Use the default-state property to express the desired led handling in the devicetree source file instead of the userspace. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix multi colour led handlingMathias Kresin2018-08-294-2/+14
| | | | | | | | All boards either have a multi colour led or a single lightpipe. It makes it impossible to handle the LEDs individual. Change the LED config for these boards to take it into account. Signed-off-by: Mathias Kresin <dev@kresin.me>
* treewide: fix some cosmetic glitches in dts filesPaul Wassi2018-08-2714-20/+4
| | | | | | | | | | | - fix single spaces hidden by a tab - replace indentation with spaces by tabs - make empty lines empty - drop trailing whitespace - drop unnecessary blank lines Signed-off-by: Mathias Kresin <dev@kresin.me> Signed-off-by: Paul Wassi <p.wassi@gmx.at>
* ramips: fix mt7620 pinmux for second SPIMathias Kresin2018-08-272-4/+4
| | | | | | | | | | | The mt7620 doesn't have a pinmux group named spi_cs1. The cs1 is part of the "spi refclk" group. The function "spi refclk" enables the second chip select. On reset, the pins of the "spi refclk" group are used as reference clock and GPIO. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix RBM11G partitioningThibaut VARÈNE2018-08-241-9/+36
| | | | | | | | | | | | | | | | | | | | | | | | | This patch improves faf64056ddd46992a75b1e277d94541c7251035c by correcting the partition scheme for the "RouterBoot" section of the flash. The partition scheme initially submitted is incorrect and does not reflect the actual flash structure. The "RouterBoot" section (name matching OEM) is subdivided in several static segments, as they are on ar71xx RB devices albeit with different offsets and sizes. The naming convention from ar71xx has been preserved, except for the bootloaders which are named "bootloader1" and "bootloader2" to avoid confusion with the master "RouterBoot" partition. The preferred 'fixed-partitions' DTS node syntax is used, with nesting support as introduced in 2a598bbaa3. "partition" is used for node names, with associated "label" to match policy set by 6dd94c2781. Leave a note in DTS to explain how the original author selected the SPI speed. Tested-by: Tobias Schramm <tobleminer@gmail.com> Signed-off-by: Thibaut VARÈNE <hacks@slashdirt.org> Reviewed-by: Rafał Miłecki <rafal@milecki.pl>
* ramips: fix RBM33G partitioningThibaut VARÈNE2018-08-241-9/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch improves 5684d087418d176cfdef4e045e1950ca7ba3b09f by correcting the partition scheme for the "RouterBoot" section of the flash. The partition scheme initially submitted is incorrect and does not reflect the actual flash structure. The "RouterBoot" section (name matching OEM) is subdivided in several static segments, as they are on ar71xx RB devices albeit with different offsets and sizes. The naming convention from ar71xx has been preserved, except for the bootloaders which are named "bootloader1" and "bootloader2" to avoid confusion with the master "RouterBoot" partition. The preferred 'fixed-partitions' DTS node syntax is used, with nesting support as introduced in 2a598bbaa3. "partition" is used for node names, with associated "label" to match policy set by 6dd94c2781. The OEM source code also define a "RouterBootFake" partition at the beginning of the secondary flash chip: to avoid trouble if OEM ever makes use of that space, it is also defined here. The resulting partition scheme looks like this: [ 10.114241] m25p80 spi0.0: w25x40 (512 Kbytes) [ 10.118708] 1 fixed-partitions partitions found on MTD device spi0.0 [ 10.125049] Creating 1 MTD partitions on "spi0.0": [ 10.129824] 0x000000000000-0x000000040000 : "RouterBoot" [ 10.136215] 5 fixed-partitions partitions found on MTD device RouterBoot [ 10.142894] Creating 5 MTD partitions on "RouterBoot": [ 10.148032] 0x000000000000-0x00000000f000 : "bootloader1" [ 10.154336] 0x00000000f000-0x000000010000 : "hard_config" [ 10.160665] 0x000000010000-0x00000001f000 : "bootloader2" [ 10.167046] 0x000000020000-0x000000021000 : "soft_config" [ 10.173461] 0x000000030000-0x000000031000 : "bios" [ 10.190191] m25p80 spi0.1: w25q128 (16384 Kbytes) [ 10.194950] 2 fixed-partitions partitions found on MTD device spi0.1 [ 10.201271] Creating 2 MTD partitions on "spi0.1": [ 10.206071] 0x000000000000-0x000000040000 : "RouterBootFake" [ 10.212746] 0x000000040000-0x000001000000 : "firmware" [ 10.307216] 2 minor-fw partitions found on MTD device firmware [ 10.313044] 0x000000040000-0x000000220000 : "kernel" [ 10.319002] 0x000000220000-0x000001000000 : "rootfs" [ 10.324906] mtd: device 9 (rootfs) set to be root filesystem [ 10.330678] 1 squashfs-split partitions found on MTD device rootfs [ 10.336886] 0x000000b40000-0x000001000000 : "rootfs_data" Leave a note in DTS to explain how the original author selected the SPI speed. Tested-by: Tobias Schramm <tobleminer@gmail.com> Signed-off-by: Thibaut VARÈNE <hacks@slashdirt.org> Reviewed-by: Rafał Miłecki <rafal@milecki.pl> [rmilecki: dropped "RouterBootFake" partition] Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ramips: add support for ELECOM WRC-1900GSTNOGUCHI Hiroshi2018-08-233-172/+187
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ELECOM WRC-1900GST is a wireless router, based on Mediatek MT7621A. This is almost same as WRC-2533GST except wireless specs. Specifications: - SoC : MT7621A (four logical CPU cores) - RAM : 128MiB - ROM : 16MiB of SPI NOR-FLASH - wireless : 5GHz : 3T3R up to 1300Mbps/11ac with MT7615 2.4GHz : 3T3R up to 600Mbps/11n with MT7615 - Ethernet : 5 ports, all ports is capable of 1000base-T - Ether switch : MT7530 (MT7621A built-in) - LEDs : 4 LEDs - buttons : 2 buttons and 1 slide-switch - UART : header is on PCB, 57600bps Flash instruction using factory image: 1. Connect the computer to the LAN port of WRC-1900GST 2. Connect power cable to WRC-1900GST and turn on it 3. Access to "https://192.168.2.1/" and open firmware update page ("ファームウェア更新") 4. Select the OpenWrt factory image and click apply ("適用") button 5. Wait ~150 seconds to complete flashing Signed-off-by: NOGUCHI Hiroshi <drvlabo@gmail.com>
* ramips: fix compatibles in SoC dtsiMathias Kresin2018-08-233-3/+3
| | | | | | | The former used compatibles aren't defined anywhere and aren't used by the devicetree source files including them. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix GL-MT300N-V2 SoC compatibleMathias Kresin2018-08-231-1/+1
| | | | | | | | According to abbfcc85259a ("ramips: add support for GL-inet GL-MT300N-V2") the board has a MediaTek MT7628AN. Change the SoC compatible to match the used hardware. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: drop not existing groups from pinmuxMathias Kresin2018-08-2310-10/+10
| | | | | | | | | | | | | | RT5350 neither have rgmii nor a mdio pinmux group. MT7628an doesn't have a jtag group. Having these groups defined might cause a boot panic. The pin controller fails to initialise for kernels > 4.9 if invalid groups are used. If a subsystem references a pin controller configuration node, it can not find this node and errors out. In worst case it's the SPI driver which errors out and we have no root filesystem to mount. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: add support for D-Link DWR-118-A2Cezary Jackiewicz2018-08-151-0/+179
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The DWR-118-A2 Wireless Router is based on the MT7620A SoC. Specification: - MediaTek MT7620A (580 Mhz) - 128 MB of RAM - 16 MB of FLASH - 1x 802.11bgn radio - 1x 802.11ac radio (MT7612EN) - 4x 10/100 Mbps Ethernet (1 WAN and 3 LAN) - 1x 10/100/1000 Mbps Marvell Ethernet PHY (1 LAN) - 2x external, non-detachable antennas - 1x USB 2.0 - UART (J1) header on PCB (57600 8n1) - 7x LED (5x GPIO-controlled), 2x button - JBOOT bootloader Known issues: - GELAN not working - flash is very slow The status led has been assigned to the dwr-118-a2:green:internet led. At the end of the boot it is switched off and is available for other operation. Work correctly also during sysupgrade operation. Installation: Apply factory image via http web-gui or JBOOT recovery page How to revert to OEM firmware: - push the reset button and turn on the power. Wait until LED start blinking (~10sec.) - upload original factory image via JBOOT http (IP: 192.168.123.254) Signed-off-by: Cezary Jackiewicz <cezary@eko.one.pl> Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 03:18:33 +0000