aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* ar71xx: unify CONFIG_CMDLINEFelix Fietkau2017-09-284-4/+1
| | | | | | | Booting from jffs2 directly is no longer supported, use rootfstype=squashfs consistently for all subtargets Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ramips: reduce napi_weight in the ethernet driver.Rosen Penev2017-09-281-1/+1
| | | | | | Currently dmsg a weight of 128 which is above the kernel limit of 64. Silence the warning. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* ramips: mt7621: add MT29F2G08ABAE NAND flash supportRoman Yeryomin2017-09-281-1/+2
| | | | Signed-off-by: Roman Yeryomin <roman@advem.lv>
* ramips: improve Xiaomi Mi Router 3G supportKevin Darbyshire-Bryant2017-09-284-26/+59
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit improves support for the Xiaomi Mi Router 3G originally added in commit 6e283cdc0da25928f8148805ebef7f8f2b769ee8 Improvements: - Remove software watchdog as hardware watchdog now working as per commit 3fbf3ab44f5cebb22e30a4c8681b13341feed6a6 for all mt7621 devices. - Reset button polarity corrected - length of press determines reboot (short press) vs. reset to defaults (long press) behaviour. - Enable GPIO amber switch port LEDs on board rear - lit indicates 1Gbit link and blink on activity. Green LEDs driven directly by switch indicating any link speed and tx activity. - USB port power on/off GPIO exposed as 'usbpower' - Add access to uboot environment settings for checking/setting uboot boot order preference from user space. Changes: - Front LED indicator is physically made of independent Yellow/Amber, Red & Blue LEDs combined via a plastic 'lightpipe' to a front panel indicator, hence the colour behaviour is similar to an RGB LED. RGB LEDs are not supported at this time because they produce colour results that do not then match colour labels, e.g. enabling 'mir3g:red' and 'mir3g:blue' would result in a purple indicator and we have no such label for purple. The yellow, red & blue LEDs have been split out as individual yellow, red & blue status LEDs, with yellow being the default status LED as before and with red's WAN and blue's USB default associations removed. - Swapped order of vlan interfaces (eth0.1 & eth0.2) to match stock vlan layout. eth0.1 is LAN, eth0.2 is WAN - Add 'lwlll' vlan layout to mt7530 switch driver to prevent packet leakage between kernel switch init and uci swconfig uboot behaviour & system 'recovery' uboot expects to find bootable kernels at nand addresses 0x200000 & 0x600000 known by uboot as "system 1" and "system 2" respectively. uboot chooses which system to hand control to based on 3 environment variables: flag_last_success, flag_try_sys1_failed & flag_try_sys2_failed last_success represents a preference for a particular system and is set to 0 for system 1, set to 1 for system 2. last_success is considered *if* and only if both try_sys'n'_failed flags are 0 (ie. unset) If *either* failed flags are set then uboot will attempt to hand control to the non failed system. If both failed flags are set then uboot will check the uImage CRC of system 1 and hand control to it if ok. If the uImage CRC of system is not ok, uboot will hand control to system 2 irrespective of system 2's uImage CRC. NOTE: uboot only ever sets failed flags, it *never* clears them. uboot sets a system's failed flag if that system's was selected for boot but the uImage CRC is incorrect. Fortunately with serial console access, uboot provides the ability to boot an initramfs image transferred via tftp, similarly an image may be flashed to nand however it will flash to *both* kernels so a backup of stock kernel image is suggested. Note that the suggested install procedure below set's system 1's failed flag (stock) thus uboot ignores the last_success preference and boots LEDE located in system 2. Considerable thought has gone into whether LEDE should replace both kernels, only one (and which one) etc. LEDE kernels do not include a minimal rootfs and thus unlike the stock kernel cannot include a method of controlling uboot environment variables in the event of rootfs mount failure. Similarly uboot fails to provide an external mechanism for indicating boot system failure. Installation - from stock. Installation through telnet/ssh: - copy lede-ramips-mt7621-mir3g-squashfs-kernel1.bin and lede-ramips-mt7621-mir3g-squashfs-rootfs0.bin to usb disk or wget it from LEDE download site to /tmp - switch to /extdisks/sda1/ (if copied to USB drive) or to /tmp if wgetted from LEDE download site - run: mtd write lede-ramips-mt7621-mir3g-squashfs-kernel1.bin kernel1 - run: mtd write lede-ramips-mt7621-mir3g-squashfs-rootfs0.bin rootfs0 - run: nvram set flag_try_sys1_failed=1 - run: nvram commit - run: reboot Recovery - to stock. Assuming you used the above installation instructions you will have a stock kernel image in system 1. If it can be booted then it may be used to perform a stock firmware recovery, thus erasing LEDE completely. From a 'working' LEDE state (even failsafe) Failsafe only: - run: mount_root - run: sh /etc/uci-defaults/30_uboot-envtools Then do the steps for 'All' All: - run: fw_setenv flag_try_sys2_failed 1 - run: reboot The board will reboot into system 1 (stock basic kernel) and wait with system red light slowly blinking for a FAT formatted usb stick with a recovery image to be inserted. Press and hold the reset button for around 1 second. Status LED will turn yellow during recovery and blue when recovery complete. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* ramips: RT5350F-OLINUXINO: enable ttyS1Zoltan Gyarmati2017-09-281-1/+16
| | | | | | | | | The RT5350F's second UART pins are available on the base module and on the EVB as well, so enable it in the device tree. In order to keep the origian serial port numbering (ttyS0 is the serial console), aliases added for the UART devices. Signed-off-by: Zoltan Gyarmati <mr.zoltan.gyarmati@gmail.com>
* ramips: RT5350F-OLINUXINO: enable i2cZoltan Gyarmati2017-09-281-0/+4
| | | | | | | The RT5350F i2c pins is available on the base module and on the EVB as well, so enable it in the dts. Signed-off-by: Zoltan Gyarmati <mr.zoltan.gyarmati@gmail.com>
* ramips: RT5350F-OLINUXINO: invert WiFi LED polarityZoltan Gyarmati2017-09-281-0/+1
| | | | | | | The polarity of WLAN_ACT LED on the base module needs to inverted in order to be 'on' when the WiFi interface is active Signed-off-by: Zoltan Gyarmati <mr.zoltan.gyarmati@gmail.com>
* ramips: introduce RT5350F-OLINUXINO.dtsiZoltan Gyarmati2017-09-283-140/+76
| | | | | | | | | | The RT5350F-OLINUXINO(-EVB).dts files' content are nearly the same, so to avoid code duplication this patch creates RT5350F-OLINUXINO.dtsi file which covers the base board's features. The corresponding RT5350F-OLINUXINO.dts just includes the new .dtsi and the RT5350F-OLINUXINO-EVB.dts adds the EVB specific GPIO config. Signed-off-by: Zoltan Gyarmati <mr.zoltan.gyarmati@gmail.com>
* ramips: add 'lwlll' portmap to mt7530 switchKevin Darbyshire-Bryant2017-09-281-1/+7
| | | | | | | | | | | The Xiaomi Mi Router 3G uses this deranged vlan portmap. Add support so that packets are not leaked across all switch ports when reset. Fix a whitespace nit while we're here. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> [fix wrong pvids order] Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: mt7621: fix failsafe mode networkingKevin Darbyshire-Bryant2017-09-281-2/+7
| | | | | | | | | | Disable VLANs on mt7621 boards with mt7530 switches on failsafe entry. Allows failsafe networking to work correctly. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> [fixed default case syntax error] Signed-off-by: Mathias Kresin <dev@kresin.me>
* kernel: update 4.9 to 4.9.52Stijn Tintel2017-09-281-1/+1
| | | | | | | | Refresh patches. Compile-tested on x86/64. Runtime-tested on x86/64. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* Revert "brcm47xx: Fix sysupgrade with E1200v1"Hauke Mehrtens2017-09-251-1/+0
| | | | | | | | | | This reverts commit 31e9445b7e614f54daa0caf3148e223d088311ab. "Linksys E1200 V1" is not a valid board name, as the brcm47xx arch code can not detect this device. Stefan Lippers-Hollmann also found a typo in this patch "cybetran" instead of "cybertan". Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* brcm47xx: Fix sysupgrade with E1200v1Rosen Penev2017-09-241-0/+1
| | | | | | Entry was missing for some reason. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* sunxi: add Olimex A20-OLinuXino-LIME2-eMMCLucian Cristian2017-09-241-0/+10
| | | | | | Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com> [replaced u-boot patch with original version from u-boot git] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: don't scrimp on memory on big ironPhilip Prindeville2017-09-242-4/+10
| | | | | | | | | x86_64 platforms typically don't lack memory, so don't needlessly economize memory if fq_codel on capable platforms. Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com> [Add a comment to the patch] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ramips: fix missing mediatek wdtKevin Darbyshire-Bryant2017-09-222-2/+2
| | | | | | | | | | | | | | | mediatek MT7621 soc watchdog DTS id was renamed from "mtk,mt7621-wdt" to "mediatek,mt7621-wdt" when driver upstreamed to kernel 4.5 Update mt7621.dtsi & mt7628an.dtsi definitions to match upstreamed kernel. Restores hardward watchdog functionality on mt7621 devices under linux 4.9 Tested on: MIR3G Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* kernel: update 4.9 to 4.9.51Stijn Tintel2017-09-2012-37/+37
| | | | | | | | | | | | Refresh patches. Compile-tested on octeon and x86/64. Runtime-tested on octeon and x86/64. Fixes the following CVEs: - CVE-2017-14106 - CVE-2017-14497 Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* at91: Add UBI parameters for sama5d4.Sandeep Sheriker Mallikarjun2017-09-201-1/+6
| | | | | | Add UBIFS_OPTS & UBINIZE_OPTS parameters for sama5d4 Xplained board. Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* at91: Add SAMA5D4 deviceSandeep Sheriker Mallikarjun2017-09-202-0/+11
| | | | | | | Add support for SAMA5D4 with target device as at91-sama5d4_xplained in SAMA5 subtarget and build images for SAMA5D4 Xplained board. Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* at91: Add SAMA5D2 deviceSandeep Sheriker Mallikarjun2017-09-202-0/+11
| | | | | | | Add support for SAMA5D2 with target device as at91-sama5d2_xplained in SAMA5 subtarget and build images for SAMA5D2 Xplained board. Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* at91: Install zImage.Sandeep Sheriker Mallikarjun2017-09-201-0/+6
| | | | | | Installing zImage to bin folder of device target. Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* at91: Renaming subtarget sama5d3 to sama5Sandeep Sheriker Mallikarjun2017-09-205-8/+8
| | | | | | | | | Renaming at91 subtarget sama5d3 to sama5 and using at91-sama5d3_xplained as a target device in sama5 subtarget.This will enable to add other sama5d2 & sama5d4 target devices in sama5 subtraget.This will avoid code duplication when sama5d2 & sama5d4 added as different subtarget. Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* sunxi: add Olimex A20-OlinuXino-LIME2Lucian Cristian2017-09-181-0/+10
| | | | Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* sunxi: Add A64 support with cortex53 subtargetHauke Mehrtens2017-09-185-1/+135
| | | | | | | | | | | | This adds initial support for the A64 Allwinner SoC to LEDE. It will be build in the new cortexa53 subtarget. Currently it only supports the pine64 and the image is able to boot on this SoC. Camera, Ethernet, HDMI and other parts are currently not working. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* sunxi: Backport patches from kernel 4.11 for A64Hauke Mehrtens2017-09-1814-0/+640
| | | | | | | This backports some more patches from kernel 4.11 adding more devices to the device tree of the A64 SoC. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* sunxi: Backport patches needed for A64Hauke Mehrtens2017-09-1825-0/+4665
| | | | | | | | This backports multiple patches from kernel 4.10 which are adding missing support for the A64 and the pine64 board. These are the device tree files, the pinctlk and the clock driver. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* sunxi: split into cortex A8 and A7 subtargetHauke Mehrtens2017-09-188-151/+223
| | | | | | Now we can activate some compiler optimizations for the cortex A7. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* sunxi: fix build of rtc package when module not availableHauke Mehrtens2017-09-181-2/+2
| | | | | | | If the Kconfig option CONFIG_RTC_DRV_SUNXI is not selected this package should be be build. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* sunxi: add support for kernel 4.9Hauke Mehrtens2017-09-184-1/+689
| | | | | | | Most of the patches were backpoprts from the mainline kernel and are integrated upstream now. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: add some config optionsHauke Mehrtens2017-09-181-0/+10
| | | | | | These are needed for the sunxi target. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* rb532: drop 4.4 supportStijn Tintel2017-09-184-268/+0
| | | | Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* rb532: add myself as maintainerRoman Yeryomin2017-09-181-0/+1
| | | | Signed-off-by: Roman Yeryomin <roman@advem.lv>
* rb532: switch to 4.9Roman Yeryomin2017-09-181-1/+1
| | | | Signed-off-by: Roman Yeryomin <roman@advem.lv>
* rb532: add support for 4.9Roman Yeryomin2017-09-1810-0/+675
| | | | | | | | Includes latest korina fixes. Signed-off-by: Roman Yeryomin <roman@advem.lv> [rewrite commit message (subject <= 50 characters)] Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* rb532: set lan interface type to brigdeRoman Yeryomin2017-09-181-0/+1
| | | | Signed-off-by: Roman Yeryomin <roman@advem.lv>
* rb532: increase kernel size limitRoman Yeryomin2017-09-181-1/+1
| | | | | | | | This is required to support kernel 4.9. Signed-off-by: Roman Yeryomin <roman@advem.lv> [rewrite commit message (subject <= 50 characters)] Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: update 4.9 to 4.9.50Stijn Tintel2017-09-183-73/+65
| | | | | | | | | | | | Refresh patches. Compile-tested on ipq8065/nbg6817 and x86/64. Runtime-tested on ipq8065/nbg6817 and x86/64. Fixes CVE-2017-1000251. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> [adapt qcom_nandc.c patches to match upstream changes, test ipq8065/nbg6817] Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* kernel: update to 3.18.71Florian Fainelli2017-09-1838-415/+131
| | | | | | | | | | Delete a bunch of fixes that are already included. Refresh patches. Compile-tested on malta/mipsel Runtime-tested on malta/mipsel Signed-off-by: Florian Fainelli <f.fainelli@gmail.com> Acked-by: Hauke Mehrtens <hauke@hauke-m.de>
* generic: drop 704-phy-no-genphy-soft-reset.patchFlorian Fainelli2017-09-162-42/+0
| | | | | | | | | | | | 4.4.80+ contains 71a165f6397df07a06ce643de5c2dbae29bd3cfb, 4.9.41+ contains 6c78197e4a69c19e61dfe904fdc661b2aee8ec20 which are all backports of upstream commit 0878fff1f42c18e448ab5b8b4f6a3eb32365b5b6 ("net: phy: Do not perform software reset for Generic PHY"). Our local patch is no longer needed, all this patch was doing was utilizing gen10g_soft_reset which does nothing either, so just keep the code unchanged. Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
* armvirt: Enable CONFIG_ARM_PMUFlorian Fainelli2017-09-161-0/+1
| | | | | | | We will be prompted with this config symbol when performance monitoring is enabled in the kernel. Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
* mvebu: WRT3200ACM: add bluetooth moduleHenryk Heisig2017-09-171-1/+1
| | | | Signed-off-by: Henryk Heisig <hyniu@o2.pl>
* kernel: add packaging for Xeon iTCO watchdog timerPhilip Prindeville2017-09-171-1/+1
| | | | Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
* kernel: update 4.4 to 4.4.88Kevin Darbyshire-Bryant2017-09-162-20/+20
| | | | | | | Refresh patches. Compile & run tested: ar71xx Archer C7 v2 Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* ramips: fix used MAC addresses for Phicomm K2PJiawei Wang2017-09-151-1/+1
| | | | | | | | | | | | | | | The factory partition of the Phicomm K2P contains two MAC addresses. The lower MAC address is at offset 0xe006 and the higher one is at offset 0xe000. Use the lower MAC address as base mac-address which the switch driver increments by one for the second (wan) vlan. The MAC addresses are still inverted in contrast to the stock firmware where the lower MAC address is used for wan. But at least the use of a MAC address not intended/reserved for this particular board is fixed. Signed-off-by: Jiawei Wang <me@jwang.link>
* ramips: fix D240 mini-PCIe power control GPIOsKristian Evensen2017-09-131-3/+14
| | | | | | | | | | | | | | | | In commit b11c51916cb9 ("ramips: Improve Sanlinking D240 config") I made a mistake with regards GPIO numbering. And in addition to specifying the wrong GPIO for controling the power of one of the mini-PCIe, I recently discovered that the power of both slots can be controlled. This patch specifies the correct GPIO for the left-most mini-PCIe slot of the D240 (labeled power_mpcie2 since the slot is attached to SIM2), and adds a GPIO that can be used to control the power of the other mini-PCIe slot (labeled power_mpcie1). Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com> [do not use the gpio active macros for the gpio-export value] Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: add support for TP-Link Archer C20 v1Maxim Anisimov2017-09-137-0/+212
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link Archer C20 v1 is a router with 5-port FE switch and non-detachable antennas. It's very similiar to TP-Link Archer C50. Also it's based on MediaTek MT7620A+MT7610EN. Specification: - MediaTek MT7620A (580 Mhz) - 64 MB of RAM - 8 MB of FLASH - 2T2R 2.4 GHz and 1T1R 5 GHz - 5x 10/100 Mbps Ethernet - 2x external, non-detachable antennas - UART (J1) header on PCB (115200 8n1) - 8x LED (GPIO-controlled*), 2x button, power input switch - 1 x USB 2.0 port * WAN LED in this devices is a dual-color, dual-leads type which isn't (fully) supported by gpio-leds driver. This type of LED requires both GPIOs state change at the same time to select color or turn it off. For now, we support/use only the blue part of the LED. * MT7610EN ac chip isn't not supported by LEDE. Therefore 5Ghz won't work. Factory image notes: These devices use version 3 of TP-Link header, fortunately without RSA signature (at least in case of devices sold in Europe). The difference lays in the requirement for a non-zero value in "Additional Hardware Version" field. Ideally, it should match the value stored in vendor firmware header on device. We are able to prepare factory firwmare file which is accepted and (almost) correctly flashed from the vendor GUI. As it turned out, it accepts files without U-Boot image with second header at the beginning but due to some kind of bug in upgrade routine, flashed image gets corrupted before it's written to flash. So, to flash this device we must to prepare image using original firmware from tp-link site with uboot. Flash instruction: Until (if at all) TP-Link fixes described problem, the only way to flash LEDE image in these devices is to use tftp recovery mode in U-Boot. There are two ways to flash the device to LEDE: 1) Using tftp mode with UART connection and original LEDE image - Place lede-ramips-mt7620-ArcherC20-squashfs-factory.bin in tftp server directory - Configure PC with static IP 192.168.0.66/24 and tftp server. - Connect PC with one of LAN ports, power up the router and press key "4" to access U-Boot CLI. - Use the following commands to update the device to LEDE: setenv serverip 192.168.0.66 tftp 0x80060000 lede-ramips-mt7620-ArcherC20-squashfs-factory.bin erase tplink 0x20000 0x7a0000 cp.b 0x80060000 0x20000 0x7a0000 reset - After that the device will reboot and boot to LEDE 2) Using tftp mode without UART connection but require some manipulations with target image - Download and unpack TP-Link Archer C20 v1 firmware from original web site - Split uboot.bin from original firmware by this command (example): dd if=Archer_C20v1_0.9.1_4.0_up_boot(160427)_2016-04-27_13.53.59.bin of=uboot.bin bs=512 count=256 skip=1 - Create ArcherC20V1_tp_recovery.bin using this command: cat uboot.bin lede-ramips-mt7620-ArcherC20-squashfs-factory.bin > ArcherC20V1_tp_recovery.bin - Place ArcherC20V1_tp_recovery.bin in tftp server directory. - Configure PC with static IP 192.168.0.66/24 and tftp server. - Connect PC with one of LAN ports, press the reset button, power up the router and keep button pressed for around 6-7 seconds, until device starts downloading the file. - Router will download file from server, write it to flash and reboot. Signed-off-by: Maxim Anisimov <maxim.anisimov.ua@gmail.com>
* generic: drop support for get_port_stats() on ar8xxxThibaut VARENE2017-09-133-59/+18
| | | | | | | | | | | | | | | | The implementation is not efficient on ar8xxx switches. It triggers high CPU load and degrades device performance. The high CPU load has been traced down to the ar8xxx_reg_wait() call in ar8xxx_mib_op(), which has to usleep_range() till the MIB busy flag set by the request to update the MIB counter is cleared. This commit removes the get_port_stats() code introduced in 4d8a66d and leaves a note for future hacker's beware. Fixes: FS#1004 Signed-off-by: Thibaut VARENE <hacks@slashdirt.org>
* ramips: fix hg255d LED status supportDavid Yang2017-09-131-0/+1
| | | | | | | | Use the green power LED for boot status indication. Source: https://my.oschina.net/osbin/blog/278782 Para 3 Signed-off-by: David Yang <mmyangfl@gmail.com>
* ar71xx: fix MAC addresses on TP-Link TL-WR1043ND v4Matthias Schiffer2017-09-112-2/+3
| | | | | | | | | | The addresses were read from the 'config' partition, which would not always contain the addresses at the same offsets, depending on the stock firmware version used before flashing LEDE. Change this to get the addresses from the 'product-info' partition, which is read-only. Reported-and-tested-by: Andreas Ziegler <ml@andreas-ziegler.de> Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ramips: Add support for ZBT WE1026-5GKristian Evensen2017-09-117-1/+220
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The ZBT WE1026-5G (http://www.zbtlink.com/products/router/WE1026-5G.html) is the follow-up to the ZBT WE1026 and is based on MT7620. For the previous WE1026, the ZBT WE826 image could be used. However, as the name implies, the -5G comes equipped with a 5GHz wifi radio. As the WE826 only has a 2.4GHz radio, the addition of 5GHz means that a separate image is needed for the WE1026-5G. I suspect that this image will also work on the previous WE1026, but I don't have a device to test with. The WE1026-5G has following specifications: * CPU: MT7620A * 1x 10/100Mbps Ethernet. * 16 MB Flash. * 64 MB RAM. * 1x USB 2.0 port. * 1x mini-PCIe slots. * 1x SIM slots. * 1x 2.4Ghz WIFI. * 1x 5GHz wifi (MT7612) * 1x button. * 3x controllable LEDs. Works: * Wifi. * Switch. * mini-PCIe slot. Only tested with a USB device (a modem). * SIM slot. * Sysupgrade. * Button (reset). Not working: * The 5GHz WIFI LED is completely dead. I suspect the issue is the same as on other devices with Mediatek 5Ghz wifi-cards/chips. The LED is controlled by the driver, and mt76 (currently) does not support this. Not tested: * SD card reader. Notes: * The modem (labeled 3G/4G) and power LEDs are controlled by the hardware. * There is a 32MB version of this device available, but I do not have access to it. I have therefor only added support for the 16MB version, but added all the required infrastructure to make adding support for the 32MB version easy. Installation: The router comes pre-installed with OpenWRT, including a variant of Luci. The initial firmware install can be done through this UI, following normal procedure. I.e., access the UI and update the firmware using the sysupgrade-image. Remember to select that you do not want to keep existing settings. Recovery: If you brick the device, the WE1026-5G supports recovery using HTTP. Keep the reset button pressed for ~5sec when booting to start the web server. Set the address of the network interface on your machine to 192.168.1.2/24, and point your browser to 192.168.1.1 to access the recovery UI. From the recovery UI you can upload a firmware image. Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-29 12:56:10 +0000