aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ar71xx
Commit message (Collapse)AuthorAgeFilesLines
* ar71xx: fold 641-MIPS-ath79-fix-AR934x-OTP-offsets.patch into the patch that ↵Felix Fietkau2017-04-2615-131/+91
| | | | | | it fixes Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ar71xx: Add OTP support for AR934xChris Blake2017-04-261-0/+66
| | | | | | | | | | The patch 523-MIPS-ath79-OTP-support only supports the OTP offsets for AR933x chips, which has changed on newer platforms such as the AR934x. The follwoing change is to add support for reading the OTP on the AR934x. Tested on an Aerohive AP-121. Signed-off-by: Christian Lamparter <chunkeey@googlemail.com> Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
* ar71xx: fix minor syntax error in /lib/upgrade/platform.shMatthias Schiffer2017-04-221-1/+1
| | | | | | | Fix a '==' that should be a '=' in a test condition. Busybox fortunately doesn't care. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ar71xx: fix ath9k default LED changes falloutMathias Kresin2017-04-134-13/+22
| | | | | | | | | | | | | | | | Since 192f0a3db859 ("ath9k: unset the default LED pin if used by platform leds") the default ath9k wireless LED is not set as soon as any pin of the ath ath9k gpio controller is used. All touched boards have leds defined which are using the gpio pins exposed by the ath9k driver but rely on a default set wireless led trigger. Add the wireless leds were missing and setup the wireless phy trigger in userspace. Signed-off-by: Russell Senior <russell@personaltelco.net> Signed-off-by: Mathias Kresin <dev@kresin.me>
* ar71xx: add correct named default wireless led by using platform ledsMathias Kresin2017-04-085-43/+28
| | | | | | | | | | | | | Instead of renaming the default wireless led attached to the wireless chip, add a new led using the platform leds with the phy0tpt trigger set in userspace. When switching ar71xx to device tree, the same can be done by using the build in GPIO controller and without adding new bindings. Drop the now unused platform code. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ar71xx: tp-link.mk: always include device version in image and DEVICE_TITLEPiotr Dymacz2017-04-031-54/+54
| | | | | | | | | | | | | | | | | | | | There are currently several supported TP-Link devices without specified version number in image name and/or DEVICE_TITLE (e.g. WBS210, WBS510, TL-WR810N, TL-WA7510N, TL-WPA8630), but vendor website shows that there are already more than one version of them on the market. For devices like Archer C5, which second version is based on a total different platform, missing version number in DEVICE_TITLE (used in menuconfig) might be misleading for users. To make it less confusing for users and easier to maintain in future, include version number in image name and DEVICE_TITLE for all TP-Link devices, even if there is only one version of device at the moment. Also, keep DEVICE_TITLE in same format for all TP-Link devices. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> Acked-by: John Crispin <john@phrozen.org>
* ar71xx: add userspace support for Mikrotik RB2011iLRon Angeles2017-04-036-2/+11
| | | | | | | | | Kernel/hardware support for this board has been implemented since Chaos Calmer. This set of patches is to get the board identified in userland. This will allow support for things like sysupgrade, configuring initial LED state, configuring initial switch state, etc. Signed-off-by: Ron Angeles <ronangeles@gmail.com>
* ar71xx: add TP-LINK TL-WR841N/ND v12 imageVittorio Gambaletta2017-04-031-1/+7
| | | | | | | | | | | | | This router has the same hardware as TP-LINK TL-WR841N/ND v11 (same FCC ID, same TFTP image name...). If the stock firmware web interface doesn't accept LEDE factory image, it can be flashed via the U-Boot TFTP recovery mode, by long-pressing the reset button after power on. The TFTP image name is wr841nv11_tp_recovery.bin (yes, v11, not v12). Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net>
* ar71xx: Compex WPJ563 supportChristian Mehlis2017-03-3012-0/+186
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Specification: - SoC: Qualcomm Atheros QCA9563 (775 MHz, MIPS 74Kc) - RAM: 128 MiB - Storage: 16MB NOR flash - Wireless: Built into QCA9563 (Dragonfly), PHY modes b/g/n, 3x3 MIMO - Ethernet: 2x1G Tested and working: - ethernet / switch / lan / wan - 2.4GHz SoC wifi - PCIe - leds - buzzer Ramload: - tftpboot 0x84000000 lede-ar71xx-generic-wpj563-16M-initramfs-uImage.bin - bootm 0x84000000 Install: - tftpboot 0x80500000 lede-ar71xx-generic-wpj563-16M-squashfs-sysupgrade.bin - erase 0x9f030000 +$filesize - erase 0x9f680000 +1 - cp.b $fileaddr 0x9f030000 $filesize Erasing 0x9f680000 is required because uboot defines "bootcmd=bootm 0x9f680000 || bootm 0x9f030000", so it first tries to boot the higher address. I think the 16 mb flash are intended to be used as 8+8mb for a fallback image. In my hardware only the lower address has a bootable image. But to make sure future hardware will boot lede too, I erase one block, so uboot will skip this address. Signed-off-by: Christian Mehlis <christian@m3hlis.de>
* ar71xx: drop default CONSOLE valuesJohn Crispin2017-03-291-4/+0
| | | | | | Compex boards dont need to set these as they are default. Signed-off-by: John Crispin <john@phrozen.org>
* ar71xx: move Compex WPJ342 to generic build targetChristian Mehlis2017-03-293-7/+10
| | | | Signed-off-by: Christian Mehlis <christian@m3hlis.de>
* ar71xx: move Compex WPJ344 to generic build targetChristian Mehlis2017-03-293-7/+10
| | | | Signed-off-by: Christian Mehlis <christian@m3hlis.de>
* ar71xx: move Compex WPJ531 to generic build targetChristian Mehlis2017-03-293-7/+10
| | | | Signed-off-by: Christian Mehlis <christian@m3hlis.de>
* ar71xx: move Compex WPJ558 to generic build targetChristian Mehlis2017-03-293-7/+10
| | | | Signed-off-by: Christian Mehlis <christian@m3hlis.de>
* ar71xx: wpj531: fix GPIOs for LEDLeon M. George2017-03-271-4/+4
| | | | | | /sys/devices/platform/leds-gpio/leds/ was not initialised with working LEDs. Signed-off-by: Leon M. George <leon@georgemail.eu>
* kernel: update kernel 4.4 to 4.4.56Hauke Mehrtens2017-03-261-1/+1
| | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* treewide: select ath10k firmware explicitMathias Kresin2017-03-241-2/+2
| | | | | | Do not rely on the default firmware selected by ath10k. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ar71xx: image: fix indentationPiotr Dymacz2017-03-234-553/+553
| | | | Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ar71xx: add support for P&W R602N and CPE505NPiotr Dymacz2017-03-2313-8/+285
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | P&W (full name: Shenzhen Progress&Win Technologies) R602N (could be also labeled as R602F, R602, etc.) is a simple N300 router with 5-port 10/100 Mbps switch, non-detachable antennas and USB. CPE505 is an outdoor CPE with PoE support and detachable antennas. Both devices are based on Qualcomm/Atheros QCA9531 v2. Common specification: - 650/597/216 MHz (CPU/DDR/AHB) - 64 MB of RAM (DDR2) - 16 MB of FLASH - UART (J2) header on PCB R602N specification: - 5x 10/100 Mbps Ethernet - 1x USB 2.0 - 2T2R 2.4 GHz with external LNA and PA (SE2576L), up to 28 dBm - 2x external, non-detachable antennas - 7x LED, 1x button CPE505N specification: - 2x 10/100 Mbps Ethernet (both ports support passive PoE 12-24 V) - 2T2R 2.4 GHz with external LNA and PA (SKY65174-21), up to 30 dBm - 2x external, detachable antennas (RP-SMA connectors) - 1x RGB LED, 2x LEDs (in RJ45 sockets), 1x button Flash instructions: It seems that there are many different versions of the firmware which these devices are shipped with. The generic/standard one is based on some modified OpenWrt and LEDE firmware can be flashed directly from vendor's webgui or with sysupgrade (root password is "admin123"). Before flashing, make sure (use "fw_printenv") that the kernel load address in your device is set to "0x9f050000" (bootcmd variable is "bootm 0x9f050000"). If your device uses different load address, you should first change it, under vendor's firmware, with command: fw_setenv bootcmd "bootm 0x9f050000 || bootm OLD_ADDRESS" Where OLD_ADDRESS is previous kernel load address (in CPE505 version I got access to, it was "0x9fe80000"). This will allow you to use both the vendor's and LEDE firmware. If version of your device contains empty U-Boot environment (you will get information about this after issuing "fw_printenv"), you should use U-Boot, serial line access and TFTP to perform firmware upgrade: 1. tftp 0x80060000 lede-ar71xx-generic-...-squashfs-sysupgrade.bin 2. erase 0x9f050000 +$filesize 3. cp.b $fileaddr 0x9f050000 $filesize 4. setenv bootcmd "bootm 0x9f050000 || bootm OLD_ADDRESS" 5. saveenv && reset These devices contain also web recovery mode inside U-Boot. It can be started with pressing the reset button for around 3 seconds just after the device powerup. Web recovery panel is available on "192.168.10.9" and to be able to use it, IP on your PC must be set to "192.168.10.10". Make sure to change kernel load address before using recovery mode or the U-Boot will not be able to load LEDE firmware. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ar71xx: add support for TP-LINK TL-WR840N v2 and v3Vaclav Svoboda2017-03-2313-2/+115
| | | | | | | | | | | | | | This patch adds support for the TP-LINK TL-WR840N v2 and v3. - SoC: Qualcomm QCA9533-BL3A (650 MHz) - RAM: 32 MiB (Zentel A3S56D40GTP) - Flash: 4 MiB (v2: Macronix MX 25L323F) (v3: Winbond 25Q32FVSIG) - LAN: 4x 100M - WAN: 1x 100M Signed-off-by: Vaclav Svoboda <svoboda@neng.cz>
* ar71xx: add support for MikroTik hAP acRyan Mounce2017-03-2311-3/+175
| | | | | | | | | | | This patch adds initial support for the MikroTik RouterBOARD hAP ac (RB962UiGS-5HacT2HnT). All functions are supported except: -SFP cage (eth1) is not working -WLAN LEDs are not working Signed-off-by: Ryan Mounce <ryan@mounce.com.au>
* ar71xx: add support for MikroTik hAP ac liteRyan Mounce2017-03-2311-10/+47
| | | | | | | | | | This patch adds support for the MikroTik RouterBOARD hAP ac lite (RB952Ui-5ac2nD). The hAP ac lite is nearly identical to the hAP, with an added QCA9887 5GHz radio. The 2.4GHz radio ID is also changed in the hAP ac lite. Signed-off-by: Ryan Mounce <ryan@mounce.com.au>
* ar71xx: mikrotik: prepend "RouterBOARD" to machine name for NOR devicesThibaut VARENE2017-03-151-3/+15
| | | | | | | | | | | | When the device name doesn't already contain "RouterBOARD", this patch adds this string to the machine name. Most NOR devices already have "RouterBOARD" in their hardware-stored device name, but not all of them. This patch also makes the code more robust against buffer overflows. Signed-off-by: Thibaut VARENE <hacks@slashdirt.org>
* ar71xx: add support for RB LHG 5nDThibaut VARENE2017-03-1510-34/+146
| | | | | | | | | | | | | | | | This patch adds support for the MikroTik RouterBOARD LHG 5 https://routerboard.com/RBLHG-5nD Specifications: - SoC: Atheros AR9344 (600MHz) - RAM: 64MB - Storage: 16MB NOR SPI flash - Wireless: builtin AR9344 5GHz, 2x2:2 - Ethernet: 1x100M Initial flash via initramfs, like all other RB devices. Signed-off-by: Thibaut VARENE <hacks@slashdirt.org>
* ar71xx: WNDR4300: Fix network vlan IDsDaniel Gonzalez Cabanelas2017-03-131-3/+3
| | | | | | The Netgear WNDR4300 has the VLAN IDs flipped in LuCi, fix it. Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com>
* ar71xx: WNDR4300: Fix switch HW controlled LEDsDaniel Gonzalez Cabanelas2017-03-131-4/+4
| | | | | | | | | | | | The Netgear WNDR4300, equipped with an Atheros AR8327 Gigabit Switch, has two LEDs on each port for monitoring LAN activity, but it currently only uses one. Fix the configuration to use both. The patch provides this new configuration: - green LED: 1 Gbps link, 4Hz blink frequency - amber LED: 10/100 Mbps link. 4Hz for 100Mbps, 2Hz for 10Mbps Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com>
* ar71xx: fix Wallys DR344 ethernet MAC addresses offsetsPiotr Dymacz2017-03-121-2/+3
| | | | | | | Without this fix, ethernet interfaces on Wallys DR344 use random MAC addresses. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ar71xx: base-files: few minor cleanups in lib/ar71xx.shPiotr Dymacz2017-03-121-39/+16
| | | | Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ar71xx: base-files: fix boards order in lib/ar71xx.shPiotr Dymacz2017-03-121-276/+276
| | | | | | Keep everything within case statements in alphabetical order. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ar71xx: base-files: shorten case statement patterns in lib/ar71xx.shPiotr Dymacz2017-03-121-13/+13
| | | | | | | | | | | | | | At now there is no general rule about what part of (or whole) machine name string should be used for board name assignment/detection and every target handles this in a different way. For most of the boards in ar71xx we already use only part of the string, generally without the vendor name. This shortens wildcards patterns in case statement for board name assignment, wherever possible (e.g. where it won't be misleading). Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ar71xx: base-files: always use double quotes in lib/ar71xx.shPiotr Dymacz2017-03-121-104/+104
| | | | | | | | | | Be consistent and always use double quotes for case statement patterns, as in other targets. With this approach it should be less confusing for users adding support for new devices. Also, be consistent with MikroTik boards wildcard pattern. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ar71xx: base-files: fix indentation in lib/ar71xx.shPiotr Dymacz2017-03-121-19/+19
| | | | Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ar71xx: fix machine name for several devicesPiotr Dymacz2017-03-123-4/+4
| | | | | | Be consistent with form and format of the vendor name. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ar71xx: add support for Rockeetech AP531B0Shuanglin Liu2017-03-1212-4/+148
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Specification: - SoC: Qualcomm Atheros QCA9531 (650/400/216 MHz (CPU/DDR/AHB)) - RAM: 64 MiB DDR2 - Storage: 16 MiB of flash (optional 16 MiB second flash) - Wireless: built into QCA9531 (Honey Bee), PHY modes b/g/n - Ethernet: 1x100M (port0) 1x100M (port 4) - PCI-E: x1 - SIMcard slot: x1 - USB 2.0 port: x1 (optional) - Ext GPIO pin: x8 - UART for serial console: x1 - External watchdog: x1 (optional) - Power supply: 9-48V (DC jack/passive PoE) Installation through tftp: - Copy <Firmware Image Name> into tftp directory - Connect board via ttl port and Ethernet port - Boot the AP531B0 - When "Autobooting in 1 seconds" appears press Enter - Set serverip and ipaddr appropriate (e.g. setenv serverip 192.168.88.10;setenv ipaddr 192.168.88.1) - Enter "tftp 0x8050000 <Firmware Image Name>" - Enter "erase 0x9f050000 +$filesize" - Enter "cp.b 0x80500000 0x9f050000 $filesize" - Enter "reset" Signed-off-by: Shuanglin Liu <roboidler@gmail.com>
* kernel: update kernel 4.4 to 4.4.53Hauke Mehrtens2017-03-121-1/+1
| | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ar71xx: add ath10k driver and firmware for Netgear R6100 to firmware imageStijn Segers2017-03-111-1/+1
| | | | | | | | A Netgear R6100 owner reported the LEDE images lack the ath10k driver and firmware [1]. This patch adds both to the R6100 image. [1] https://forum.lede-project.org/t/netgear-r6100-5ghz-wifi-not-working-after-initial-install/2222 Signed-off-by: Stijn Segers <francesco.borromini@inventati.org>
* ar71xx: fix build without CONFIG_NOP_USB_XCEIV (FS#593)Felix Fietkau2017-03-071-9/+6
| | | | | | | | Open-code usb_phy_generic_register instead of calling it, since it is really trivial. Avoid pulling CONFIG_NOP_USB_XCEIV into the kernel config and add a proper dependency instead Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ar71xx: set status led for the gl-* boardsWojciech Jowsa2017-03-064-128/+129
| | | | Signed-off-by: Wojciech Jowsa <w.jowsa@radytek.com>
* ar71xx: mikrotik: erase firmware partition on SPI NOR devices in pre_upgrade()Thibaut VARENE2017-02-261-0/+8
| | | | | | | | | | | | On Mikrotik SPI NOR devices, the firmware partition must be erased when flashing from stock firmware, otherwise leftover bits (in particular a kernel signature) can trigger a boot loop. When booted from initramfs (the only way to flash LEDE on these devices), this patch unconditionally erases the firmware partition in the pre_upgrade() stage for all supported SPI NOR devices. Signed-off-by: Thibaut VARENE <hacks@slashdirt.org>
* ar71xx: Enable RB2011 TTYArvid E. Picciani2017-02-261-1/+2
| | | | | | Enables TTY on the Mikrotik RouterBoard RB2011*R* Signed-off-by: Arvid E. Picciani <aep@exys.org>
* ar71xx: use common firmware partition for WNDAP360Felix Fietkau2017-02-231-2/+2
| | | | | | Patch from https://github.com/openwrt/openwrt/pull/398 Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: update kernel 4.4 to 4.4.50Kevin Darbyshire-Bryant2017-02-231-11/+11
| | | | | | | | | | Bump kernel from 4.4.49 to 4.4.50 Compile tested: All targets Run tested: ar71xx Archer C7 v2 Signed-off-by: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
* ar71xx: Enable mtdsplit support for RB SPI NOR devicesThibaut VARENE2017-02-224-32/+17
| | | | | | | | | | | | | | | | | | This patch enables mtdsplit for the MikroTik subtarget. It converts mach-rbspi.c to use a single "firmware" partition. Finally, it converts the SPI NOR profile to metadata images: the original combined-image format is gone, the images are now "standard" sysupgrade images with metadata appended. Note: kernel2minor apparently pads the kernel container to erase-block boundary, but this is undocumented behaviour, so we do not rely on it and call pad-to anyway. Note: in platform.sh, the boards are tested last in platform_check_image() as this should eventually become the "*)" default case when more devices switch to metadata images. Signed-off-by: Thibaut VARENE <hacks@slashdirt.org>
* ar71xx: remove bogus "rb*)" catch-all from platform.shThibaut VARENE2017-02-221-8/+54
| | | | | | This patch replaces a dangerous catch-all with the exhaustive list of devices. Signed-off-by: Thibaut VARENE <hacks@slashdirt.org>
* ar71xx: fix vlan settings for some boardsWeijie Gao2017-02-201-1/+1
| | | | | | | | | | | For AR71XX devices, GMAC1 always connects port 0 of the built-in switch, as the CPU port. This patch sets correct vlan for some devices with wrong settings: a) mark port 0 as CPU port, tagged b) reverse port order, marking these ports untagged Signed-off-by: Weijie Gao <hackpascal@gmail.com>
* ar71xx: Add more boards to the routerboard serial detection patchThibaut VARENE2017-02-201-1/+3
| | | | | | This patch enables serial console on the 435 series and the 953gs. Signed-off-by: Thibaut VARENE <hacks@slashdirt.org>
* ar71xx: add support for TL-WR802N Version 2Thomas Roberts2017-02-2012-2/+136
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for the TP-Link TL-WR802N Version 2. Specification: - SoC: Qualcomm Atheros QCA9533 (560 MHz, MIPS 24Kc) - RAM: 32 MiB - Storage: 4 MiB of FLash on board - Wireless: Built into QCA9533 (Honey Bee), PHY modes b/g/n - Ethernet: 1x100M (port0) Installation through OEM Web Interface: - Connect to TL-WR802N by Ethernet or Wi-Fi - Go to http://192.168.0.1 (default user is "admin" & password is "admin) - Go to "System Tools -> Firmware Upgrade" - Browse for firmware "*.factory-us.bin" or "*.factory-eu.bin" for eu model - Click upgrade Installation through tftp: Note: T_OUT, T_IN and GND on the board must be connected to USB TTL Serial Configuration 115200 8n1 - Boot the TL-WR802N - When "Autobooting in 1 seconds" appears type "tpl" followed by enter - Connect to the board Ethernet port (IPADDR: 192.168.1.1, ServerIP: 192.168.1.10) - tftpboot 0x80000000 <Firmware Image Name> - Record the result of "printenv bootcmd" - Enter "erase <Result of 'printenv bootcmd'> +0x3c0000" (e.g erase 0x9f020000 +0x3c0000) - Enter "cp.b 0x80000000 <Result of 'printenv bootcmd'> 0x3c0000" (e.g cp.b 0x80000000 0x9f020000 0x3c0000) - Enter "bootm <Result of 'printenv bootcmd'>" (e.g bootm 0x9f020000) Signed-off-by: Thomas Roberts <tom.p.roberts@gmail.com>
* ar71xx: fix ethernet PLL configuration for QCA956xFelix Fietkau2017-02-171-1/+1
| | | | | | | QCA956x is configured like AR934x, not like the older chips. Should fix ethernet hangs when using the WAN port without SGMII Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ar71xx: fix lan ports on archer C59 and C60Henryk Heisig2017-02-174-14/+39
| | | | Signed-off-by: Henryk Heisig <hyniu@o2.pl>
* ar71xx: add support for 8devices Lima boardKarol Dudek2017-02-1710-0/+117
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Lima is a module for the (IoE) internet of everything applications, based on Qualcomm/Atheros QCA4531. Specification: - 650/600/216 MHz (CPU/DDR/AHB) - 64 MB of RAM (DDR2) - 32 MB of FLASH - 2T2R 2.4 GHz - 2x 10/100 Mbps Ethernet - USB 2.0 Host - PCIe - UART for serial console - 14x GPIO Flash instruction: 1. Download lede-ar71xx-generic-lima-squashfs-sysupgrade.bin and rename it to 8dev_recovery.bin 2. Binary file copy to USB stick and plug into slot USB 3. Press S2 (reset) button 4. Press and hold the S1 button by 5 seconds 5. Wait ~40 seconds to complete recovery Tested on: - Lima development kit Signed-off-by: Karol Dudek <karoiz@sli.pl>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-07 12:59:47 +0000