aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* ramips: use patch-dtb for F5D8235 V1Tobias Wolf2018-04-231-3/+1
| | | | | | | | | | The old DTB method (OWRTDTB) is not recognized by the boot process anymore with 4.9/4.14. This patch reuses KERNEL_DTB to get a valid DTB applied to the kernel image. Signed-off-by: Tobias Wolf <github-NTEO@vplace.de>
* kernel: fix usb interface on 3G dwm-158 modemGiuseppe Lippolis2018-04-231-0/+42
| | | | | | | | | | | | The current option driver binds to the usb interface 2,3,4,5. But the interface 4 and 5 doesn't answer to the AT commands. On the new openwrt configuration the wwan script select the 5th interface as control interface, failing to establish the 3G connection. Backport the fix for the problem. Signed-off-by: Giuseppe Lippolis <giu.lippolis@gmail.com>
* ipq40xx: add support for OpenMesh A62Sven Eckelmann2018-04-237-5/+276
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * QCA IPQ4019 * 256 MB of RAM * 32 MB of SPI NOR flash (s25fl256s1) - 2x 15 MB available; but one of the 15 MB regions is the recovery image * 2T2R 2.4 GHz - QCA4019 hw1.0 (SoC) - requires special BDF in QCA4019/hw1.0/board-2.bin with bus=ahb,bmi-chip-id=0,bmi-board-id=20,variant=OM-A62 * 2T2R 5 GHz (channel 36-64) - QCA9888 hw2.0 (PCI) - requires special BDF in QCA9888/hw2.0/board-2.bin bus=pci,bmi-chip-id=0,bmi-board-id=16,variant=OM-A62 * 2T2R 5 GHz (channel 100-165) - QCA4019 hw1.0 (SoC) - requires special BDF in QCA4019/hw1.0/board-2.bin with bus=ahb,bmi-chip-id=0,bmi-board-id=21,variant=OM-A62 * multi-color LED (controlled via red/green/blue GPIOs) * 1x button (reset; kmod-input-gpio-keys compatible) * external watchdog - triggered GPIO * 1x USB (xHCI) * TTL pins are on board (arrow points to VCC, then follows: GND, TX, RX) * 2x gigabit ethernet - phy@mdio3: + Label: Ethernet 1 + gmac0 (ethaddr) in original firmware + 802.3at POE+ - phy@mdio4: + Label: Ethernet 2 + gmac1 (eth1addr) in original firmware + 18-24V passive POE (mode B) * powered only via POE The tool ap51-flash (https://github.com/ap51-flash/ap51-flash) should be used to transfer the factory image to the u-boot when the device boots up. The initramfs image can be started using setenv bootargs 'loglevel=8 earlycon=msm_serial_dm,0x78af000 console=ttyMSM0,115200 mtdparts=spi0.0:256k(0:SBL1),128k(0:MIBIB),384k(0:QSEE),64k(0:CDT),64k(0:DDRPARAMS),64k(0:APPSBLENV),512k(0:APPSBL),64k(0:ART),64k(0:custom),64k(0:KEYS),15552k(inactive),15552k(inactive2)' tftpboot 0x84000000 openwrt-ipq40xx-openmesh_a62-initramfs-fit-uImage.itb set fdt_high 0x85000000 bootm 0x84000000 Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
* ipq40xx: fix gpio-hog related boot issuesSven Eckelmann2018-04-236-6/+109
| | | | | | | | | | | | | | | The pinctrl initialization fails with the MSM pinctrl code and gpio-hogs because either the gpio ranges are not yet initialized (missing gpio-range in DT) or that the msm driver unconditionally tries to re-initializes the ranges (gpio-range in DT). To allow gpio-hogs and similar early-boot gpio code, the gpio-ranges must be in the device tree and the pinctrl-msm code must check whether the range was already initialized by the DT. Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com> [drop changes to unrelated dtsi files, refresh patches] Signed-off-by: Mathias Kresin <dev@kresin.me>
* ipq40xx: use upstream board-2.binSven Eckelmann2018-04-235-10/+11
| | | | | | | The BDFs for all boards were upstreamed to the ath10k-firmware repository and are now part of ath10k-firmware 2018-04-19. Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
* brcm47xx: backport upstream patches for Netgear WNR1000 V3Rafał Miłecki2018-04-2317-137/+383
| | | | | | This includes fix for reading NVRAM content. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ipq40xx: ex61x0v2: Disable unused GMACsThomas Hebb2018-04-201-0/+1
| | | | | | | These devices have only one ethernet port. It doesn't make sense to expose the unused GMACs as separate network devices. Signed-off-by: Thomas Hebb <tommyhebb@gmail.com>
* ipq40xx: Move reserved-memory DT to qcom-ipq4019.dtsiSven Eckelmann2018-04-2010-145/+89
| | | | | | | | The tz and smem reserved-memory information handled in the upstream Linux sources by the SoC specific dtsi and not by the the boards dts. Using the same approach in OpenWrt avoids unneccessary duplication. Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
* ipq40xx: Remove unused reserved-memory nodesSven Eckelmann2018-04-207-76/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The reserved-memory regions are mostly undocumented by QCA and are named very unspecific in the QSDK device trees. It was tried to clean them up by commit 71ed9f10a33e ("ipq40xx: Use detailed reserved memory for A42") and similar changes. The features which require these regions were mostly unknown but Senthilkumar N L <snlakshm@qti.qualcomm.com> and Sricharan Ramabadhran <srichara@qti.qualcomm.com> provided some more insight in some of them: * crash dump feature - a couple of regions used when 'qca,scm_restart_reason' dt node has the value 'dload_status' not set to 1 + apps_bl <0x87000000 0x400000> + sbl <0x87400000 0x100000> + cnss_debug <0x87400000 0x100000> + cpu_context_dump <0x87b00000 0x080000> - required driver not available in Linux - safe to remove * QSEE app execution - region tz_apps <0x87b80000 0x280000> - required driver not available in Linux - safe to remove * communication with TZ/QSEE - region smem <0x87b80000 0x280000> - driver changes not yet upstreamed - must not be removed because any access can crash kernel/program * trustzone (QSEE) private memory - region tz <0x87e80000 0x180000> - must not be removed because any access can crash kernel/program Removing the unnecessary regions saves some kilobyte of reserved-memory and cleans up the device tree: * 2560 KiB - 8devices Jalapeno - AVM FRITZ!Box 4040 - Compex WPJ428 - Meraki MR33 Access Point - OpenMesh A42 * 14336 KiB - GL.iNet GL-B1300 - Qualcomm Technologies, Inc. IPQ40xx/AP-DK01.1-C1 Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
* build: consolidate fake uImage header build commandsMathias Kresin2018-04-206-21/+11
| | | | | | | | | | | Merge the two existing functions and use a parameter for the type header field. It updates the syntax of the former mpc85xx fake ramdisk header command to be compatible with mkimage from u-boot 2018.03 and fixes the build error spotted by the build bot. Signed-off-by: Mathias Kresin <dev@kresin.me>
* mediatek: disable ubifsFelix Fietkau2018-04-201-1/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mediatek: remove 4.9 kernel configFelix Fietkau2018-04-201-472/+0
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* orion: remove linux 4.4 supportFelix Fietkau2018-04-196-954/+0
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* omap: remove linux 4.4 supportFelix Fietkau2018-04-192-730/+0
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: drop linux 4.4 and 4.9 supportFelix Fietkau2018-04-19147-26085/+0
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: fix an issue with infinite stack traces on MIPSFelix Fietkau2018-04-181-0/+57
| | | | | | Reproduced by enabling lockdep on MT7621 Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mediatek: enable ramdisk support by defaultFelix Fietkau2018-04-171-1/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mediatek: fix target FPU settingsFelix Fietkau2018-04-173-2/+3
| | | | | | | | | | This reverts commit 5555545494c876adedf4f0038db49c1d85527e78. The target supports both NEON and VFPv4, but for this to work properly, a few more changes are needed: - enable NEON support in the kernel config - add the fpu feature flag to the makefile Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ramips: fix locking issues in the ethernet driverFelix Fietkau2018-04-171-2/+3
| | | | | | | The stats update needs to protect against being interrupted by a tasklet The u64 stats seqlock needs to be initialized Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ramips: mt7620: fix double use of pinsMathias Kresin2018-04-173-6/+0
| | | | | | | | | The pins are used as (LED) GPIOs and can't be used at the same time as hardware controlled ephy (LED) pins. Fixes: FS#1500 Signed-off-by: Mathias Kresin <dev@kresin.me>
* kernel: bump 4.14 to 4.14.34Stijn Tintel2018-04-1620-82/+84
| | | | | | | | | | | | | Refresh patches. Update patches that no longer apply: - backport/313-netfilter-remove-defensive-check-on-malformed-packet.patch - pending/642-net-8021q-support-hardware-flow-table-offload.patch Compile-tested: x86/64. Runtime-tested: x86/64. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* ramips: remove broken and bogus spinlock in the SPI driverFelix Fietkau2018-04-141-4/+1
| | | | | | Based on patch by Neil Brown Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ramips: add missing unlock in fe_phy_link_adjustFelix Fietkau2018-04-141-0/+1
| | | | | | Based on patch by Neil Brown Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ramips: fix usb phy compatible string (should fix FS#1489)Felix Fietkau2018-04-131-1/+1
| | | | | | | In the new USB phy driver, it checks the compatible string before attempting to iomap its mem resource and do the extra PHY init Signed-off-by: Felix Fietkau <nbd@nbd.name>
* apm821xx: Force Ethernet PHYID on MX60/MX60WChristian Lamparter2018-04-131-1/+1
| | | | | | | | | | The MX60's uboot disables all the PHYs before starting linux. This causes the PHY/switch detection code to malfunction almost all of the time. To get around this, set a compatible flag to force PHYID. Signed-off-by: Christian Lamparter <chunkeey@gmail.com> Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
* ipq40xx: unbundle firmware and board fileMathias Kresin2018-04-132-5/+5
| | | | | | | | | | | Don't select the firmware with the board file, it prevents an easy use of the -ct ath10k firmware. Select the firmware within the default packages instead. Remove the per device selection of the firmware now that it the firmware is selected by default. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ipq40xx: add support for Netgear EX6100v2/EX6150v2David Bauer2018-04-139-3/+446
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Specifications: SOC: Qualcomm IPQ4018 (DAKOTA) ARM Quad-Core RAM: 256 MB Winbond W632GU6KB12J FLASH: 16 MiB Macronix MX25L12805D ETH: Qualcomm QCA8072 WLAN1: Qualcomm Atheros QCA4018 2.4GHz 802.11b/g/n/ac 2x2 WLAN2: Qualcomm Atheros QCA4018 5GHz 802.11n/ac 1x1 (EX6100) 2x2 (EX6150) INPUT: Power, WPS, reset button AP / Range-extender toggle LED: Power, Router, Extender (dual), WPS, Left-/Right-arrow SERIAL: Header next to QCA8072 chip. VCC, TX, RX, GND (Square hole is VCC) WARNING: The serial port needs a TTL/RS-232 v3.3 level converter! The Serial setting is 115200-8-N-1. Tested and working: - Ethernet - 2.4 GHz WiFi (Correct MAC-address) - 5 GHz WiFi (Correct MAC-address) - Factory installation from WebIF - Factory installation from tftp - OpenWRT sysupgrade (Preserving and non-preserving) - LEDs - Buttons Not Working: - AP/Extender toggle-switch Untested: - Support on EX6100v2. They share the same GPL-Code and vendor-images. The 6100v2 seems to lack one 5GHz stream and differs in the 5GHz board-blob. I only own a EX6150v2, therefore i am only able to verify functionality on this device. Install via Web-Interface: Upload the factory image to the device to the Netgear Web-Interface. The device might asks you to confirm the update a second time due to detecting the OpenWRT firmware as older. The device will automatically reboot after the image is written to flash. Install via TFTP: Connect to the devices serial. Hit Enter-Key in bootloader to stop autobooting. Command "fw_recovery" will start a tftp server, waiting for a DNI image to be pushed. Assign your computer the IP-address 192.168.1.10/24. Push image with tftp -4 -v -m binary 192.168.1.1 -c put <OPENWRT_FACTORY> Device will erase factory-partition first, then writes the pushed image to flash and reboots. Parts of this commit are based on Thomas Hebb's work on the openwrt-devel mailinglist. See https://lists.openwrt.org/pipermail/openwrt-devel/2018-January/043418.html Signed-off-by: David Bauer <mail@david-bauer.net>
* ipq-wifi: Add 8devices JalapenoRobert Marko2018-04-131-1/+1
| | | | | | | Add custom board-2.bin for 8devices Jalapeno. Upstreaming is in progress. Signed-off-by: Robert Marko <robimarko@gmail.com>
* ipq40xx: add support for 8devices JalapenoRobert Marko2018-04-136-9/+317
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for 8devices Jalapeno. Specification: QCA IPQ4018, Quad core ARM v7 Cortex A7 717MHz 256 MB of DDR3 RAM 8 MB of SPI NOR flash 128 MB of Winbond SPI NAND flash WLAN1: Qualcomm Atheros QCA4018 2.4GHz 802.11bgn 2:2x2 requires special BDF in QCA4019/hw1.0/board-2.bin with: bus=ahb,bmi-chip-id=0,bmi-board-id=16,variant=8devices-Jalapeno WLAN2: Qualcomm Atheros QCA4018 5GHz 802.11a/n/ac 2:2x2 requires special BDF in QCA4019/hw1.0/board-2.bin with: bus=ahb,bmi-chip-id=0,bmi-board-id=17,variant=8devices-Jalapeno ETH: Qualcomm Atheros QCA8072 Gigabit Switch (1 x LAN, 1 x WAN) phy@mdio3: Label: eth0 gmac0 phy@mdio4: Label: eth1 gmac1 Installation instructions: Since boards ship with old version of LEDE installation is simple. Just use sysupgrade -n -F sysupgrade.bin Syuspgrade needs to be forced since OpenWRT uses DT detection in recent releases. If you get error that FIT configuration is not found during boot it is due to older U-boot used on your board. That is because 8devices used custom FIT configuration partition name as they internally had v1 and v2 boards. Only v2 boards are sold so now they are shipping boards with never U-boot using generic config@1 FIT partition name. Also for old uboot it is possible to force loading config@1 by changing uboot environment: setenv boot5 'bootm 0x84000000#config@1’ saveenv Signed-off-by: Robert Marko <robimarko@gmail.com>
* kernel: mtd: bcm47xxpart: improve handling TRX partition sizeRafał Miłecki2018-04-125-2/+197
| | | | | | | | | | | | | | This is important fix for flash parsing in some corner cases. In case of TRX subpartition with rootfs being aligned to the flash block size it was incorrectly registered twice. Detecting & registering it as a standalone partition was resulting in an incorrect "firmware" partition size and possibly broken sysupgrade. It wasn't noticed before because "rootfs" alignment depends on a kernel size. It can happen though - depending on the configuration and the kernel size. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* omap: kernel update and switch to 4.14Lucian Cristian2018-04-112-1/+737
| | | | Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* ar71xx: increase kernel partition size for CPE/WBS 210/510Matthias Schiffer2018-04-101-1/+1
| | | | Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ar71xx: sysupgrade: improve CPE/WBS 210/510 validation, add new metadata offsetMatthias Schiffer2018-04-101-12/+20
| | | | | | | | | Previously, tplink_pharos_check_image() would accept any image with ELF magic and only non-printable data in the support-list, as in this case the while-read loop would not run at all. Add the new support-list offset and ensure an image is only accepted when the model string is actually found. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ar71xx: increase kernel partition size for UniFi AP Pro and Outdoor+, enable ↵Matthias Schiffer2018-04-101-2/+4
| | | | | | | | devices again Tested on UAP Outdoor+. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ar71xx: limit Ethernet speed of UBNT Airmax M (XM) devices to 100Mbit/sMatthias Schiffer2018-04-101-0/+2
| | | | | | | | | Some Airmax devices can establish a Gigabit link even though the MAC only supports 10/100 MBit/s, leading to broken connectivity. Prevent this from happening by limiting the speed to 100MBit/s. Fixes: FS#296 Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ipq806x: replace linux,part-probe with a proper partitions subnodeRafał Miłecki2018-04-094-5/+20
| | | | | | | | | | | This solution is more upstream compatible as it only requires specifying of_match_table in the parser code and doesn't depend on linux,part-probe which is solution made generic by a LEDE downstream patch that can't be upstreamed. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> Acked-by: John Crispin <john@phrozen.org>
* kernel: use accepted mtd patchset adding support for "compatible" stringRafał Miłecki2018-04-096-18/+50
| | | | | | | These patches were finally accepted and are already present in the Linus's tree. This should be good enough to make is "backport" material. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ramips: rename pwm kernel moduleMathias Kresin2018-04-081-5/+5
| | | | | | | | | | | | | | With kernel 4.14 the OpenWrt specific module name collides with the upstream added module for Mediatek ARM Socs. During addition of preliminary support for kernel 4.14, the config symbol used by the out of tree driver was already renamed but the ramips kernel package wasn't updated. Fix the build error by updating the config and kernel module name for the kernel package. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: add support for Zorlik ZL5900V2Vianney le Clément de Saint-Marcq2018-04-086-1/+109
| | | | | | | | | | | | | | | | | | | | | | | | The Zorlik ZL5900V2 is an unbranded clone of HAME MPR-A1/2. It is marketed as "3G Wi-Fi Router". Only the PCB has the model name "ZL5900V2" printed on it. Specifications: - Ralink RT5350F (360 MHz) - 32 MB RAM - 8 MB Flash - 802.11bgn 1T1R - 1x 10/100 Mbps Ethernet - 1x USB 2.0 (Type-A) - 5200 mAh battery The ramdisk image (not the squashfs sysupgrade image) can be flashed through the web interface (named "GoAhead") of the factory firmware. However, as the factory firmware does not cleanly unmount the rootfs before flashing, the device may hang instead of rebooting after successful write. Power cycling the device gets you in OpenWrt where the squashfs image may be flashed through normal sysupgrade procedure. Signed-off-by: Vianney le Clément de Saint-Marcq <code@quartic.eu>
* ramips: add support for the YouHua WR1200JSZheng Qian2018-04-086-1/+157
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | YouHua tech WR1200JS is an AC1200 router with 5 1Gb ports (4 Lan, 1 Wan) and 1 USB 2.0 port. Devices is base on MediaTek MT7621AT + MT7603E + MT7612E. Specification: - MT7612AT (880 MHz) - 128 MB of RAM - 16 MB of FLASH (SPI NOR) - 5x 10/100/1000 Mbps Ethernet - 2T2R 2.4 GHz (MT7603E) - 2T2R 5 GHz (MT7612E) - 1x USB 2.0 - 10x LED (Power 2G 5G WPS Internet LAN4-1 USB) - 3x button (reset wifi wps) - DC jack for main power input (12V) Installation: 1.) Press reset key 5 sec and restore the factory default 2.) Login webUI and change username to root and set a new password 3.) Visit http://192.168.2.254/adm/telnetd.shtml and turn on the telnet service 4.) Copy openwrt-ramips-mt7621-youhua_wr1200js-initramfs-kernel.bin to a usb pan 5.) Plug the usb pan to the router, telnet to the router and login by root 6.) cd /media/sda1 and check the initramfs file is there 7.) exec command: mtd_write write openwrt-ramips-mt7621-youhua_wr1200js-initramfs-kernel.bin Kernel 8.) reboot and visit 192.168.1.1 Signed-off-by: Zheng Qian <sotux82@gmail.com>
* ramips: add dwr-512 jboot firmware configurationGiuseppe Lippolis2018-04-085-15/+19
| | | | | | | | | | | | | | | | | | | | | The previous fw version require the replacement of the stock bootloader with u-boot. This prevent an easy stock restore of the original fw. Now a proper fw util has been developed to manage the stock jboot bootloader. Therefore make sense have a fw image for the stock bootloader. The old fw configuration (u-boot) is not compatible with the new one and will not be supported anymore. So at the end 2 image can be generated: 1) factory image with jboot bootloader openwrt-ramips-rt305x-dwr-512-b-squashfs-factory.bin 2) sysupgrade image with jboot bootloader openwrt-ramips-rt305x-dwr-512-b-squashfs-sysupgrade.bin Signed-off-by: Giuseppe Lippolis <giu.lippolis@gmail.com>
* ar8216: reduce latency even further for ar8327 chipsFelix Fietkau2018-04-081-2/+4
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ar8216: reduce latency by inserting scheduling points into code hogging the CPUFelix Fietkau2018-04-081-2/+7
| | | | | | Should reduce network related latency caused by accessing MIB counters Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ramips: fix usbphy DT nodes on linux 4.14Vianney le Clément de Saint-Marcq2018-04-077-25/+34
| | | | | | | | | | | | | | The Ralink USB PHY driver merged into mainline has a slightly different device tree binding than the patch that was used with linux 4.9. The new driver requires a `ralink,sysctl` node pointing to the `syscon` node. This patch also sets `#phy-cells` to 0, as recommended by the mainline documentation [1]. [1] Documentation/devicetree/bindings/phy/ralink-usb-phy.txt Signed-off-by: Vianney le Clément de Saint-Marcq <code@quartic.eu>
* ar71xx: add support for TP-Link Archer C60 v2Henryk Heisig2018-04-0714-4/+119
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 (web): Download lede-ar71xx-generic-archer-c60-v2-squashfs-factory.bin and use OEM System Tools - Firmware Upgrade site. Flash instruction (recovery): 1. Set PC to fixed IP address 192.168.0.66 2. Download lede-ar71xx-generic-archer-c60-v2-squashfs-factory.bin 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 lede-ar71xx-...-sysupgrade.bin erase 0x9f030000 +$filesize cp.b $fileaddr 0x9f030000 $filesize reset Signed-off-by: Henryk Heisig <hyniu@o2.pl>
* ar71xx: add support for TP-Link TL-WR940N v6Robert Marko2018-04-068-17/+72
| | | | | | | | | Add support for TL-WR940N v6 board. It is pretty much the same as v5 except they only left WAN LED and removed other ones. Installation: flash factory image through WEB UI or use TFTP. Signed-off-by: Robert Marko <robimarko@gmail.com>
* ar71xx: drop kernel 4.4 supportPiotr Dymacz2018-04-0697-8147/+0
| | | | Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ar71xx: change brand name WHQX to QxwlanPeng Zhang2018-04-065-16/+16
| | | | Signed-off-by: Peng Zhang <sd20@qxwlan.com>
* ar71xx: rework chipidea controller support, add QCA9531Piotr Dymacz2018-04-061-39/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | Rework (again) platform support for dual-role chipidea USB controller: - include support for QCA9531 - use correct EHCI block size - drop ar933x_usb_setup_ctrl_config() function - simplify code after previous "register chipidea only in device mode" change (fa22714181) Reworked patch was tested on devices with below QCA WiSOCs (signal/GPIO name with required bootstrap state for USB bus 0 in device mode): - AR9331 (GPIO13 pull-down) - AR9342 (RGMII_TXD1/ETXD1 pull-up) - AR9344 (GPIO20 pull-up) - QCA9531 (GPIO13 pull-up) - QCA9558 (GPIO13 pull-up) The only way to select device mode for bus 0 is to change SOC bootstrap configuration which is sampled only once, at hard reset. Likely, other models, like QCA9556 or AR9341, should also support dual-role USB mode but they were not tested. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ramips: add U-Boot env support for ALFA Network AC1200RMPiotr Dymacz2018-04-062-2/+7
| | | | Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-28 04:14:53 +0000