aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* kernel: bump 5.4 to 5.4.74John Audia2020-11-0210-124/+18
| | | | | | | | | | | | | | | | | | | Removed upstreamed patches: mvebu/patches-5.4 409-phy-marvell-comphy-Convert-internal-SMCC-firmware-re.patch All modifications made by update_kernel.sh Build system: x86_64 Build-tested: ipq806x/R7800, ath79/generic, bcm27xx/bcm2711, x86_64 Run-tested: ipq806x/R7800, x86_64, lantiq/Easybox 904 xDSL No dmesg regressions, everything functional Signed-off-by: John Audia <graysky@archlinux.us> Tested-by: Curtis Deptuck <curtdept@me.com> [x86_64 build/run] [added lantiq test report] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* x86: fix touching bootloader "upgraded" markYousong Zhou2020-11-021-1/+1
| | | | | | | | | | | | | | The mount point is "/tmp/boot", the path in the boot partition is "/boot/grub/upgraded". Origin of this mark b9c1cf16 ("x86: add preinit hook for bootloader upgrade") Fixes 32f675ca ("x86: fix grub-bios-setup fail during sysupgrade") Ref: https://bugs.openwrt.org/index.php?do=details&task_id=3140 Reported-by: Philip Prindeville <philipp@redfish-solutions.com> Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* sdk: fix missing include directoriesPetr Štetiar2020-11-021-1/+6
| | | | | | | | | | | | | It's not possible to compile some applications which are using `-Werror=missing-include-dirs` compiler flags with the SDK as some target directories are missing in the SDK tarball: cc1: error: staging_dir/target/usr/include: No such file or directory [-Werror=missing-include-dirs] cc1: error: staging_dir/target/include: No such file or directory [-Werror=missing-include-dirs] Fix this by adding the missing directories in the SDK. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ipq40xx: enable RX hash / CTAG TX offloading for single-phyDavid Bauer2020-11-011-0/+9
| | | | | | | | | | | | This re-enables offloading features disabled by commit 9da2b567605b ("ipq40xx: fix ethernet vlan double tagging"). Single-PHY devices use port-based VLANs on the switch, therefore no S-TAG magic is involved here. Re-enabling these features restores throughput back to 950 Mbit/s. Reported-by: Jannis Pinter <jannis@pinterjann.is> Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: use correct firmware name for UniFi APDavid Bauer2020-11-011-3/+3
| | | | | | | | | The Ubiquiti UniFi AP does not have a AHB connected radio but a PCI one. Also the EEPROM ist only 0x440 bytes of length. Reported-by: Martin Weinelt <martin@darmstadt.freifunk.net> Tested-by: Martin Weinelt <martin@darmstadt.freifunk.net> Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: remove AT803X config symbol from subtargetsDavid Bauer2020-11-012-2/+0
| | | | | | | The AT803X_PHY kernel config symbol is already enabled target-wide. SO it does not have to be enabled for individual subtargets. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: drop upstreamed patchDavid Bauer2020-11-011-24/+0
| | | | | | | | | | | Patch was upstreamed a long time ago (over 2 years) as commit a08227a206b8d ("MIPS: ath79: select the PINCTRL subsystem"). When porting this patch to a newer kernel, nobody noticed we now patch a Broadcom platform. This is clearly not intended. So drop this patch and pretend nothing ever happened. Signed-off-by: David Bauer <mail@david-bauer.net>
* kernel: bump 5.4 to 5.4.73John Audia2020-11-01114-405/+224
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Removed upstreamed patches: generic/pending-5.4 445-mtd-spinand-gigadevice-Only-one-dummy-byte-in-QUA.patch 446-mtd-spinand-gigadevice-Add-QE-Bit.patch pistachio/patches-5.4 150-pwm-img-Fix-null-pointer-access-in-probe.patch Manually rebased: layerscape/patches-5.4 801-audio-0011-Revert-ASoC-fsl_sai-add-of_match-data.patch 801-audio-0039-MLK-16224-6-ASoC-fsl_sai-fix-DSD-suspend-resume.patch 801-audio-0073-MLK-21957-3-ASoC-fsl_sai-add-bitcount-and-timestamp-.patch 820-usb-0009-usb-dwc3-Add-workaround-for-host-mode-VBUS-glitch-wh.patch All modifications made by update_kernel.sh Build system: x86_64 Build-tested: ipq806x/R7800, ath79/generic, bcm27xx/bcm2711, mvebu (mamba, rango), x86_64, ramips/mt7621 Run-tested: ipq806x/R7800, mvebu (mamba, rango), x86_64, ramips (RT-AC57U) No dmesg regressions, everything functional Signed-off-by: John Audia <graysky@archlinux.us> [alter 820-usb-0009-usb-dwc3-Add-workaround-for-host-mode-VBUS-glitch-wh] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* target: remove obsolete kernel version switches for 4.19Adrian Schmutzler2020-10-3010-272/+2
| | | | | | | This removes unneeded kernel version switches from the targets after kernel 4.19 has been dropped. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: remove support for kernel 4.19Adrian Schmutzler2020-10-30526-104563/+0
| | | | | | | We use 5.4 on all targets by default, and 4.19 has never been released in a stable version. There is no reason to keep it. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* octeon: disable edgerouter imageJohannes Kimmel2020-10-301-0/+1
| | | | | | | | | | | | | | | | | | | | | | This patch disables the image for edgerouter devices by default, since it isn't able to boot at the moment. Currently the edgerouter image won't boot. Current kernels have an option CONFIG_CAVIUM_CN63XXP1 that needs to be enabled for this chip. If the kernel was compiled without this option, following message is displayed and the machine reboots: [ 36.778028] Kernel panic - not syncing: OCTEON II DCache prefetch workaround not in place (cfa0000c). [ 36.778028] Please build kernel with proper options (CONFIG_CAVIUM_CN63XXP1). [ 36.794398] Rebooting in 1 seconds.. This was last confirmed on 2020-10-29. The description of this option states, that enabling it will possibly cause performance issues on other chips. Signed-off-by: Johannes Kimmel <fff@bareminimum.eu>
* kernel: move kmod-i2c-bcm-iproc to I2C menuDaniel Golle2020-10-301-1/+1
| | | | | | | | A typo resulted in that module having it's own menu. Move it into the I2C menu as it was most likely intended. Fixes: 1291274335 ("kernel: package bcm53xx i2c module") Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* build,IB: reload packages/ only if existingPaul Spooren2020-10-301-1/+4
| | | | | | | | | | | With the fix of external kmod feeds it is possible to ship the ImageBuilder without any packages except the pseudo packages kernel and libc. Therefore the local package feeds becomes optional. This commit adds a check to the package_reload function to only run if the local feed is existing. Signed-off-by: Paul Spooren <mail@aparcar.org>
* build,IB: include kmods only in local buildsPaul Spooren2020-10-302-12/+16
| | | | | | | | | | The buildbots generate a kmod archive which should be used instead of a local copy. This is possible due to the introduction of a kernelversion specific feed. This commit adds the ability of using only signed package feeds. Signed-off-by: Paul Spooren <mail@aparcar.org>
* ath79: mikrotik: use vmlinuz (zBoot ELF)John Thomson2020-10-292-3/+5
| | | | | | | | | | | - minimal built initramfs: 10MB vmlinux ELF -> 6MB vmlinuz - ~5 seconds for kernel decompression, which was equivalent to the additional time to load the uncompressed ELF from SPI NOR. - Removes requirement for lzma-loader, which may have been causing some image builds to fail to boot on Mikrotik mt7621. Suggested-by: Thibaut VARÈNE <hacks@slashdirt.org> Signed-off-by: John Thomson <git@johnthomson.fastmail.com.au>
* mt7621: mikrotik: use vmlinuz (zBoot ELF)John Thomson2020-10-292-2/+5
| | | | | | | | | | | | - minimal built initramfs: 11MB vmlinux ELF -> 4.5MB vmlinuz - ~5 seconds for kernel decompression, which was equivalent to the additional time to load the uncompressed ELF from SPI NOR. - Removes requirement for lzma-loader, which may have been causing some image builds to fail to boot on Mikrotik mt7621. Fixes: FS#3354 Suggested-by: Thibaut VARÈNE <hacks@slashdirt.org> Signed-off-by: John Thomson <git@johnthomson.fastmail.com.au>
* kernel: mips: zboot: put appended dtb into a sectionChuanhong Guo2020-10-291-0/+36
| | | | | | | | | | | | This will make a separated section for dtb appear in ELF, and we can then use objcopy to patch a dtb into vmlinuz when RAW_APPENDED_DTB is set in kernel config. command to patch a dtb: objcopy --set-section-flags=.appended_dtb=alloc,contents \ --update-section=.appended_dtb=<target>.dtb vmlinuz vmlinuz-dtb Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* ramips: add linux zboot supportChuanhong Guo2020-10-291-0/+26
| | | | | | | | linux-mips has zboot code which can create a self-extracting kernel image. This allows enabling kernel zboot support for ramips targets. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* ramips: add support for Wavlink WL-WN530HG4Nuno Goncalves2020-10-273-2/+151
| | | | | | | | | | | | | | | | | | | | | | | | | | Same hardware as Phicomm K2G but different flash layout. Specification: - SoC: MediaTek MT7620A - Flash: 8 MB - RAM: 64 MB - Ethernet: 4 FE ports and 1 GE port (RTL8211F on port 5) - Wireless radio: MT7620 for 2.4G and MT7612E for 5G, both equipped with external PA. - UART: 1 x UART on PCB - 57600 8N1 Flash instruction: To avoid requiring UART for TFTP a dual flash procedure is suggested to install the squashfs image: 1. Rename openwrt-ramips-mt7620-wavlink_wl-wn530hg4-initramfs-kernel.bin to WN530HG4-WAVLINK. 2. Flash this file with the factory web interface. 3. With OpenWRT now running use standard sysupgrade to install the squashfs image. Signed-off-by: Nuno Goncalves <nunojpg@gmail.com> [remove dts-v1, remove model from LED labels, wrap commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* malta: relocate CPU_TYPE setting to subtarget makefilesTony Ambardar2020-10-273-1/+2
| | | | | | | Move CPU_TYPE:=24kc (32-bit) from the top-level target makefile to the be/le subtarget makefiles, which is consistent with the 64-bit subtargets. Signed-off-by: Tony Ambardar <itugrok@yahoo.com>
* lantiq: add support for AVM FRITZ!Box 7430Leon Maurice Adam2020-10-275-3/+294
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware: - SoC: Lantiq VRX 220 - CPU: 2x MIPS 34Kc 500 MHz - RAM: 128 MiB 250 MHz - Flash: 128 MiB NAND - Ethernet: Built-in Fast Ethernet switch, 4 ports used - Wifi: Atheros AR9381-AL1A b/g/n with 2 pcb/internal and 1 external antennas - USB: 1x USB 2.0 - DSL: Built-in A/VDSL2 modem - DECT: Dialog SC14441 - LEDs: 1 two-color, 4 one-color - Buttons: 1x DECT, 1x WIFI - Telephone connectors: 1 FXS port via TAE or RJ11 connector With the exception of FXS/DECT everything works (there are no drivers for AVM's FXS or DECT implementation), DSL is yet untested. Installation: Boot up the device and wait a few seconds. Run the eva_ramboot.py script in scripts/flashing/ to load the initramfs image on the device: $ ./scripts/flashing/eva_ramboot.py 192.168.178.1 <path to your initramfs image> If the script fails to reach the device, maybe try 169.254.120.1. Wait until booting is complete. You should now be able to reach your device under the default ip address 192.168.1.1. Before flashing, check if linux_fs_start is not set to 1 in the tffs partition: $ fritz_tffs_nand -d /dev/mtd1 -n linux_fs_start If linux_fs_start is 1, you will need to reset it to 0, either by FTP, upgrading FritzOS or doing a recovery. Now you should be able to flash the device using sysupgrade. Signed-off-by: Leon Maurice Adam <leon.adam@aol.de> Acked-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl> [drop BOARD_NAME, use wpad-basic-wolfssl, drop 4.19, drop dts-v1, remove model prefix from LED names] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: fix indent in vr9_avm_fritz7412.dtsAdrian Schmutzler2020-10-271-1/+1
| | | | | | Indent should be tabs. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm63xx: reorganize board patches into fewer filesAdrian Schmutzler2020-10-2675-4067/+2730
| | | | | | | | | | | | | | | At the moment, bcm63xx creates one patch for each board to add to board_bcm963xx.c. While this is not really helpful to get an overview in the first place, it is particularly painful if you want to change something for an early file and have to refresh all the later patches accordingly. Since it does not look like these board patches are upstreamed either, this commit consolidates all board additions into one patch per "board". By this, both adding and editing boards should become much simpler, and we drop about 1300 lines of "code" from patches as well. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: enable upgrade from ar71xx for Qxwlan devicesAdrian Schmutzler2020-10-262-0/+14
| | | | | | | This supports upgrade from ar71xx for the recently added Qxwlan devices E1700AC v2, E558 v2, E750A v4 and E750G v8. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* octeon: use dedicated function to move config backupRoman Kuzmitskii2020-10-261-8/+14
| | | | | | | | | | | | | | All octeon devices use the same or a very similar way to backup and restore configuration. We expect to have more devices added and in order to stop repeating ourselves move the logic to a separate function. While at it, add a few checks. Signed-off-by: Roman Kuzmitskii <damex.pp@icloud.com> [commit message facelift] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* sdk: keep the linux package in the same subdir as in the main build systemFelix Fietkau2020-10-261-1/+4
| | | | | Fixes: 953435795d17 ("build: always build package/kernel/linux") Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ath79: fix block protection clearingNick Hainke2020-10-261-0/+28
| | | | | | | | | | | | | | | The block protection bits of macronix do not match the implementation. The chip has 3 BP bits. Bit 5 is actually the third BP but here the 5th bit is SR_TB. Therefore the patch adds SR_TB to the mask. In the 4.19er kernel the whole register was simply set to 0. The wrong implementation did not remove the block protection. This led to jffs2 errors in the form of: "jffs2: Newly-erased block contained word 0x19852003 at offset 0x..." This caused inconsistent memory and other errors. Suggested-by: David Bauer <mail@david-bauer.net> Signed-off-by: Nick Hainke <vincent@systemli.org>
* layerscape: several kernel fix-ups from NXP linux factoryYangbo Lu2020-10-263-0/+146
| | | | | | | | | | | | | NXP linux factory unifies one linux kernel for i.MX, Layerscape and S32 platforms. It provides a common code base for their SDKs. Add several kernel patches for bug fix from linux factory last release. Git: https://source.codeaurora.org/external/qoriq/qoriq-components/linux Tag: LTS-5.4.47-20200828 Signed-off-by: Biwen Li <biwen.li@nxp.com> Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update kernel to LSDK-20.04-V5.4-update-290520Biwen Li2020-10-262-0/+274
| | | | | | | | | | | Update kernel from LSDK-20.04-V5.4 to LSDK-20.04-V5.4-update-290520. Only two patches added for Layerscape. LSDK kernel link https://source.codeaurora.org/external/qoriq/qoriq-components/linux/ Signed-off-by: Biwen Li <biwen.li@nxp.com> Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: harmonize wrapping for IMAGE/* definitionsAdrian Schmutzler2020-10-262-3/+6
| | | | | | Always keep the first line empty for multi-line IMAGE/* definitions. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* layerscape: create shared definitions for sdboot devicesAdrian Schmutzler2020-10-262-24/+21
| | | | | | | This moves a few shared variables for SD-Boot devices into common definitions in order to reduce duplicate code. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* layerscape: Change to combined rootfs on sd imagesPawel Dembicki2020-10-2611-173/+149
| | | | | | | | | | | | | | | | | | At this moment layerscape images are ext4 only. It causes problem with save changes durring sysupgrade and make "firstboot" and failsafe mode useless. This patch changes sd-card images to squashfs + f2fs combined images. To make place, for saving config, kernel space ar now ext4 partition with fit kernel. This method of image generation is similar to rest of OpenWrt sd-card targets. Reviewed-by: Yangbo Lu <yangbo.lu@nxp.com> Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com> [reword README, reword DEVICE_COMPAT_MESSAGE, keep original indent] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* layerscape: fix platform_copy_config functionPawel Dembicki2020-10-261-3/+21
| | | | | | | | | | | | | | | | At this moment platform_copy_config function is used for every device and function "export_partdevice" without "export_bootdevice" causes multiple errors like that: "sh: 1: unknown operand" This patch fix usage of export_partdevice and split platform_copy_config for sd-card images. Fixes: 0841b68c91d3 ("layerscape: support sysupgrade for SD card ext4 rootfs") Reviewed-by: Yangbo Lu <yangbo.lu@nxp.com> Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* layerscape: add dtb to sysupgradePawel Dembicki2020-10-265-11/+59
| | | | | | | | | | | | | | | | | | | At this moment sysupgrade replaces only kernel and rootfs. This patch add dtb part to sysupgrade images to avoid situation when old dtb make system broken. Is possible to sysupgrade older images for NOR devices: 1. Firmware partition in bootargs need to be updated to: "49m@0xf00000(firmware)". Env should be saved after changes. 2. After step one, "sysupgrade -F" will work. Run tested: LS1046A-RDB Reviewed-by: Yangbo Lu <yangbo.lu@nxp.com> Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com> [bump PKG_RELEASE for uboot-layerscape] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* layerscape: fix sd-card sysupgradePawel Dembicki2020-10-261-2/+4
| | | | | | | | | | | | | | | So far, kernel has not been written correctly to SD card during sysupgrade, as both target path and offset were wrong. This patch fixes it, and adds some descriptive output on the way. Fixes: 0841b68c91d3 ("layerscape: support sysupgrade for SD card ext4 rootfs") Reviewed-by: Yangbo Lu <yangbo.lu@nxp.com> Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com> [alter/extend commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: define 2.4GHz radio for litebeam ac gen2Nick Hainke2020-10-251-0/+6
| | | | | | The litebeam ac gen2 has a 2.4GHz management radio. Signed-off-by: Nick Hainke <vincent@systemli.org>
* ath79: define 2.4GHz radio for nanostation ac locoNick Hainke2020-10-251-0/+6
| | | | | | The nanostation ac loco has a 2.4GHz management radio. Signed-off-by: Nick Hainke <vincent@systemli.org>
* ath79: fix nanostation ac loco ethernet interfaceNick Hainke2020-10-251-3/+2
| | | | | | | | | | | | In 4.14 the delays were not cleared, so setting "rgmii" as phy-mode did not affect delays set by the bootloader. With 5.4 kernel the situation changed and the ethernet interface stopped working. Just taking the ethernetpart from the litebeam ac gen2 will fix the issue. Explained-by: David Bauer <mail@david-bauer.net> Signed-off-by: Nick Hainke <vincent@systemli.org>
* ramips: mt7621: use lzma-loader for U7621-06Jianhui Zhao2020-10-251-0/+2
| | | | | | | The U7621-06 fails to boot if the kernel is large. Enabling lzma-loader resolves the issue. Signed-off-by: Jianhui Zhao <zhaojh329@gmail.com>
* ramips: add support for TOTOLINK X5000RChuanhong Guo2020-10-252-0/+149
| | | | | | | | | | | | | | | | | | | | | | Specifications: - SoC: MT7621AT - RAM: 256MB - Flash: 16MB (EN25QH128A) - Ethernet: 5xGbE - WiFi: MT7915 2x2 2.4G 573.5Mbps + 2x2 5G 1201Mbps Known issue: MT7915 DBDC variant isn't supported yet. Flash instruction: Upload the sysupgrade firmware to the firmware upgrade page in vendor fw. Other info: MT7915 seems to have two PCIEs connected to MT7621. Card detected on PCIE0 has an ID of 14c3:7916 and the other one on PCIE1 has 14c3:7915. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* generic: 5.4: make nf nat masquerade in unset state by defaultYousong Zhou2020-10-241-2/+1
| | | | | | | | | | | | | | Upstream linux 5.1 commit d1aca8ab ("netfilter: nat: merge ipv4 and ipv6 masquerade functionality") replaces the following 2 options - CONFIG_NF_NAT_MASQUERADE_IPV4 - CONFIG_NF_NAT_MASQUERADE_IPV6 with CONFIG_NF_NAT_MASQUERADE. The new option is one without prompt and will be selected by CONFIG_NETFILTER_XT_TARGET_MASQUERADE introduced still later in 5.2. Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* kernel: bump 5.4 to 5.4.72John Audia2020-10-202-7/+7
| | | | | | | | | | | | All modifications made by update_kernel.sh Build system: x86_64 Build-tested: ipq806x/R7800, ath79/generic, bcm27xx/bcm2711 Run-tested: ipq806x/R7800 No dmesg regressions, everything functional Signed-off-by: John Audia <graysky@archlinux.us>
* ramips: add support for TP-Link RE200 v4Richard Fröhning2020-10-204-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link RE200 v4 is a wireless range extender with Ethernet and 2.4G and 5G WiFi with internal antennas. It's based on MediaTek MT7628AN+MT7610EN like the v2/v3. Specifications -------------- - MediaTek MT7628AN (580 Mhz) - 64 MB of RAM - 8 MB of FLASH - 2T2R 2.4 GHz and 1T1R 5 GHz - 1x 10/100 Mbps Ethernet - 8x LED (GPIO-controlled), 2x button - UART connection holes on PCB (57600 8n1) There are 2.4G and 5G LEDs in red and green which are controlled separately. MAC addresses ------------- The MAC address assignment matches stock firmware, i.e.: LAN : *:8E 2.4G: *:8D 5G : *:8C MAC address assignment has been done according to the RE200 v2. The label MAC address matches the OpenWrt ethernet address. Installation ------------ Web Interface ------------- It is possible to upgrade to OpenWrt via the web interface. Simply flash the -factory.bin from OEM. In contrast to a stock firmware, this will not overwrite U-Boot. Recovery -------- Unfortunately, this devices does not offer a recovery mode or a tftp installation method. If the web interface upgrade fails, you have to open your device and attach serial console. Instructions for serial console and recovery may be checked out in commit 6d6f36ae787c ("ramips: add support for TP-Link RE200 v2") or on the device's Wiki page. Signed-off-by: Richard Fröhning <misanthropos@gmx.de> [removed empty line, fix commit message formatting] Signed-off-by: David Bauer <mail@david-bauer.net>
* lantiq: remove support for kernel 4.19Adrian Schmutzler2020-10-19197-27155/+0
| | | | | | | | | | | | | The target uses 5.4 as default kernel since 06/2020. Kernel 4.19 support is not really maintained anymore, it does not seem to be needed and upcoming changes (mainly DSA) will break backward-compatibility anyway. Thus, make maintaining of old stuff and reviewing of new stuff easier by removing support for kernel 4.19. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ipq806x: fix pci broken on bootm commandAnsuel Smith2020-10-191-0/+51
| | | | | | | | Pci is broken when bootm is used instead of the custom bootipq. This is caused by the lack of reset by the bootloader. Make the driver do the reset to fix this specific problem. Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: remove support for kernel 4.19Adrian Schmutzler2020-10-1993-16473/+0
| | | | | | | | | | | | | The target uses 5.4 as default kernel since 04/2020. Kernel 4.19 support is not really maintained anymore, and there has been a lot of changes between 4.19 and 5.4 on this target. Despite, new devices are typically added for 5.4 only anyway. Thus, make maintaining of old stuff and reviewing of new stuff easier by removing support for kernel 4.19. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ipq40xx: remove support for kernel 4.19Adrian Schmutzler2020-10-1952-12169/+0
| | | | | | | | | | The target uses 5.4 as default kernel since 03/2020. Kernel 4.19 support is not really maintained anymore, it does not seem to be needed, and removing it will make upcoming driver updates easier. Thus, remove it. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* rtl838x: various fixesJohn Crispin2020-10-194-0/+244
| | | | | | | | | * add d-link_dgs-1210-10p support * make sure mips16 is disabled * add a generic sub target * add proper cflags Signed-off-by: John Crispin <john@phrozen.org>
* sunxi: add support for FriendlyARM NanoPi R1Jayantajit Gogoi2020-10-184-0/+219
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Specification: - CPU: Allwinner H3, Quad-core Cortex-A7 Up to 1.2GHz - DDR3 RAM: 512MB/1GB - Network: 10/100/1000M Ethernet x 1， 10/100M Ethernet x 1 - WiFi: 802.11b/g/n, with SMA antenna interface - USB Host: Type-A x2 - MicroSD Slot x 1 - MicroUSB: for OTG and power input - Debug Serial Port: 3Pin 2.54mm pitch pin-header - LED: nanopi:red:status nanopi:green:wan nanopi:green:lan - KEY: reset - Power Supply: DC 5V/2A Installation: - Write the image to SD Card with dd - Boot NanoPi from the SD Card Signed-off-by: Jayantajit Gogoi <jayanta.gogoi525@gmail.com>
* ath79: add support for Qxwlan E1700AC v2张鹏2020-10-176-0/+214
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | E1700AC v2 based on Qualcomm/Atheros QCA9563 + QCA9880. Specification: - 750/400/250 MHz (CPU/DDR/AHB) - 128 MB of RAM (DDR2) - 8/16 MB of FLASH (SPI NOR) - 3T3R 2.4 GHz - 3T3R 5 GHz - 2 x 10/1000M Mbps Ethernet (RJ45) - 1 x MiniPCI-e - 1 x SIM (3G/4G) - 1 x USB 2.0 Port - 5 x LED , 2 x Button(S8-Reset Buttun), 1 x power input - UART (J5) header on PCB (115200 8N1) Flash instruction: 1.Using tftp mode with UART connection and original LEDE image - Configure PC with static IP 192.168.1.10 and tftp server. - Rename "openwrt-ar71xx-generic-xxx-squashfs-sysupgrade.bin" to "firmware.bin" and place it in tftp server directory. - Connect PC with one of LAN ports, power up the router and press key "Enter" to access U-Boot CLI. - Use the following commands to update the device to LEDE: run lfw - After that the device will reboot and boot to LEDE. - Wait until all LEDs stops flashing and use the router. 2.Using httpd mode with Web UI connection and original LEDE image - Configure PC with static IP 192.168.1.xxx(2-255) 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 leds flashing. - Open your browser and enter 192.168.1.1,You will see the upgrade interface, select "openwrt-ar71xx-generic-xxx-squashfs- sysupgrade.bin" and click the upgrade button. - After that the device will reboot and boot to LEDE. - Wait until all LEDs stops flashing and use the router. Signed-off-by: 张鹏 <sd20@qxwlan.com> [cut out of bigger patch, keep swconfig, whitespace fixes] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-04 04:00:14 +0000