aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* lantiq: fix phys ledAleksander Jan Bajkowski2019-12-231-2/+2
| | | | | | | | | led2l and led2h value is incorrectly set by led3l and led3h. Bug was introduced in commit: 863e79f8d5544a8a884375d7e867f350fddca9b9 Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl> Fixes: 863e79f8d554 ("lantiq: add support for kernel 4.9") (cherry picked from commit 692390225d76de8f2daf582454e74942b82d090a)
* ar71xx: fix MAC address setup for TL-WDR4300 boardSungbo Eo2019-12-212-1/+5
| | | | | | | | | | | | | | | | | | The current ethernet MAC address setup of TL-WDR4300 board is different from the setup of stock firmware: OpenWrt: lan = label_mac -2, wan = label_mac -2 stock: lan = label_mac, wan = label_mac +1 This patch applies to all devices using TL-WDR4300 board: TL-WDR3600 v1 TL-WDR4300 v1 TL-WDR4300 v1 (IL) TL-WDR4310 v1 Mercury MW4530R v1 Signed-off-by: Sungbo Eo <mans0n@gorani.run> (cherry picked from commit 9b02d32e34df2bb8821ec6f08f525bee22d0d1ba)
* ath79: fix MAC address setup for TP-Link TL-WDR3600/TL-WDR4300Sungbo Eo2019-12-212-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | The current ethernet MAC address setup of TL-WDR4300 board is different from the setup of stock firmware: OpenWrt: lan = label_mac -2, wan = label_mac -2 stock: lan = label_mac, wan = label_mac +1 The full address assignment is as follows: LAN label WAN label + 1 5G label 2G label - 1 This patch changes all devices using TL-WDR4300 board: TL-WDR3600 v1 (checked on device) TL-WDR4300 v1 (checked on device) TL-WDR4300 v1 (IL) Signed-off-by: Sungbo Eo <mans0n@gorani.run> [rephrase/extend commit title/message, backport] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit a4260eaab7744c8e3f1f7a62a61aab5e3b562342)
* 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)
* ath79: migrate LED paths of TL-WDR4300 boardSungbo Eo2019-12-171-1/+4
| | | | | | | | | | | | | | TL-WDR4300 board uses only green LED names in DTSI. This patch adds migration for them. The actual LED colors on the devices have been reported to vary across subrevisions (v1.x). Despite, the USB LEDs on the back might have different color than the other LEDs on the front. Signed-off-by: Sungbo Eo <mans0n@gorani.run> [extended commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 01d39cd18c4035e362f179548cd2c051aac03042)
* malta: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-171-2/+0
| | | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit e964338110526b3692847769343816cd2f853d18)
* sunxi: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-171-2/+0
| | | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit 2105354968ed9698709d220ec446b6d9c27da3a5)
* layerscape: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-172-4/+0
| | | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit 414d027ae8ac05ec9aa06bc50afd5458c2da02fc)
* kirkwood: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-171-2/+0
| | | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit 411e824ec371a322b975e90af5a1f32760a61720)
* at91: disable legacy PTYs and virtual terminalsDaniel Golle2019-12-171-6/+0
| | | | | | | | | | Enabling legacy PTYs causes problems with procd-hotplug. And as this is a headless target, no need to have virtual terminals. Remove corresponding kernel config options, they are disabled in generic kernel config. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit c1db4d9c5655e3c74ffdbb6a6a3367269f65c55f)
* mpc85xx: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-171-2/+0
| | | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit d0d7f5d9e49b8632f372c92e0339895fa10904f9)
* uml: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-172-4/+0
| | | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit dcf48fda054c4bbc52f6106250a7e06ab8f5cbdd)
* oxnas: disable legacy PTYs and virtual terminalsDaniel Golle2019-12-171-6/+0
| | | | | | | | | | Enabling legacy PTYs causes problems with procd-hotplug. And as this is a headless target, no need to have virtual terminals. Remove corresponding kernel config options, they are disabled in generic kernel config. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit c881769a558b38ddd5977a50b67cd32c6d3f7d5e)
* lantiq: remove redundant WiFi LED on FRITZ!Box 7320Manuel Kock2019-12-141-3/+0
| | | | | | | | | | The led wireless trigger is already set correctly to phy0tpt through the alias in the device tree. Signed-off-by: Manuel Kock <github.web@manu.li> [rephrased commit title] Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 509894cffb7ec24ac21a381bed3c035efce42aeb)
* mpc85xx: add support for Enterasys WS-AP3710iDavid Bauer2019-12-147-0/+310
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware -------- SoC: NXP P1020 (2x e500 @ 800MHz) RAM: 256M DDR3 (Micron) FLASH: 32M NOR (Spansion S29GL128S) BTN: 1x Reset WiFi: 1x Atheros AR9590 2.4 bgn 3x3 2x Atheros AR9590 5.0 an 3x3 ETH: 1x Gigabit Ethernet (Atheros AR8033) LED: System (green/red) - Radio{0,1} (green) LAN (connected to PHY) - GE blue - FE green Serial is a Cisco-compatible RJ45 next to the ethernet port. 115200-N-8 are the settings for OS and U-Boot. Installation ------------ 1. Grab the OpenWrt initramfs, rename it to 01C8A8C0.img. Place it in the root directory of a TFTP server and serve it at 192.168.200.200/24. 2. Connect to the serial port and boot the AP. Stop autoboot in U-Boot by pressing Enter when prompted. Credentials are identical to the one in the APs interface. By default it is admin / new2day. 3. Set the bootcmd so the AP can boot OpenWrt by executing $ setenv boot_openwrt "setenv bootargs; cp.b 0xee000000 0x1000000 0x1000000; bootm 0x1000000" $ setenv bootcmd "run boot_openwrt" $ saveenv If you plan on going back to the vendor firmware - the bootcmd for it is stored in the boot_flash variable. 4. Load the initramfs image to RAM and boot by executing $ tftpboot 0x1000000 192.168.200.200:01C8A8C0.img; bootm 5. Make a backup of the "firmware" partition if you ever wish to go back to the vendor firmware. 6. Upload the OpenWrt sysupgrade image via SCP to the devices /tmp folder. 7. Flash OpenWrt using sysupgrade. $ sysupgrade -n /tmp/openwrt-sysupgrade.bin Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 16b01fb1b9c99513c318109bef96a1a3545c57a0)
* ath79: add support for TP-Link TL-WDR4300 v1 (IL)Adrian Schmutzler2019-12-134-0/+21
| | | | | | | | | The TL-WDR4300 v1 sold in Israel has a different TPLINK_HWID. Thanks to Josh4300 for testing on device. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit c642a97aa6b51352a718449cd715b92f94af4a5d)
* 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)
* brcm47xx: add switch configuration for WNR3500LOlli Asikainen2019-12-111-1/+2
| | | | | | | | | | | | | | | | | | | | | Netgear WNR3500L is an already supported device, but out of the box, the device has no switch configuration and there is no wan. The correct configuration for this specific model is similar to some other models. This simple commit adds the correct switch and the out-of-the-box experience is improved. Experimentally determined: Port 0 => WAN Port 1..4 => LAN Port 5..7 => unused Port 8 => CPU Signed-off-by: Olli Asikainen <olli.asikainen@gmail.com> Tested-by: Fabian Zaremba <fabian@youremail.eu> [added port mapping to commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit deb835849aeb713968aaa48bf046101140ab4825)
* 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-1020-40/+40
| | | | | | | | | | | | 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>
* generic ar8xxx: increase VLAN table for AR83x7David Bauer2019-11-303-9/+13
| | | | | | | | | | | | | The Atheros AR8327 and AR8337 have (according to their datasheet) a VLAN table with a maximum of 4096 entries. Currently, there's a hard limit of 128 VLANs, which is the same as for most other Atheros switches. Increase this limit only for the AR83x7 series and modify some shared functions to allow them to work with a variable max VLAN count. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 3f79aaa2979793c054eae2c8b4058c8c7fccdbe7)
* 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>
* ar71xx: disable TP-Link TL-WA855RE by defaultJo-Philipp Wich2019-11-301-0/+1
| | | | | | | | Disable the TP-Link TL-WA855RE 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>
* brcm47xx: disable Linksys E1000 v1 by defaultJo-Philipp Wich2019-11-301-0/+1
| | | | | | | | Disable the Linksys E1000 v1 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-WA750RE by defaultJo-Philipp Wich2019-11-301-0/+1
| | | | | | | | Disable the TP-Link TL-WA750RE 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/30 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ar71xx: disable TP-Link TL-WA850RE by defaultJo-Philipp Wich2019-11-301-0/+1
| | | | | | | | Disable the TP-Link TL-WA850RE 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/30 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>
* ar71xx: disable Netgear WNR2000v4 by defaultJo-Philipp Wich2019-11-291-0/+1
| | | | | | | | Disable the Netgear WNR2000v4 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/11 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ar71xx: disable On Networks N150R by defaultJo-Philipp Wich2019-11-291-0/+1
| | | | | | | | Disable the On Networks N150R 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/10 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ar71xx: disable TP-Link TL-WA850RE v2 by defaultJo-Philipp Wich2019-11-291-0/+1
| | | | | | | | Disable the TP-Link TL-WA850RE v2 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/9 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ar71xx: disable Netgear WNR612 v2 by defaultJo-Philipp Wich2019-11-291-0/+1
| | | | | | | | Disable the Netgear WNR612 v2 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/4 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-2925-65/+65
| | | | | | | | | Refreshed all patches. Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ath79: add support for YunCore XD4200 and A782Piotr Dymacz2019-11-266-1/+211
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | YunCore XD4200 ('XD4200_W6.0' marking on PCB) is Qualcomm/Atheros based (QCA9563, QCA9886, QCA8334) dual-band, Wave-2 AC1200 ceiling AP with PoE (802.3at) support. A782 model ('T750_V5.1' marking on PCB) is a smaller version of the XD4200, with similar specification but lower TX power. Specification: - QCA9563 (775 MHz) - 128 MB of RAM (DDR2) - 16 MB of FLASH (SPI NOR) - 2x 10/100/1000 Mbps Ethernet (QCA8334), with 802.3at PoE support (WAN) - Wi-Fi 2.4 GHz: - XD4200: 2T2R (QCA9563), with ext. PA (SKY65174-21) and LNA - A782: 2T2R (QCA9563), with ext. FEM (SKY85329-11) - Wi-Fi 5 GHz: - XD4200: 2T2R (QCA9886), with ext. FEM (SKY85728-11) - A782: 2T2R (QCA9886), with ext. FEM (SKY85735-11) - LEDs: - XD4200: 5x (2x driven by SOC, 1x driven by AC radio, 2x Ethernet) - A782: 3x (1x RGB, driven by SOC and radio, 2x Ethernet) - 1x button (reset) - 1x UART (4-pin, 2.54 mm pitch) header on PCB - 1x DC jack (12 V) Flash instructions: If your device comes with generic QSDK based firmware, you can login over telnet (login: root, empty password, default IP: 192.168.188.253), issue first (important!) 'fw_setenv' command and then perform regular upgrade, using 'sysupgrade -n -F ...' (you can use 'wget' to download image to the device, SSH server is not available): fw_setenv bootcmd "bootm 0x9f050000 || bootm 0x9fe80000" sysupgrade -n -F openwrt-...-yuncore_...-squashfs-sysupgrade.bin In case your device runs firmware with YunCore custom GUI, you can use U-Boot recovery mode: 1. Set a static IP 192.168.0.141/24 on PC and start TFTP server with 'tftp' image renamed to 'upgrade.bin' 2. Power the device with reset button pressed and release it after 5-7 seconds, recovery mode should start downloading image from server (unfortunately, there is no visible indication that recovery got enabled - in case of problems check TFTP server logs) Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> (backported from commit e5d4c0966736287c7ade29c5ccaf6f1ad841b7db)
* ath79: add support for YunCore TFTP image generationVincent Wiemann2019-11-262-0/+15
| | | | | | | | | | | | | | | | | | | YunCore QCA9k based devices released in 2019 require a custom TFTP image for U-Boot built-in recovery mode (triggered with reset button). Image has to be prepended with 'YUNCORE' keyword followed by U-Boot CLI commands which will be executed later. Images without the custom header will be ignored by U-Boot. To be able to support both the vendor firmware (QSDK) and OpenWrt flash layouts, used here commands change the 'bootcmd' before flashing image. This commit adds generic helper script for YunCore devices with 16 MB of flash and enables TFTP image generation for A770 model. Signed-off-by: Vincent Wiemann <vincent.wiemann@ironai.com> [pepe2k@gmail.com: commit description reworded, recipe renamed] Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> (cherry picked from commit 8016f648640e8f73f0dc4fc307fb6bebd12afb88)
* ath79: Add support for TP-Link Archer C60 v2Adrian Schmutzler2019-11-265-2/+78
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link Archer C60 v2 is a dual-band AC1350 router, based on Qualcomm/Atheros QCA9561 + QCA9886. Specification: - 775/650/258 MHz (CPU/DDR/AHB) - 64 MB of RAM (DDR2) - 8 MB of FLASH (SPI NOR) - 3T3R 2.4 GHz - 2T2R 5 GHz - 5x 10/100 Mbps Ethernet - 7x LED, 2x button - UART header on PCB Flash instruction (WebUI): Download *-factory.bin image and upload it via the firmwary upgrade function of the stock firmware WebUI. Flash instruction (TFTP): 1. Set PC to fixed IP address 192.168.0.66 2. Download *-factory.bin image and rename it to tp_recovery.bin 3. Start a tftp server with the file tp_recovery.bin in its root directory 4. Turn off the router 5. Press and hold reset button 6. Turn on router with the reset button pressed and wait ~15 seconds 7. Release the reset button and after a short time the firmware should be transferred from the tftp server 8. Wait ~30 second to complete recovery Flash instruction (under U-Boot, using UART): tftp 0x81000000 ...-sysupgrade.bin erase 0x9f030000 +$filesize cp.b $fileaddr 0x9f030000 $filesize reset Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 974d6958a7c6332438ab4cda98e72156c8d944ed)
* ath79: Add support for TP-Link Archer C60 v1Adrian Schmutzler2019-11-266-1/+183
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link Archer C60v1 is a dual-band AC1350 router, based on Qualcomm/Atheros QCA9561+QCA9886. Specification: - 775/650/258 MHz (CPU/DDR/AHB) - 64 MB of RAM (DDR2) - 8 MB of FLASH (SPI NOR) - 3T3R 2.4 GHz - 2T2R 5 GHz - 5x 10/100 Mbps Ethernet - 7x LED, 2x button - UART header on PCB Flash instruction (WebUI): Download *-factory.bin image and upload it via the firmwary upgrade function of the stock firmware WebUI. Flash instruction (TFTP): 1. Set PC to fixed ip address 192.168.0.66 2. Download *-factory.bin image and rename it to tp_recovery.bin 3. Start a tftp server with the file tp_recovery.bin in its root directory 4. Turn off the router 5. Press and hold Reset button 6. Turn on router with the reset button pressed and wait ~15 seconds 7. Release the reset button and after a short time the firmware should be transferred from the tftp server 8. Wait ~30 second to complete recovery. Flash instruction under U-Boot, using UART: 1. tftp 0x81000000 ...-sysupgrade.bin 2. erase 0x9f020000 +$filesize 3. cp.b $fileaddr 0x9f020000 $filesize 4. reset Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 6d313da6dc5f655d92aa86e2ec42ecfcf763df3d)
* ar71xx: ubnt-(xm,xw): add rssileds packageLech Perczak2019-11-261-2/+8
| | | | | | | | | | | | | | | | | | | In order to make RSSI indicator on the device work out of box, include "rssileds" package in per-device rootfs image by default for Ubiquiti XM and XW devices, namely: - Bullet M (XM/XW) - Rocket M (XM/XW) - Nanostation M (XM/XW) - Nanostation Loco-M (XW) This moves the package addition to the individual devices in order to prevent accidental inclusions of the package when not looking at the parent node carefully enough. Signed-off-by: Lech Perczak <lech.perczak@gmail.com> [add bullet-m-xw, remove rocket-m-ti, extend commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 08d9c95417399ac8615df210f4381cca68a4b25c)
* ath79: add PoE passthrough switch for Ubiquiti Nanostation (XM/XW)Adrian Schmutzler2019-11-261-0/+6
| | | | | | | | | | | | | | This adds the gpio switch to enable PoE passthrough on Ubiquiti Nanostation (XM/XW). Values are copied from the implementation in ar71xx. GPIO values checked on: - NanoStation M5 XW - NanoStation M2 XM Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 317e98a5a2c6f1e2ac599ec530478669b965602c)
* 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>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-06 16:02:15 +0000