aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ramips
Commit message (Collapse)AuthorAgeFilesLines
* kernel: bump 4.14 to 4.14.171Koen Vandeputte2020-02-245-14/+14
| | | | | | | | | | | | Refreshed all patches. Fixes: - CVE-2013-1798 Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ramips: append tail to WF2881 initramfs imageSungbo Eo2020-02-211-0/+8
| | | | | | | | | | | | | 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: Sungbo Eo <mans0n@gorani.run> (cherry picked from commit be3e98ce26da5e737744427e1d59dd1c0508edef)
* ramips: reenable image creation for the D-Link DIR-645Mason Clarke2020-02-011-1/+0
| | | | | | | | | | | | | | | | | | | 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 62d5ece) with the default 19.07 release config, and I cannot confirm the report that commit 2607c02ed599b6118ba26e2f35e7c828c21d7275 ("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 2607c02ed599b6118ba26e2f35e7c828c21d7275. Signed-off-by: Mason Clarke <mclarke2355@gmail.com>
* ramips: use tpt DTS trigger for TP-Link TL-MR3020 v3 and TL-WA801ND v5Jan Alexander2020-01-303-6/+4
| | | | | | | | | | | | | | | | | This converts the TP-Link TL-MR3020v3 board to use the WLAN throughput LED trigger in order to react to all VAPs. It also moves the WLAN trigger config of the TP-Link TL-WA801NDv5 to the DTS and merges the now identical LAN LED configs. Verified these changes on a TL-MR3020v3 and TL-WA801NDv5. Signed-off-by: Jan Alexander <jan@nalx.net> [changed commit title and extended commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> [added comment about test result on TL-WA801ND v5] Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 20eb45da4fc19c12ea2073471992eeaf9d602fa5)
* ramips: remove duplicate DEVICE_PACKAGES for TP-Link Archer C20iAdrian Schmutzler2020-01-291-1/+0
| | | | | | | | | | DEVICE_PACKAGES is specified twice for the same device. Remove the first (=older) assignment. Fixes: 40692f0fb55c ("ramips: mt7620: select only the matching mt76 driver") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 4ecd6510bf8877dcd07561045852726ffbab8814)
* ramips: mt7621: ubnt-erx: allow sysupgrade from masterPetr Štetiar2020-01-241-0/+2
| | | | | | | | | | | | Currently it's not possible to downgrade from master: Device ubiquiti,edgerouterx not supported by this image Supported devices: ubnt-erx So fix it by adding a DTS based device name from master into SUPPORTED_DEVICES list. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: rt305x: remove unnecessary mediatek,portmapSungbo Eo2020-01-212-2/+0
| | | | | | | | | | "#mediatek,portmap" is not a valid property name. If mediatek,portmap equals 0x0, then the esw driver ditches it and uses the default value, 0x3f. Signed-off-by: Sungbo Eo <mans0n@gorani.run> (cherry picked from commit f87281b2956110f10af9eb23fc6d327dfde7ab42)
* ramips: mt76x8: fix bogus mediatek,portmapSungbo Eo2020-01-2117-13/+58
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | mt76x8 uses esw_rt3050 driver, which does not accept mediatek,portmap with string values. Convert the strings to integers to make it work. According to its switch setup, WRTnode 2P/2R have a WAN port at port 0, so the correct value should be 0x3e. tplink_8m.dtsi uses "llllw", but it does not match switch setups of any device using the DTSI. Remove it from the DTSI and add correct value to DTS for each device. These devices have a WAN port at port 0. Set the value to 0x3e. - tplink,archer-c20-v4 - tplink,archer-c50-v3 - tplink,tl-mr3420-v5 - tplink,tl-wr840n-v4 - tplink,tl-wr841n-v13 - tplink,tl-wr842n-v5 These devices have only one ethernet port. They don't need portmap setting. - tplink,tl-wa801nd-v5 - tplink,tl-wr802n-v4 - tplink,tl-wr902ac-v3 Signed-off-by: Sungbo Eo <mans0n@gorani.run> (backported from commit 7a387bf9a0d73f7c581e2c9aeae6476588100e2c) [removed TL-WR841N v14 which is not present in 19.07] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: fix portmap for TP-Link Archer C50 v4Maxim Anisimov2020-01-211-1/+1
| | | | | | | According to 02_network portmap is wan=0 lan1=1 lan2=2 lan3=3 lan4=4 Signed-off-by: Maxim Anisimov <maxim.anisimov.ua@gmail.com> (cherry picked from commit ebf535a6cfefef5b0afb74cb01c9a17ab242b85b)
* ramips: mt7620/mt7621: remove invalid mediatek,portmapSungbo Eo2020-01-211-3/+2
| | | | | | | | | | | | | mt7620 and mt7621 use mt7530 driver, which only accepts "llllw", "wllll", and "lwlll" values. According to its switch setup, Mi Router 3G v2 has a WAN port at port 4, so the correct value should be "llllw". Signed-off-by: Sungbo Eo <mans0n@gorani.run> (backported from commit d3c0a944059bb0d45c3b56278249100258378b0c) [removed devices not in 19.07] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: add factory image for Netgear R6350Christoph Krapp2020-01-211-1/+6
| | | | | | | | | | | | | | This adds factory image generation for all three devices. These images can be flashed via WebUI for easy installation. Thanks to David Bauer for the inspiration. Signed-off-by: Christoph Krapp <achterin@googlemail.com> [altered commit to only include the R6350] Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 3c8df280a96bbd81357d6eb52845e6b5fa7162fe) Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* ramips: add mt7615e support to Netgear R6350Christoph Krapp2020-01-212-1/+10
| | | | | Signed-off-by: Christoph Krapp <achterin@googlemail.com> (cherry picked from commit 9861fa7abab97cb928aaa6cd5732a413d973ac95)
* ramips: fix HiWiFi HC5962 status LEDDENG Qingfang2020-01-181-3/+4
| | | | | | | | | | Match LED behavior to stock firmware: Red: booting White: running Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn> (cherry picked from commit 9a3c9a96563c3c3fb1e15b791d9117b193fed7a6)
* ramips: fix HiWiFi HC5962 switch configurationDENG Qingfang2020-01-181-1/+4
| | | | | | | | HC5962 has only 3 LAN ports, switch port 0 is unused Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn> (backported from commit 68f49df31507454f86b72a5c1e250505176baed7) Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: add kmod-mt7615e to Xiaomi Mi Router 3 Pro imagesOzgur Can Leonard2020-01-182-3/+5
| | | | | | | Now that the mt76/mt7615e driver is in Openwrt, might as well use it. Signed-off-by: Ozgur Can Leonard <ozgurcan@gmail.com> (cherry picked from commit d7c082ba4f7de97b3708d1f4a064954ffc774778)
* ramips: fix wps leds/btn for TP-Link TL-WA801ND v5Jan Alexander2020-01-171-4/+16
| | | | | | | | | | | - fix color and active mode for existing wps led - add green wps led - add wps button Signed-off-by: Jan Alexander <jan@nalx.net> [wrap line] Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 26105974e7f9758cd4bc443ce0322983f818acd5)
* ramips: mt7621: disable images for gehua_ghl-r-001Petr Štetiar2020-01-141-0/+1
| | | | | | | | | | | This device OOPs during the boot due to broken flash. It can be probably fixed with `broken-flash-reset` once ramips is on 4.19 kernel. So disable images for this device until its fixed. Ref: FS#2695, PR#2483 Signed-off-by: Petr Štetiar <ynezz@true.cz> (cherry picked from commit 28080d54d217fb4ab112e079f69462fee695dbf8)
* ramips: fix leds for TP-Link Archer C20 v4Maxim Anisimov2020-01-122-2/+3
| | | | | | | | | | | - add "gpio" group for wan_orange led - use tpt triggers for wifi led indication - add wifi 5 GHz led support Signed-off-by: Maxim Anisimov <maxim.anisimov.ua@gmail.com> [slight commit message adjustment, backport] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 3a538db60abfc50b47ce1774f66d489700a50c00)
* ramips: Fix sysupgrade for Xiaomi mir3gHauke Mehrtens2020-01-061-3/+4
| | | | | | | | | | | | | | | | | | | This mostly reverts the original commit e9929ebeeaef ("ramips: Fix sysupgrade for Xiaomi mir3g") and replaces it with setting the BOARD_NAME to the old value. This way the folder in the tar will be named sysupgrade-mir3g and not sysupgrade-xiaomi_mir3g and the sysupgrade in OpenWrt 18.06 can find it. Without this change sysupgrade from 18.06 to 19.07 is only possible with the -F option. I tested the following sysupgrades successfully without -F 18.06 -> 19.07 19.07 -> master master -> 19.07 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ramips: Fix sysupgrade for Xiaomi mir3gHauke Mehrtens2020-01-051-3/+3
| | | | | | | | | | | | | | | | | Without this change sysupgrade from 18.06 to 19.07 is only possible with the -F option. In OpenWrt 18.06 the nand_do_platform_check() function is called with the board name mir3g only, if the tar does not use mir3g it will fail. OpenWrt 19.07 and later support the metadata with the supported_devices attribute to allow renaming. Do the renaming of the target between 19.07 and master like it is done for some other boards. I tested the following sysupgrades successfully without -F 18.06 -> 19.07 19.07 -> master master -> 19.07 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ramips: remove duplicate dts nodes of MediaTek LinkIt Smart 7688Jack Chen2020-01-051-4/+0
| | | | | | | | There are two identical wmac nodes in the dts file of MediaTek LinkIt Smart 7688, so delete one of them. Signed-off-by: Jack Chen <redchenjs@live.com> (cherry picked from commit 4be271a4867dcf57a122eeb7b42407e7a506915e)
* ramips: fix Archer C20i wireless MAC addressDavid Bauer2020-01-031-0/+3
| | | | | | | | | | | The TP-Link Archer C20i previously had a generic Ralink MAC address set for both radios, as the caldata does only contain a generic MAC address. Set the MAC address from the vendor firmware for both radios to assign unique MAC addresses to every device. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 3b013dcdf8d8aa0e3601e3aac30342318025e32a)
* ramips: fix Archer C2 v1 5GHz MAC addressDavid Bauer2020-01-031-0/+2
| | | | | | | | | | | | The TP-Link Archer C2 v1 previously had a generic Ralink MAC address set for the 5GHz radio (MT7610), as the caldata does only contain a generic MAC address. Set the MAC address from the vendor firmware for the 5GHz radio to assign unique MAC addresses to every device. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit dcc923a4c45b48fcbef4f3964f74fbcaabad335e)
* ramips: add system LED indicators for TP-Link C20iDavid Bauer2020-01-031-1/+8
| | | | | | | | Use the WPS LED to indicate system status like it is done for the TP-Link Archer C2 v1 and many other boards. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit a272fafc9c507820cc62aa12464588bac45f250a)
* ramips: convert TP-Link MT7620 boards to tpt triggerDavid Bauer2020-01-036-5/+7
| | | | | | | | | | | | | This converts all MediaTek MT7620 boards from TP-Link to use the now supported WiFi throughput LED trigger. This way, the LED state now covers all VAPs regardless of their name. Also align all single-WiFi LEDs to represent the state of the 2.4GHz radio. This was not always the case previously, as later-added support for the MT7610 altered the phy probing order. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 1e7c6381f0058e49caab8de54eaad4862732f95d)
* ramips: fix inverted reset button for Ravpower WD03Moritz Warning2020-01-031-1/+1
| | | | | | | The button events "pressed" and "released" were switched. Tested with v18.06.4. Signed-off-by: Moritz Warning <moritzwarning@web.de> (cherry picked from commit 3e1325b219fced91f01d5594503f61d326a93b90)
* ramips: add LED trigger for TL-WR902AC v3 WAN LEDDavid Bauer2019-12-301-0/+1
| | | | | | | | | | | | This adds an LED trigger for the WAN LED on top of the TP-Link TL-WR902AC v3. Currently, only the LED on the port itself shows the link state, while the LED on top of the device stays dark. The WAN port of the device is a hybrid LAN/WAN one, hence why the LED at the port was labled LAN. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit c48b571ad708b9f66efb0c2942291c2d8f1d7780)
* ramips: remove bogus ralink,mtd-eeprom with offset 0x4Adrian Schmutzler2019-12-286-6/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Several devices in mt76x8 subtarget use the following line to set up wmac in their DTS(I) files: ralink,mtd-eeprom = <&factory 0x4> This is strange for several reasons: - They should use mediatek,mtd-eeprom on this SOC - The caldata is supposed to start at 0x0 - The parent DTSI mt7628an.dtsi specifies mediatek,mtd-eeprom anyway, starting from 0x0 - The offset coincides with the default location of the MAC address in caldata Based on the comment in b28e94d4bfa1 ("ramips: MiWiFi Nano fixes"), it looks like the author for this device wanted to actually use mtd-mac-address instead of ralink,mtd-eeprom. A check on the same device revealed that actually the MAC address start at offset 4 there, so the correct caldata offset is 0x0. Based on these findings, and the fact that the expected location on this SOC is 0x0, we remove the "ralink,mtd-eeprom = <&factory 0x4>" statement from all devices in ramips (being only mt7628an anyway). Thanks to Sungbo Eo for finding and researching this. Reported-by: Sungbo Eo <mans0n@gorani.run> Fixes: b28e94d4bfa1 ("ramips: MiWiFi Nano fixes") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 09d38a3bc328d122b0d84fcf6bb53d2bce7373b6)
* ramips: fix USB LED for Belkin F9K1109v1Sungbo Eo2019-12-201-1/+1
| | | | | | | | | | | | | | | Device support for Belkin F9K1109v1 was added using set_usb_led() although this was removed in 772b27c20736 ("ramips: set F5D8235 v1 usb led trigger via devicetree"). Use ucidef_set_led_usbport() instead. Fixes: f2c83532f92c ("ramips: add support for Belkin F9K1109v1") Signed-off-by: Sungbo Eo <mans0n@gorani.run> [rephrase commit title and message, backport] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 1f455418ef1ea67fda710e1b86a9e021bb4a2413)
* ramips: allow JCG_MAXSIZE in kiB in Build/jcg-headerAdrian Schmutzler2019-12-132-2/+4
| | | | | | | | | | | | | | | This allows JCG_MAXSIZE to be specified in kilobytes. This makes this value more consistent and easier comparable with other size variables. This also changes the only occurence of the variable, for Cudy WR1000. This is backported to 19.07 for convenience, as other developers backporting device support might not be aware that JCG_MAXSIZE in kilobytes would not work there. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 0bf4d681d4f2e4bd3c3a61e7fe5dca2a40b1902f)
* ramips: fix number of LAN Ports for Mikrotik RBM33GMartin Schiller2019-12-111-1/+4
| | | | | | | | | The Mikrotik RBM33G has only 2 LAN ports. Signed-off-by: Martin Schiller <ms@dev.tdt.de> [moved node in 02_network to maintain alphabetic sorting; backport] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 3a55c7935d4efdc86575601cb4aa7bc94e3c5e44)
* ramips: fix switch port order for TP-Link Archer C20iWalter Sonius2019-12-111-1/+1
| | | | | | | | | | | | | | | | | | | Physical port order watched from the backside of the C20i (from left to right) is: Internet / 1 / 2 / 3 / 4 Physical Port Switch port WAN 0 LAN 3 1 LAN 4 2 LAN 1 3 LAN 2 4 (not used) 5 CPU 6 Signed-off-by: Walter Sonius <walterav1984@gmail.com> [commit message/title improvements; backport to 19.07] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit a065cd29bf2dfd1ce1f07becd65aef96cec658e7)
* kernel: bump 4.14 to 4.14.158Koen Vandeputte2019-12-102-2/+2
| | | | | | | | | | | | Refreshed all patches. Altered patches: - 400-mtd-add-rootfs-split-support.patch Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ramips: disable ZyXel Keenetic by defaultJo-Philipp Wich2019-11-301-0/+1
| | | | | | | | Disable the ZyXel Keenetic images by default as the device has insufficient flash space for release build images. Ref: https://forum.openwrt.org/t/devices-too-big-to-save-overlay/18161/72 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ramips: disable WR512-3GN 4MB variant by defaultJo-Philipp Wich2019-11-301-0/+1
| | | | | | | | Disable the WR512-3GN 4MB image by default as the device has insufficient flash space for release build images. Ref: https://forum.openwrt.org/t/devices-too-big-to-save-overlay/18161/72 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ramips: disable A5-V11 by defaultJo-Philipp Wich2019-11-301-0/+1
| | | | | | | | Disable the A5-V11 image by default as the device has insufficient flash space for release build images. Ref: https://forum.openwrt.org/t/devices-too-big-to-save-overlay/18161/72 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ramips: disable TP-Link TL-WR840N v5 by defaultJo-Philipp Wich2019-11-291-0/+1
| | | | | | | | Disable the TP-Link TL-WR840N v5 image by default as the device has insufficient flash space for release build images. Ref: https://forum.openwrt.org/t/devices-too-big-to-save-overlay/18161/29 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ramips: disable Sitecom WL-351 by defaultJo-Philipp Wich2019-11-291-0/+1
| | | | | | | | Disable the Sitecom WL-351 image by default as the device has insufficient flash space for release build images. Ref: https://forum.openwrt.org/t/devices-too-big-to-save-overlay/18161/24 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ramips: disable D-Link DIR-645 by defaultJo-Philipp Wich2019-11-291-0/+1
| | | | | | | | Disable the D-Link DIR-645 image by default as the device has insufficient flash space for release build images. Ref: https://forum.openwrt.org/t/devices-too-big-to-save-overlay/18161/23 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ramips: disable D-Link DIR-300 B5/B6/B7 by defaultJo-Philipp Wich2019-11-291-0/+1
| | | | | | | | Disable the D-Link DIR-300 B5/B6/B7 image by default as the device has insufficient flash space for release build images. Ref: https://forum.openwrt.org/t/devices-too-big-to-save-overlay/18161/18 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ramips: disable ASUS RT-N10+ B1 by defaultJo-Philipp Wich2019-11-291-0/+1
| | | | | | | | Disable the ASUS RT-N10+ B1 image by default as the device has insufficient flash space for release build images. Ref: https://forum.openwrt.org/t/devices-too-big-to-save-overlay/18161/1 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* kernel: bump 4.14 to 4.14.156Koen Vandeputte2019-11-292-2/+2
| | | | | | | | | Refreshed all patches. Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ramips: add support for ALFA Network Quad-E4GPiotr Dymacz2019-11-246-13/+265
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ALFA Network Quad-E4G is a universal Wi-Fi/4G platform, which offers three miniPCIe (PCIe, USB 2.0, SIM) and a single M.2 B-key (dual-SIM, USB 3.0) slots, RTC and five Gigabit Ethernet ports with PoE support. Specification: - MT7621A (880 MHz) - 256/512 MB of RAM (DDR3) - 16/32+ MB of FLASH (SPI NOR) - optional second SPI flash (8-pin WSON/SOIC) - 1x microSD (SDXC) flash card reader - 5x 10/100/1000 Mbps Ethernet, with passive PoE support (24 V) in LAN1 - optional 802.3at/af PoE module for WAN - 3x miniPCIe slot (with PCIe and USB 2.0 buses, micro SIM and 5 V) - 1x M.2/NGFF B-key 3042 (USB 3.0/2.0, mini + micro SIM) - RTC (TI BQ32002, I2C bus) with backup battery (CR2032) - external hardware watchdog (EM Microelectronic EM6324) - 1x USB 2.0 Type-A - 1x micro USB Type-B for system serial console (Holtek HT42B534) - 11x LED (5 for Ethernet, 5 driven by GPIO, 1x power indicator) - 3x button (reset, user1, user2) - 1x I2C (4-pin, 2.54 mm pitch) header on PCB - 4x SIM (6-pin, 2.00 mm pitch) headers on PCB - 2x UART2/3 (4-pin, 2.54 mm pitch) headers on PCB - 1x mechanical power switch - 1x DC jack with lock (24 V) Other: - U-Boot selects default SIM slot, based on value of 'default_sim' env variable: '1' or unset -> SIM1 (mini), '2' -> SIM2 (micro). This board has additional logic circuit for M.2 SIM switching. The 'sim-select' will work only if both SIM slots are occupied. Otherwise, always slot with SIM inside is selected, no matter 'sim-select' value. - U-Boot enables power in all three miniPCIe and M.2 slots before loading the kernel - this board supports 'dual image' feature (controlled by 'dual_image' U-Boot environment variable) - all three miniPCIe slots have additional 5 V supply on pins 47 and 49 - the board allows to install up to two oversized miniPCIe cards (vendor has dedicated MediaTek MT7615N/D cards for this board) - this board has additional logic circuit controlling PERSTn pins inside miniPCIe slots. By default, PERSTn (GPIO19) is routed to all miniPCIe slots but setting GPIO22 to high allows PERSTn control per slot, using GPIO23-25 (value is inverted) Flash instructions: You can use the 'sysupgrade' image directly in vendor firmware which is based on OpenWrt (make sure to not preserve settings - use 'sysupgrade -n -F ...' command). Alternatively, use web recovery mode in U-Boot: 1. Power the device with reset button pressed, the modem LED will start blinking slowly and after ~3 seconds, when it starts blinking faster, you can release the button. 2. Setup static IP 192.168.1.2/24 on your PC. 3. Go to 192.168.1.1 in browser and upload 'sysupgrade' image. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> (backported from commit e68539aca43a560077364de27eb220f1d85ca3ef)
* ramips: add support for ALFA Network R36M-E4GPiotr Dymacz2019-11-246-4/+238
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ALFA Network R36M-E4G is a dual-SIM, N300 Wi-Fi, compact size platform based on MediaTek MT7620A WiSoC. This product is designed for operation with 4G modem (can be bought in bundle with Quectel EC25, EG25 or EP06) but supports also Wi-Fi modules (miniPCIe slot has USB and PCIe buses). Specification: - MT7620A (580 MHz) - 64/128/256 MB of RAM (DDR2) - 16/32+ MB of FLASH (SPI NOR) - 2x 10/100 Mbps Ethernet, with passive PoE support (24 V) - 2T2R 2.4 GHz (MT7620A), with ext. LNA (RFFM4227) - 1x miniPCIe slot (with PCIe and USB 2.0 buses and optional 5 V) - 2x SIM slot (mini, micro) with detect and switch driven by GPIO - 2x u.fl antenna connectors (for Wi-Fi) - 8x LED (7 driven by GPIO) - 2x button (reset, wifi) - 2x UART (4-pin/2.54 mm pitch, 10-pin/1.27 mm pitch) headers on PCB - 1x I2C (4-pin, 1.27 mm pitch) header on PCB - 1x LED (8-pin, 1.27 mm pitch) header on PCB - 1x DC jack with lock (12 V) Other: - there is a dedicated, 4-pin connector for optional RTC module (Holtek HT138x) with 'enable' input, not available at the time of preparing support for this board - miniPCIe slot supports additional 5 V supply on pins 47 and 49 but a jumper resistor (R174) is not installed by default - U-Boot selects default SIM slot, based on value of 'default_sim' env variable: '1' or unset -> SIM1 (mini), '2' -> SIM2 (micro). This will work only if both slots are occupied, otherwise U-Boot will always select slot with SIM card inside (user can override it later, in user-space) - U-Boot resets the modem, using PERSTn signal, before starting kernel - this board supports 'dual image' feature (controlled by 'dual_image' U-Boot environment variable) Flash instruction: You can use the 'sysupgrade' image directly in vendor firmware which is based on OpenWrt (make sure to not preserve settings - use 'sysupgrade -n -F ...' command). Alternatively, use web recovery mode in U-Boot: 1. Power the device with reset button pressed, the modem LED will start blinking slowly and after ~3 seconds, when it starts blinking faster, you can release the button. 2. Setup static IP 192.168.1.2/24 on your PC. 3. Go to 192.168.1.1 in browser and upload 'sysupgrade' image. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> (backported from commit dfecf94c2059998411f95067de3866aa7cdf5ec9)
* ramips: support dual image feature on ALFA Network boardsPiotr Dymacz2019-11-242-3/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | New U-Boot version for MediaTek MT76x8/MT762x based ALFA Network boards includes support for a 'dual image' feature. Users can enable it using U-Boot environment variable 'dual_image' ('1' -> enabled). When 'dual image' feature is enabled, U-Boot will modify DTB and divide the original 'firmware' flash area into two, equal in size and aligned to 64 KB partitions: 'firmware' and 'backup'. U-Boot will also adjust size of 'firmware' area to match installed flash chip size. U-Boot will load kernel from active partition which is marked with env variable 'bootactive' ('1' -> first partition, '2' -> second partition) and rename both partitions accordingly ('firmware' <-> 'backup'). There are 3 additional env variables used to control 'dual image' mode: - bootlimit - maximum number of unsuccessful boot tries (default: '3') - bootcount - current number of boot tries - bootchanged - flag which informs that active partition was changed; if it is set and 'bootcount' reaches 'bootlimit' value, U-Boot will start web-based recovery which then updates both partitions with provided image Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> (backported from commit bc173ddd8381b03dde8cc2e6c66d0cd392c62bbd)
* ramips: refresh all subtargets kernel configsPiotr Dymacz2019-11-246-5/+40
| | | | Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ramips: use upstream RAW_APPENDED_DTB instead of our OWRTDTBChuanhong Guo2019-11-249-86/+15
| | | | | | | | | | | | | | | | | | | Upstream kernel added support for RAW_APPENDED_DTB on ralink arch in the following commit: 02564fc89d3d ("ralink: Introduce fw_passed_dtb to arch/mips/ralink") Use upstream solution and get rid of our OWRTDTB hack. This commit set DEVICE_DTS to $$(DTS) instead of replacing DTS with DEVICE_DTS in device profile because DTS variable will be dropped in later commits. Signed-off-by: Chuanhong Guo <gch981213@gmail.com> [Tested on mt7621/mt76x8] Tested-by: Chuanhong Guo <gch981213@gmail.com> [Tested on rt305x/mt7620] Tested-by: INAGAKI Hiroshi <musashino.open@gmail.com> (cherry picked from commit 7a8d3432c739c6ff038295176e8b6324e92fc116) Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ramips: set uImage name of WeVO 11AC NAS and W2914NS v2Sungbo Eo2019-11-211-0/+2
| | | | | | | | | | | | | | | | The stock firmware and bootloader only accept uImage with names that match certain patterns. This patch enables OpenWrt installation from stock firmware without having to reflash the bootloader or 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: Sungbo Eo <mans0n@gorani.run> (cherry picked from commit 19800ac095f6ddbba03ccab08e5197b1eec4a49e) [backported] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: bump 4.14 to 4.14.154Koen Vandeputte2019-11-191-11/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | Refreshed all patches. Altered patches: - 902-debloat_proc.patch - 040-dmaengine-qcom-bam-Process-multiple-pending-descript.patch - 807-usb-support-layerscape.patch - 809-flexcan-support-layerscape.patch - 816-pcie-support-layerscape.patch Remove upstreamed: - 303-spi-nor-enable-4B-opcodes-for-mx66l51235l.patch New symbols: X86_INTEL_MPX X86_INTEL_MEMORY_PROTECTION_KEYS CONFIG_X86_INTEL_TSX_MODE_OFF X86_INTEL_TSX_MODE_ON X86_INTEL_TSX_MODE_AUTO SGL_ALLOC Compile-tested on: ar71xx, cns3xxx, imx6, x86_64 Runtime-tested on: ar71xx, cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ramips: assign correct key-code to wps buttonsChristian Lamparter2019-11-172-2/+2
| | | | | | | | | | | | The two ASUS WL-330N and WL-330N3G had the reset keycode assigned to the WPS button. This patch changes all three devices to use KEY_WPS_BUTTON in the hopes that this fixes unwanted restarts/ unexpected behavior from the users point of view. [dropped RG21S] Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (cherry picked from commit ad65d9d7b264d6d17293c59469e770905d2f785a)