aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
...
* mediatek: fix bootup problem on mt7629 EVBJohn Crispin2019-11-153-0/+728
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* ath79: fix sysupgrade from ar71xx for WNDR3700 V2 and WNDR3800(CH)Adrian Schmutzler2019-11-141-3/+3
| | | | | | | | | | | ar71xx has just one board name "wndr3700" for WNDR3700 V1/V2, WNDR3800 and WNDR3800CH, whereas ath79 provides separate images for the boards. So, update SUPPORTED_DEVICES to store the correct ar71xx board names. Fixes: FS#2510 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for Netgear WNDR3700v4Paul Blazejowski2019-11-145-0/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds ath79 support for Netgear WNDR3700v4. Router was previously supported by ar71xx target only. Note: device requires 'ar934x-nand' driver in kernel. Specification ============= * Description: Netgear WNDR3700v4 * Loader: U-boot * SOC: Atheros AR9344 (560 MHz) * RAM: 128 MiB * Flash: 128 MiB (NAND) - U-boot binary: 256 KiB - U-boot environment: 256 KiB - ART: 256 KiB - POT: 512 KiB - Language: 2 MiB - Config: 512 KiB - Traffic Meter: 3 MiB - Firmware: 25 MiB - ART Backup: 256 KiB - Reserved: 96 MiB * Ethernet: 5 x 10/100/1000 (4 x LAN, 1 x WAN) (AR8327) * Wireless: - 2.4 GHz b/g/n (internal) - 5 GHz a/n (AR9580) * USB: yes, 1 x USB 2.0 * Buttons: - Reset - WiFi (rfkill) - WPS * LEDs: - Power (amber/green) - WAN (amber/green) - WLAN 2G (green) - WLAN 5G (blue) - 4 x LAN (amber/green) - USB (green) - WPS (amber/green) * UART: 4-pin connector JP1, 3.3V (Vcc, TX, RX, GND), 115200 8N1 * Power supply: DC 12V 2.5A * MAC addresses: LAN=WLAN2G on case label, WAN +1, WLAN5G +2 Installation ============ * TFTP recovery * TFTP via U-boot prompt * sysupgrade * Web interface Note about partitioning: firmware partition offset (0x6c0000) is hardcoded into vendor's u-boot, so this partition cannot be moved and resized to include Netgear-specific flash areas (pot, language, config, traffic_meter) not used by OpenWrt. Test build configuration ======================== CONFIG_TARGET_ath79=y CONFIG_TARGET_ath79_nand=y CONFIG_TARGET_ath79_nand_DEVICE_netgear_wndr3700-v4=y CONFIG_ALL_KMODS=y CONFIG_DEVEL=y CONFIG_CCACHE=y CONFIG_COLLECT_KERNEL_DEBUG=y CONFIG_IMAGEOPT=y Signed-off-by: Paul Blazejowski <paulb@blazebox.homeip.net>
* ath79: split dts file for Netgear WNDR4300Michal Cieslakiewicz2019-11-142-285/+291
| | | | | | | Move board configuration to dtsi file in preparation for WNDR3700v4 router support. Signed-off-by: Michal Cieslakiewicz <michal.cieslakiewicz@wp.pl>
* ath79: fix indent in TP-Link TL-WDR4900 v2 DTSAdrian Schmutzler2019-11-141-1/+1
| | | | Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: improve common DTSI name for TP-Link Archer C5, C7 v1/v2Adrian Schmutzler2019-11-144-3/+3
| | | | | | | | As the former qca9558_tplink_archer-c7.dtsi is also used for Archer C5 v1 this patch removes the number from the DTSI name to indicate that. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: remove obsolete OF PCI related config symbolsPetr Štetiar2019-11-141-3/+0
| | | | | | | | | | | | Those symbols were removed in kernel 4.16: commit 4670d610d59233b017a6ea1fa25bbf06dabbff42 Author: Rob Herring <robh@kernel.org> PCI: Move OF-related PCI functions into PCI core Fixes: FS#2588 Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: include rssileds package for ubnt devices with LEDsRoger Pueyo Centelles2019-11-141-3/+8
| | | | | | | | | | | | | Some Ubiquiti devices had the RSSI LEDs configured in 01_leds but were missing the rssileds package, while others that don't have RSSI LEDS had the package included. This commit includes the rssileds package only for those devices that need it. Tested on a NanoStation M XW. Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
* ath79: GL-AR750S: provide NAND support; increase kernel to 4 MBJeff Kletsky2019-11-1410-56/+146
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The GL.iNet GL-AR750S has been supported by the ar71xx and ath79 platforms with access to its 16 MB NOR flash, but not its 128 MB SPI NAND flash. This commit provides support for the NAND through the upstream SPI-NAND framework. At this time, the OEM U-Boot appears to only support loading the kernel from NOR. This configuration is preserved as this time, with the glinet,gl-ar750s-nand name reserved for a potential, future, NAND-only boot. The family of GL-AR750S devices on the ath79 platform now includes: * glinet,gl-ar750m-nor-nand "nand" target * glinet,gl-ar750m-nor "nand" target (NAND-aware) NB: This commit increases the kernel size from 2 MB to 4 MB "Force-less" sysupgrade is presently supported from the current versions of following NOR-based firmwre images to the version of glinet,gl-ar750s-nor firmware produced by this commit: * glinet,gl-ar750s -- OpenWrt 19.07 ar71xx * glinet,gl-ar750s -- OpenWrt 19.07 ath79 Users who have sucessfully upgraded to glinet,gl-ar750m-nor may then flash glinet,gl-ar750m-nor-nand with sysupgrade to transtion to the NAND-based variant. Other upgrades to these images, including directly to the NAND-based glinet,gl-ar750s-nor-nand firmware, can be accomplished through U-Boot. NB: See "ath79: restrict GL-AR750S kernel build-size to 2 MB" which enables flashing of NAND factory.img with the current GL-iNet U-Boot, "U-Boot 1.1.4-gcf378d80-dirty (Aug 16 2018 - 07:51:15)" The GL-AR750S OEM U-Boot allows upload and flashing of either NOR firmware (sysupgrade.bin) or NAND firmware (factory.img) through its HTTP-based GUI. Serial connectivity is not required. The glinet,gl-ar750s-nor and glinet,gl-ar750s-nor-nand images generated after this commit flash each other directly. This commit changes the control of the USB VBUS to gpio-hog from regulator-fixed introduced by commit 0f6b944c92. This reduces the compressed kernel size by ~14 kB, with no apparent loss of functionality. No other ath79-nand boards are using regulator-fixed at this time. Note: mtd_get_mac_binary art 0x5006 does not return the proper MAC and the GL.iNet source indicates that only the 0x0 offset is valid The ar71xx targets are unmodified. Cc: Alexander Wördekemper <alexwoerde@web.de> Signed-off-by: Jeff Kletsky <git-commits@allycomm.com>
* ath79: add GL.iNet GL-AR300M16 as NOR-only boardJeff Kletsky2019-11-143-0/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The GL.iNet GL-AR300M series of devices includes variants without NAND and only the 16 MB NOR flash. These include the GL-AR300M16 and the GL-AR300M-Lite (already with its own board name). This board-name addition provides disambiguation from the NAND-bearing GL-AR300M devices, both for OpenWrt code and for end users. Kernel and firmware support for NAND and UBI will add ~320 kB to the overall firmware size at this time. This NOR-only option continues to provide more compact firmware for both the GL-AR300M16 as well as those who wish to use it as an alternate or primary, NOR-resident firmware on the GL-AR300M. The ar71xx targets are unmodified. Installation ------------ Install through OEM U-Boot (HTTP-based) or `sysupgrade --force` when booted from NOR and running OEM or OpenWrt, NOR-based firmware. As one of the intentions is disambiguation from NAND-bearing units, users who have flashed this firmware onto a device with NAND would need to use U-Boot or `sysupgrade --force` to flash firmware that again supports NAND. There are no additional SUPPORTED_DEVICES as it is not possible to determine if a device does or does not have NAND based on either the OEM's or OpenWrt's board names prior to this patch. Signed-off-by: Jeff Kletsky <git-commits@allycomm.com>
* ath79: GL-AR300M: provide NAND support; increase to 4 MB kernelJeff Kletsky2019-11-1411-54/+181
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The GL.iNet GL-AR300M has been supported by the ar71xx and ath79 platforms with access to its 16 MB NOR flash, but not its 128 MB SPI NAND flash. This commit provides support for the NAND through the upstream SPI-NAND framework. Devices with both NOR and NAND flash can support independent firmware on each, with U-Boot able to boot from either. The OEM U-Boot will fall back to the NOR firmware after three "unsuccessful" boots. The family of GL-AR300M devices on the ath79 platform now includes: * glinet,gl-ar300m-lite "generic" target, NOR-only board * glinet,gl-ar300m-nand "nand" target * glinet,gl-ar300m-nor "nand" target (NAND-aware) NB: This commit increases the kernel size from 2 MB to 4 MB "Force-less" sysupgrade is presently supported from the current versions of following NOR-based firmwre images to the version of glinet,gl-ar300m-nor firmware produced by this commit: * gl-ar300m -- OEM v3 NOR ar71xx (openwrt-ar300m16-*.bin) * gl-ar300m -- OpenWrt 18.06 ar71xx * gl-ar300m -- OpenWrt 19.07 ar71xx Other upgrades to these images should be performed through U-Boot. The GL-AR300M OEM U-Boot allows upload and flashing of either NOR firmware (sysupgrade.bin) or NAND firmware (factory.img) through its HTTP-based GUI. Serial connectivity is not required. The glinet,gl-ar300m-nand and glinet,gl-ar300m-nor images generated after this commit should safely flash each other using sysupgrade. The boot counter is implemented by the OEM using u-boot-env. At this time, it does not appear that the switch on the side of the unit can be used to select NOR vs. NAND boot and the fail-over is only from NAND to NOR. To save flash wear, it is only reset when running the glinet,gl-ar300m-nand firmware. NAND-specific base-files are used to remove impact on existing generic and tiny targets. As there is now no "generic" build appropriate for the GL-AR300M16, (or for users of the GL-AR300M that do not need access to NAND) it will be introduced in a subsequent commit. Note: `mtd_get_mac_binary art 0x6` does not return the proper MAC and the GL.iNet source indicates that only the 0x0 offset is valid The ar71xx targets are unmodified. Signed-off-by: Jeff Kletsky <git-commits@allycomm.com>
* ath79: prepare NAND subtarget for upstream support of SPI NANDJeff Kletsky2019-11-142-11/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | Linux 4.19 supplies the upstream spi-nand framework, permitting porting and support of boards with SPI NAND. * Adjusted nand/target.mk to provide FEATURES += squashfs nand * Updated config-default to provide current MTD and UBI support Defaults selected for: CONFIG_MTD_UBI_WL_THRESHOLD=4096 CONFIG_MTD_UBI_BEB_LIMIT=20 # CONFIG_MTD_UBI_FASTMAP is not set # CONFIG_MTD_UBI_GLUEBI is not set The bad-block reservation limit technically should be 21 for Paragon SPI NAND but most other devices in the class are 20 blocks per Gbit. In Linux 5.2 this is specified on a per-chip basis through NAND_MEMORG Contents adjusted to remove declarations provided at the target level by commit 08a134820f5 (Oct 23, 2019) ath79: enable PCI for whole target Signed-off-by: Jeff Kletsky <git-commits@allycomm.com> Tested-by: Michal Cieslakiewicz <michal.cieslakiewicz@wp.pl>
* ramips: add support for ALFA Network Quad-E4GPiotr Dymacz2019-11-146-11/+276
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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/100 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) 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>
* ramips: mt7621: refresh kernel configPiotr Dymacz2019-11-141-2/+2
| | | | Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ramips: provide label MAC for ALFA Network Tube-E4GPiotr Dymacz2019-11-141-0/+1
| | | | Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ramips: add support for ALFA Network R36M-E4GPiotr Dymacz2019-11-136-8/+244
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* ramips: support dual image feature on ALFA Network boardsPiotr Dymacz2019-11-134-0/+48
| | | | | | | | | | | | | | | | | | | | | | | | | 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>
* ramips: add usb-ledtrig-usbport to DEVICE_PACKAGES of CY-SWR1100Sungbo Eo2019-11-131-1/+1
| | | | | | | | | CY-SWR1100 has a USB LED but kmod-usb-ledtrig-usbport is missing in default images. This commit adds it. Signed-off-by: Sungbo Eo <mans0n@gorani.run> [changed commit title] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: change status LED of Samsung CY-SWR1100Sungbo Eo2019-11-131-4/+6
| | | | | | Use power LED for status indication and free WPS LED for other uses. Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* ramips: improve Samsung CY-SWR1100 supportSungbo Eo2019-11-132-5/+10
| | | | | | | | | | | | | | | | | | | | | | This patch does the following: - rename "devdata" flash partition and make it read-only - switch from gpio-keys-polled to gpio-keys - add missing power LED - set correct PCI ID to compatible string in wifi node - remove ralink,5ghz property in wifi node - provide label MAC address Rename devdata partition to devconf as indicated in the stock firmware partition table: 00030000-00040000: "devdata" 00040000-00050000: "devconf" Power LED can be controlled by SoC GPIO. Add it in the dts leds node. RT3092L supports only bgn mode, so it is unnecessary to disable 5GHz band. Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* ramips: fix MAC address setup for Samsung CY-SWR1100Sungbo Eo2019-11-131-1/+2
| | | | | | | | | Ethernet MAC address setup has been broken since c3e420f28cf1. Restore original setting. Fixes: c3e420f28cf1 ("ramips: Add support for D-Link DCH-M225") Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* ar71xx: fix MAC addresses for Archer C5 v1, C7 v1/v2, WDR4900 v2Adrian Schmutzler2019-11-132-3/+2
| | | | | | | | | | | | | | | | | | | As discussed in 1d18a14a90c7 ("ath79: really fix TP-Link Archer C7 v2 MAC address"), stock firmware MAC address assignment is actually as follows: wlan0 (5GHz) : -1 wlan1 (2.4GHz) : 0 eth1 (LAN) : 0 eth0 (WAN) : 1 This has never been fixed for ar71xx, so let's do it now. Note that with WDR4900 v2 even both wlan0 and wlan1 where assigned to basemac-1 before ... Fixes: FS#408 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: read label MAC address from flash instead of using phy0/phy1Adrian Schmutzler2019-11-131-2/+2
| | | | | | | | | | | | | | | | | | | | | This replaces all uses of $(cat /sys/class/ieee80211/phyX/macaddress) by retrieval from the proper flash locations. This will make 02_network independent of WiFi setup again. For future reference: The MAC addresses of the FRITZ!WLAN Repeater 300E can be extracted from the urlader key value store: maca *:6B macb *:6C macwlan *:6D macdsl *:6E and be set by e.g. addr=$(fritz_tffs -n maca -i $(find_mtd_part "tffs (1)")) Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: read label MAC address from flash instead of using phy0/phy1Adrian Schmutzler2019-11-134-11/+14
| | | | | | | | This replaces all uses of $(cat /sys/class/ieee80211/phyX/macaddress) by retrieval from the proper flash locations. This will make 02_network independent of WiFi setup again. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: bump 4.19 to 4.19.82Koen Vandeputte2019-11-1212-258/+45
| | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 950-0295-sc16is7xx-Fix-for-Unexpected-interrupt-8.patch Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.152Koen Vandeputte2019-11-122-9/+8
| | | | | | | | | | | | Refreshed all patches. Altered patches: - 301-arch-support-layerscape.patch Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.199Koen Vandeputte2019-11-121-1/+1
| | | | | | | | | Refreshed all patches. Compile-tested on: none Runtime-tested on: none Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ath79: fix SUPPORTED_DEVICES for TP-Link TL-WR1043ND v3Adrian Schmutzler2019-11-111-1/+1
| | | | | | | | | In ar71xx, the board name for the TL-WR1043ND v3 is equal to v2: tl-wr1043nd-v2 Fix SUPPORTED_DEVICES for v3 in ath79 accordingly. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: remove redundant WiFi LED on FRITZ!Box 7320Manuel Kock2019-11-111-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>
* x86,tegra,mvebu: image: use common reproducible IMG_PART_SIGNATUREPaul Spooren2019-11-113-12/+7
| | | | | | | | | | | | | These targets are currently using more or less same SIGNATURE variable which provides unique partition ID/signature, so it makes sense to refactor it out into common IMG_PART_SIGNATURE variable which could be reused by all targets. This is another step in the direction of reproducible OpenWrt images. Signed-off-by: Paul Spooren <mail@aparcar.org> [split into separate commit, renamed to IMG_PART_SIGNATURE] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: split further base-files across subtargetsAdrian Schmutzler2019-11-116-21/+68
| | | | | | | | | | | As started in 19724e28c81e ("ramips: split base-files into subtargets"), this moves some smaller left-over files to the appropriate base-files folder of their subtarget: - /etc/init.d/bootcount - /etc/uci-defaults/04_led_migration Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: fix identifier for Nanostation M in ath9k caldata extractionAdrian Schmutzler2019-11-111-1/+1
| | | | | | | | When Nanostation M was renamed from ubnt,nano-m to ubnt,nanostation-m in commit f1396ac753cc ("ath79: align naming of Ubiquiti Nanostation M"), the caldata extraction in 10-ath9k-eeprom was overlooked. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: correct Netgear WNDR3700v5 button flagDavid Bauer2019-11-101-3/+3
| | | | | | | | | This adjusts the GPIO state flag to ACTIVE_LOW as FCC pictures indicate the base board is identical to the one of the R6220. Fixes commit 3459013257e0 ("ramips: correct R6220 button flag") Signed-off-by: David Bauer <mail@david-bauer.net>
* ramips: correct R6220 button flagDavid Bauer2019-11-091-3/+3
| | | | | | | | | | | | | | All buttons on the Netgear R6220 are active-low while they are flagged as active-high. The GPIO status reads the following for no buttons pressed: root@64367-r6220:~# cat /sys/kernel/debug/gpio gpio-7 ( |wps ) in hi gpio-8 ( |wifi ) in hi gpio-14 ( |reset ) in hi Signed-off-by: David Bauer <mail@david-bauer.net>
* brcm63xx: add linux 4.19 supportÁlvaro Fernández Rojas2019-11-09181-1/+22307
| | | | | | | | | Boot tested on Comtrend AR-5387un: https://gist.github.com/Noltari/57e5030455da8dc38e61f8c3a5922254 Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> [jonas.gorski: make 4.19 an optional testing version; add gcc 8.3 fix] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* mxs: start a console on USB gadget serial portsMichael Heimpold2019-11-091-0/+1
| | | | | | | | | | | | The I2SE Duckbill devices are pen-drive like and thus the usage of the USB gadget subsystem is highly indicated. Spawning a console if a serial gadget is configured saves us from connecting a physical debug uart. On Olimex OLinuXino Maxi/Mini boards, this does not hurt. Signed-off-by: Michael Heimpold <mhei@heimpold.de>
* mxs: switch to askconsoleMichael Heimpold2019-11-091-1/+1
| | | | | | | Remove the dedicated tty name and use askconsole to spawn the console on serial debug uart. Signed-off-by: Michael Heimpold <mhei@heimpold.de>
* mxs: add support and switch to kernel 4.19Michael Heimpold2019-11-093-76/+19
| | | | | | | | | | Also remove kernel 4.14 support and the meanwhile obsolete patch. This was run-tested on I2SE Duckbill device and Olimex OLinuXino Maxi board. Signed-off-by: Michael Heimpold <mhei@heimpold.de> Tested-by: Zoltan HERPAI <wigyori@uid0.hu>
* ramips: create shared DTSI for Netgear EX2700 and WN3000RP v3Adrian Schmutzler2019-11-083-162/+104
| | | | | | | | | This moves shared code of the named devices into a common DTSI. Remove setting status="okay" for &gpio0 as it's not disabled in mt7620a.dtsi. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: increase max SPI frequency to 50 MHz for EX3700/EX6130Frederik Noe-Sdun2019-11-081-1/+1
| | | | | | | | | Based on Macronix MX25L3205DM2I datasheet this is maximum supported speed. Signed-off-by: Frederik Noe-Sdun <Frederik.Sdun@googlemail.com> [rebased, improved commit title/message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: add support for Netgear EX6130Frederik Noe-Sdun2019-11-086-114/+189
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Specifications: * SoC: MT7620A * RAM: 64 MB DDR * Flash: 8MB NOR SPI flash * WiFi: MT7612E (5Ghz) and builtin MT7620A (2.4GHz) * LAN: 1x100M The -factory images can be flashed from the device's web interface or via nmrpflash. The device seems to use base PCB as EX3700/EX3800, but supporting AC1200 using MT7612E. MAC adresses: 5.0 GHz 0x8004 *:9a 2.4 GHz 0x4 *:9b lan 0x28 *:9b wan 0x2e *:9c Since this is a one-port device, although wan MAC address is set in flash, it is not used in OpenWrt setup. Signed-off-by: Frederik Noe-Sdun <Frederik.Sdun@googlemail.com> [rebased, extended commit message, tiny DTS style fixes] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ar71xx: fix tl-wdr3320-v2 upgrade南浦月2019-11-081-1/+1
| | | | | | | | | Fix the error that tl-wdr3320-v2 can't upgrade firmware via web interface by using magic_ver="0200" for this device. Signed-off-by: 南浦月 <nanpuyue@gmail.com> [commit message facelift] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ipq40xx: u4019: use reset-gpios instead of phy-reset-gpioKristian Evensen2019-11-071-1/+2
| | | | | | | | Use reset-gpio instead of the custom phy-reset-gpio property to do phy reset on the U4019. phy-reset-gpio was incorrectly introduced when we added support for the U4019, and will be deprecated. Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
* ipq40xx: wpj419: use reset-gpios property for phy resetDaniel Danzberger2019-11-071-1/+2
| | | | | | | The old GPIO based phy reset (phy-reset-gpio) will be removed form the ipq40xx mdio driver in the future. Signed-off-by: Daniel Danzberger <daniel@dd-wrt.com>
* ipq40xx: mdio: remove support for phy-reset-gpioDENG Qingfang2019-11-071-65/+2
| | | | | | | | | | | | | Commit 6f6c00cfc95f ("ipq40xx: Add support for Unielec U4019") has introduced support for `phy-reset-gpio` DT property, which isn't needed as the MDIO already supports `reset-gpios`[1] which could be used instead. 1. https://elixir.bootlin.com/linux/v4.19.81/source/Documentation/devicetree/bindings/net/mdio.txt Ref: PR#2511 Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn> [commit title and description facelift] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: rename keys node formerly named buttonAdrian Schmutzler2019-11-073-3/+3
| | | | | | | For some devices, the keys node is named "button". Change name to match the rest of the target. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: replace generic button node namesAdrian Schmutzler2019-11-0718-30/+30
| | | | | | | | | | In several DTS files, button nodes are just named buttonX or xxx_button. This replaces the names with more specific names matching the majority of key definitions. While at it, fix name of keys node in one case. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: fix LED netdev trigger on interface renameMartin Schiller2019-11-072-0/+108
| | | | | | | | | This fixes the netdev LED trigger for interfaces, which are renamed during initialization (e.g. ppp interfaces). Fixes: FS#2193 Fixes: FS#2239 Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* ramips, mt7620: reproducible elecom-header uid/gidPaul Spooren2019-11-061-1/+1
| | | | | | | | | | | | | | | | | | | | | The elecom-header renames the firmware image to v_0.0.0.bin, stores its MD5 sum as v_0.0.0.md5 and tars both files again. Both v_0.0.0 files are created as the build user making it harder to reproduce. This commit sets the owner/group of both files to root by adding extra options to the final tar command. Before: 0 buildbot (101) buildbot (102) 3932164 2019-11-05 14:43:22.000000 v_0.0.0.bin 0 buildbot (101) buildbot (102) 33 2019-11-05 14:43:22.000000 v_0.0.0.md5 After: 0 root (0) root (0) 3932164 2019-11-05 23:43:08.000000 v_0.0.0.bin 0 root (0) root (0) 33 2019-11-05 23:43:08.000000 v_0.0.0.md5 Signed-off-by: Paul Spooren <mail@aparcar.org>
* ath79: specify N and ND subversions of TL-WR941 with ALT0_MODELAdrian Schmutzler2019-11-061-2/+8
| | | | | | | | | | | | | | | | | | TP-Link's TL-WR941 is sold with detachable antennas internationally (ND version), but with fixed antennas in China (N version). While hardware and images are similar for both variants of v2 and v4, they are different for v6. Having both explicitly will make it easier for user to identify the correct image, and most importantly will raise awareness that N and ND are not necessarily always the same as for TL-WR841 series. With an image selection webpage, using ALT0_MODEL as in this patch will provide the option to list versions for N and ND separately. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>