aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* ramips: support dual image feature on ALFA Network boardsPiotr Dymacz2019-11-242-3/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | 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> (backported from commit bc173ddd8381b03dde8cc2e6c66d0cd392c62bbd)
* ramips: refresh all subtargets kernel configsPiotr Dymacz2019-11-246-5/+40
| | | | Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ramips: use upstream RAW_APPENDED_DTB instead of our OWRTDTBChuanhong Guo2019-11-249-86/+15
| | | | | | | | | | | | | | | | | | | Upstream kernel added support for RAW_APPENDED_DTB on ralink arch in the following commit: 02564fc89d3d ("ralink: Introduce fw_passed_dtb to arch/mips/ralink") Use upstream solution and get rid of our OWRTDTB hack. This commit set DEVICE_DTS to $$(DTS) instead of replacing DTS with DEVICE_DTS in device profile because DTS variable will be dropped in later commits. Signed-off-by: Chuanhong Guo <gch981213@gmail.com> [Tested on mt7621/mt76x8] Tested-by: Chuanhong Guo <gch981213@gmail.com> [Tested on rt305x/mt7620] Tested-by: INAGAKI Hiroshi <musashino.open@gmail.com> (cherry picked from commit 7a8d3432c739c6ff038295176e8b6324e92fc116) Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ath79: remove ath10k drivers from Archer C7 v1 profileStijn Segers2019-11-231-1/+1
| | | | | | | | | | | Ath10k packages were removed from ar71xx in master in commit 34113999ef43 ("ar71xx: Remove ath10k packages from archer-c7-v1 (fixes FS#1743)") but ath79 in master and the 19.07 branch still suffer from the issue. Signed-off-by: Stijn Segers <foss@volatilesystems.org> [commit subject and description facelift] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: nf_conntrack_rtcache: fix WARNING on rmmodYousong Zhou2019-11-231-3/+1
| | | | | | | | Fixes b7c58a1ee ("kernel: nf_conntrack_rtcache: fix cleanup on netns delete and rmmod") Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com> (cherry picked from commit b3779e920ebaa168eaf18ac1140774c32b6ec6b6)
* kernel: nf_conntrack_rtcache: fix WARNING on forward pathYousong Zhou2019-11-231-11/+1
| | | | | | | | | | Fixes b7c58a1ee ("kernel: nf_conntrack_rtcache: fix cleanup on netns delete and rmmod") Resolves FS#2624 Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com> (cherry picked from commit 1c5df850a07690451f2878a310c0ea67d0690836)
* kernel: nf_conntrack_rtcache: fix cleanup on netns delete and rmmodYousong Zhou2019-11-231-1/+13
| | | | | | | | | Fixes FS#1472, FS#2353, FS#2426 Fixes: b3f95490 ("kernel: generic: Add kernel 4.14 support") Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com> Acked-by: Hauke Mehrtens <hauke@hauke-m.de> (cherry picked from commit b7c58a1eeba5be2e1f77ec05b417be9d87e26916)
* ipq40xx: add support for AVM FRITZ!Repeater 1200David Bauer2019-11-226-5/+281
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware -------- SoC: Qualcomm IPQ4019 RAM: 256M DDR3 FLASH: 128M NAND WiFi: 2T2R IPQ4019 bgn 2T2R IPQ4019 a/n/ac ETH: Atheros AR8033 RGMII PHY BTN: 1x Connect (WPS) LED: Power (green/red/yellow) Installation ------------ 1. Grab the uboot for the Device from the 'u-boot-fritz1200' subdirectory. Place it in the same directory as the 'eva_ramboot.py' script. It is located in the 'scripts/flashing' subdirectory of the OpenWRT tree. 2. Assign yourself the IP address 192.168.178.10/24. Connect your Computer to one of the boxes LAN ports. 3. Connect Power to the Box. As soon as the LAN port of your computer shows link, load the U-Boot to the box using following command. > ./eva_ramboot.py --offset 0x85000000 192.168.178.1 uboot-fritz1200.bin 4. The U-Boot will now start. Now assign yourself the IP address 192.168.1.70/24. Copy the OpenWRT initramfs (!) image to a TFTP server root directory and rename it to 'FRITZ1200.bin'. 5. The Box will now boot OpenWRT from RAM. This can take up to two minutes. 6. Copy the U-Boot and the OpenWRT sysupgrade (!) image to the Box using scp. SSH into the Box and first write the Bootloader to both previous kernel partitions. > mtd write /path/to/uboot-fritz1200.bin uboot0 > mtd write /path/to/uboot-fritz1200.bin uboot1 7. Remove the AVM filesystem partitions to make room for our kernel + rootfs + overlayfs. > ubirmvol /dev/ubi0 --name=avm_filesys_0 > ubirmvol /dev/ubi0 --name=avm_filesys_1 8. Flash OpenWRT peristently using sysupgrade. > sysupgrade -n /path/to/openwrt-sysupgrade.bin Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 7f187229a8e9b7966248b1e024217e07a9fc3e50) Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* layerscape: Fix kernel patchHauke Mehrtens2019-11-221-1/+1
| | | | | | | The kernel update added one "+" too much. Fixes: db345220b485 ("kernel: bump 4.14 to 4.14.155") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: Add missing configuration optionHauke Mehrtens2019-11-221-0/+1
| | | | | | | | This was found by the build bot. Fixes: db345220b485 ("kernel: bump 4.14 to 4.14.155") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> (cherry picked from commit 103e49f62e72664ee0d5285007907a75960e8645)
* cns3xxx: use proper macros for defining partition regionsKoen Vandeputte2019-11-221-6/+8
| | | | | | | | While at it, also reorder the items for improved readability. Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> (cherry picked from commit 6b2f953db346cfb4ddf05654efa3ad7eb84ed99f)
* kernel: bump 4.14 to 4.14.155Koen Vandeputte2019-11-2228-202/+97
| | | | | | | | | | | | | | | | | Refreshed all patches. Altered patches: - 707-dpaa-ethernet-support-layerscape.patch Remove upstreamed: - 034-v4.20-MIPS-BCM47XX-Enable-USB-power-on-Netgear-WNDR3400v3.patch - 001-4.21-01-BCM63XX-fix-switch-core-reset-on-BCM6368.patch - 073-qcom-ipq4019-fix-cpu0-s-qcom-saw2-reg-value.patch Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: fix buttons for TP-Link TL-WDR4900 v2Adrian Schmutzler2019-11-211-2/+13
| | | | | | | | TP-Link TL-WDR4900 v2 only has one combined WPS/Reset button, so don't set up an RFKILL for this device. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 25127f58b42d794bd47d56ea107f3dfc9cc4816c)
* ar71xx: fix LED setup for TL-WDR4900 v2Adrian Schmutzler2019-11-211-2/+36
| | | | | | | | | | | | | | | | | | In ar71xx there is only one combined mach file for Archer C5/C7 and TL-WDR4900 v2. This one uses the same LED struct for all devices, defining "green" LEDs for them. However, WDR4900 uses blue front LEDs, while only C5/C7 uses green ones. Despite, in base-files WDR4900 is actually set up with "blue" for the mentioned LEDs. Thus, this patch creates a separate LED struct for WDR4900, so the LEDs can be set up correctly. Despite, the wlan5g LED is removed as it is controlled by ath9k chip for WDR4900 (in contrast to C5/C7). Note: While front LEDs are blue, USB LEDs (on the back) are green, so colors are mixed intentionally for the WDR4900 v2. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 93f2bcc35e371ec0c4ceb76c06f90b898c726ba5)
* ramips: set uImage name of WeVO 11AC NAS and W2914NS v2Sungbo Eo2019-11-211-0/+2
| | | | | | | | | | | | | | | | The stock firmware and bootloader only accept uImage with names that match certain patterns. This patch enables OpenWrt installation from stock firmware without having to reflash the bootloader or access the UART console. Installation via web interface: 1. Flash **initramfs** image through the stock web interface. 2. Boot into OpenWrt and perform sysupgrade with sysupgrade image. Signed-off-by: Sungbo Eo <mans0n@gorani.run> (cherry picked from commit 19800ac095f6ddbba03ccab08e5197b1eec4a49e) [backported] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ar71xx: fix MAC address setup for TL-WDR4900 v2Adrian Schmutzler2019-11-211-3/+6
| | | | | | | | | | | | | The MAC address setup of the TL-WDR4900 v2 is different from the C5/C7. This aligns ar71xx with the setup in ath79: wlan0 (5GHz) : -2 wlan1 (2.4GHz) : -1 eth1 (LAN) : 0 eth0 (WAN) : 1 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit a9d3084b83bb2d0fa2c0b43bf2a0831b5ae1df13)
* ar71xx: fix MAC addresses for Archer C5 v1, C7 v1/v2, WDR4900 v2Adrian Schmutzler2019-11-212-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> (cherry picked from commit a021268032fb64afdce7bafa91c7c7bf44fa6ff2)
* ipq40xx: fix build errorKoen Vandeputte2019-11-201-11/+10
| | | | | | | Add missing brace which was accidentally omitted Fixes: 3c5c49af8be7 ("kernel: bump 4.14 to 4.14.154") Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.154Koen Vandeputte2019-11-1927-156/+141
| | | | | | | | | | | | | | | | | | | | | | | | | | | Refreshed all patches. Altered patches: - 902-debloat_proc.patch - 040-dmaengine-qcom-bam-Process-multiple-pending-descript.patch - 807-usb-support-layerscape.patch - 809-flexcan-support-layerscape.patch - 816-pcie-support-layerscape.patch Remove upstreamed: - 303-spi-nor-enable-4B-opcodes-for-mx66l51235l.patch New symbols: X86_INTEL_MPX X86_INTEL_MEMORY_PROTECTION_KEYS CONFIG_X86_INTEL_TSX_MODE_OFF X86_INTEL_TSX_MODE_ON X86_INTEL_TSX_MODE_AUTO SGL_ALLOC Compile-tested on: ar71xx, cns3xxx, imx6, x86_64 Runtime-tested on: ar71xx, cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ath79: fix sysupgrade from ar71xx for WNDR3700 V2 and WNDR3800(CH)Adrian Schmutzler2019-11-171-2/+2
| | | | | | | | | | | | 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> (cherry picked from commit fc44a8481cbf317febaf27a550e0c9fa49be68d5)
* ath79: include rssileds package for ubnt devices with LEDsRoger Pueyo Centelles2019-11-171-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> (cherry picked from commit 1c6066a867400eca9e335235ff4dc43acacc1183) [backported to 19.07] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: assign correct key-code to wps buttonsChristian Lamparter2019-11-172-2/+2
| | | | | | | | | | | | The two ASUS WL-330N and WL-330N3G had the reset keycode assigned to the WPS button. This patch changes all three devices to use KEY_WPS_BUTTON in the hopes that this fixes unwanted restarts/ unexpected behavior from the users point of view. [dropped RG21S] Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (cherry picked from commit ad65d9d7b264d6d17293c59469e770905d2f785a)
* ath79: remap D-Link DIR-859 A1 WPS button to WPSChristian Lamparter2019-11-161-1/+1
| | | | | | | | | The WPS button was mapped to the restart/reset. This patch changes it to emit the KEY_WPS_BUTTON keycode so pressing the WPS button does initiate WPS. Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (cherry picked from commit 7a7610c21bb0979f2ae14f3c31012ac9e148b439)
* ramips: disable D-Link DIR-300 B1 by defaultJo-Philipp Wich2019-11-161-0/+1
| | | | | | | | Disable the DIR-300 B1 image by default as the device has insufficient flash space for release build images. Fixes: FS#2606 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ramips: rt3833: fix build breakagePetr Štetiar2019-11-151-1/+1
| | | | | | | | | | | | Commit 60f41c6c9ef6 ("ramips: add usb-ledtrig-usbport to DEVICE_PACKAGES of CY-SWR1100") added stray | during backport which caused build breakage on the buildbots: bash: -c: line 0: syntax error near unexpected token `|' bash: -c: line 0: `echo kmod-usb-core kmod-usb-ledtrig-usbport kmod-usb-ohci kmod-usb2 swconfig | | mkhash md5 | head -c 8' Fixes: 60f41c6c9ef6 ("ramips: add usb-ledtrig-usbport to DEVICE_PACKAGES of CY-SWR1100") Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: add usb-ledtrig-usbport to DEVICE_PACKAGES of CY-SWR1100Sungbo Eo2019-11-141-1/+2
| | | | | | | | | | 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, backported to 19.07] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 261c746631d2bf311a6b62a6d3bacce6fde90976)
* ramips: fix MAC address setup for Samsung CY-SWR1100Sungbo Eo2019-11-141-3/+3
| | | | | | | | | | | | 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> (cherry picked from commit 7231c1edd99217c6baa8d7d5d841d75ad9de26f1) [backported due to base-files split] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: fix SUPPORTED_DEVICES for TP-Link TL-WR1043ND v3Adrian Schmutzler2019-11-121-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> (cherry picked from commit b5791118ccd3039cc9ef6fd3b1c4efcad6ab154f)
* ar71xx: fix tl-wdr3320-v2 upgrade南浦月2019-11-121-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> (cherry picked from commit 0ff2385a92c0a31769fce954b7bd571d6114dbc8)
* kernel: bump 4.14 to 4.14.152Koen Vandeputte2019-11-125-122/+11
| | | | | | | | | | | | | | | Refreshed all patches. Altered patches: - 301-arch-support-layerscape.patch Remove upstreamed: - 950-0311-sc16is7xx-Fix-for-Unexpected-interrupt-8.patch Compile-tested on: ar71xx, cns3xxx, imx6, x86_64 Runtime-tested on: ar71xx, cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* 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> (cherry picked from commit 5dc535419fe5f59839686570545fc4180e14d545)
* 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> (cherry picked from commit f7f9fe5256ebb660d3160452c3c01a9eb080938f)
* kernel: fix LED netdev trigger on interface renameMartin Schiller2019-11-091-0/+49
| | | | | | | | | | | 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> Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit edbadec843a77286d4f690a3641b7bca97f4c998)
* ath79: disable building future NAND images for GL-AR300M/GL-AR750SAdrian Schmutzler2019-11-072-3/+3
| | | | | | | | | | | | | | | | | | | | To simplify the upgrade process and ensure easier identification of device partitioning, the following devices are disabled on ath79 target in openwrt-19.07 branch: - glinet,gl-ar300m-nor - glinet,gl-ar300m-nand - glinet,gl-ar750s Proper ath79 (NAND) support for the devices is expected to be introduced based on kernel 4.19 (see GitHub PR #2184). In openwrt-19.07, ar71xx should be used for those devices. With this, we ensure that the new ath79 image names (at least for releases) refer to the updated partitioning. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ar71xx: improve support for TP-Link CPE510 v2Adrian Schmutzler2019-11-067-21/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes commit bae927c551fd ("ar71xx: add support for TP-LINK CPE510 V2.0") where the support for this device wasn't optimal. Device support for the CPE510v2 so far has been a hack to enable flashing with CPE510v1 images. Those even have different hardware (e.g. additional ethernet port). With this patch, we provide proper support for this device in ar71xx. Installation: - Flash factory image through stock firmware WEB UI or through TFTP - To get to TFTP recovery just hold reset button while powering on for around 4-5 seconds and release. - Rename factory image to recovery.bin - Stock TFTP server IP: 192.168.0.100 - Stock device TFTP address: 192.168.0.254 Fixes: bae927c551fd ("ar71xx: add support for TP-LINK CPE510 V2.0") Signed-off-by: Andrew Cameron <apcameron@softhome.net> [Rebased onto revert commit, changed comments in mach-cpe510.c, changed commit title and description, fixed eth0 MAC address, removed eth1 initialization] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> [squashed revert, added fixes tag] Signed-off-by: Petr Štetiar <ynezz@true.cz> (cherry picked from commit c79b796280fa5cd64bac663f9d5e5d9a737c30d6) [added CPE510V2 entry to tplink-safeloader.c] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* Revert "ipq806x: fix EA8500 switch control"Petr Štetiar2019-11-061-16/+4
| | | | | | | | | | | | | | | | There is a problem with the EA8500, the switch will not work after soft reboot, the only way to get it working again is to power cycle it manually. There are probably several issues in the play, it's quite hard to fix it without having access to the actual device, so I don't see any other option now, then revert the offending commit. Ref: PR#2047 Fixes: FS#2168 ("Switch no longer work after restart on Linksys EA8500") Reported-by: Adam <424778940z@gmail.com> Signed-off-by: Petr Štetiar <ynezz@true.cz> (cherry picked from commit 04d6753d03e3a6db07b7a2d3296774d0965bbbfa)
* ipq806x: use switch trigger for WAN LED on NETGEAR boardsDavid Bauer2019-11-051-1/+1
| | | | | | | | | | | With this commit, the WAN LED is triggered by the switch port state instead of the eth0 netdev. Otherwise, the LED is always illuminated, regardless of the WAN port link state. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 70d5989c9c99788a9b2a1a737987edcf7e1ae382) Signed-off-by: David Bauer <mail@david-bauer.net>
* ipqx0xx: add Generic subtargetPaul Spooren2019-11-034-0/+4
| | | | | | | | | | | | | | | | | | | Both targets miss a subtarget causing an image naming style which is different from other all othe targets, even tho it already uses `x/generic/` as subfolder as if the subtarget would exist. This commit adds the Generic subtarget resulting in consistent naming. ~/src/openwrt/openwrt/bin/targets/ipq806x/generic$ ls openwrt-ipq806x-generic-netgear_d7800-initramfs-uImage openwrt-ipq806x-generic-netgear-d7800.manifest openwrt-ipq806x-generic-netgear_d7800-squashfs-factory.img openwrt-ipq806x-generic-netgear_d7800-squashfs-sysupgrade.bin CC: John Crispin <john@phrozen.org> Signed-off-by: Paul Spooren <mail@aparcar.org> (cherry picked from commit 853e4dd3062df7cb5704b15d6af6730e3194b571)
* ramips: enable external amplifier for D-Link DIR-810LRoger Pueyo Centelles2019-11-031-0/+2
| | | | | | | | | The 2.4 GHz radio had very poor signal reception (-89 dBm for an AP sitting 5 m away). By enabling the external amplifier, received signal has improved to -50 dBm for the same AP. Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> (cherry picked from commit e667d6f46b5fa9ade5da1d76c8cc1aab1df1dcb6)
* ath79: Clean up GL-AR300M DTS/DTSI inclusionsJeff Kletsky2019-11-032-4/+1
| | | | | | | | | | | | | Modify GL-AR300M-Lite and GL-AR300M (NOR): * Include qca9531_glinet_gl-ar300m.dtsi directly rather than qca9531_glinet_gl-ar300m-nor.dts * Remove redundant inclusion of gpio.h and input.h Signed-off-by: Jeff Kletsky <git-commits@allycomm.com> Reviewed-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit f5c7fe2ff0deb20f76b4d65195434e35cbb4e08a)
* ramips: fix WiFi MAC addresses for D-Link DIR-810LAdrian Schmutzler2019-11-031-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | So far, WiFi MAC addresses for this device have been set up from caldata. However, this returns values which do not look like MAC addresses. They also do not match stock firmware: wlan0 (5.0): 00:11:22:00:17:D0 from 0x8004 wlan1 (2.4): 00:11:22:00:17:CD from 0x4 (and 0x2e) It looks like the only valid MAC address on this device is at 0x28. So, this patch changes setup to calculate addresses based on the value at 0x28: lan: *:0A (flash, label) wan: *:0B (flash + 1) wifi2: *:0A (flash) wifi5: *:0C (flash + 2) Thanks to Roger Pueyo Centelles <roger.pueyo@guifi.net> for investigating this on his devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit d1072096f49823eb39357f9555d7854a9c91bcfb)
* kernel: bump 4.14 to 4.14.151Koen Vandeputte2019-10-313-20/+20
| | | | | | | | | Refreshed all patches. Compile-tested on: ar71xx, cns3xxx, imx6, x86_64 Runtime-tested on: ar71xx, cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.150Koen Vandeputte2019-10-303-3/+3
| | | | | | | | | Refreshed all patches. Compile-tested on: ar71xx, cns3xxx, imx6, x86_64 Runtime-tested on: ar71xx, cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ath79: add support for UniFi AC-LRAndreas Ziegler2019-10-275-1/+19
| | | | | | | | | | | | | | | | The Unifi AC-LR has identical hardware to the Unifi AC-Lite. The antenna setup is different according to the vendor, which explains the thicker enclosure. Therefore, it is helpful to know the exact device variant, instead of having "Ubiquiti UniFi-AC-LITE/LR". Signed-off-by: Andreas Ziegler <dev@andreas-ziegler.de> [fix legacy name in commit message; add old boardname to SUPPORTED_DEVICES] Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 07c1ddf522dbe6085af664cf03a41f636a70b99c) Signed-off-by: David Bauer <mail@david-bauer.net>
* ar71xx: add model detection for UniFi AC-LRAndreas Ziegler2019-10-272-0/+9
| | | | | | | | | | | | | | | | This commit adds correct model detection for UniFi AC-LR. Previously, said device was incorrectly detected as UniFi-AC-LITE/MESH. The Information about the device is stored at 0xC in the EEPROM partition. It corresponds to the sysid in /etc/board.info of the Ubiquiti stock firmware. Signed-off-by: Andreas Ziegler <dev@andreas-ziegler.de> [adjust naming style of target to existing ones] Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 2bc7c519dcc0e7ca09feed24a3b9a105bc49f423) Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: add LED migration for several Archer Cxx devicesAdrian Schmutzler2019-10-221-3/+6
| | | | | | | | | | Several Archer Cxx devices were using board-specific LED names in ar71xx, which were changed to "tp-link:*" in ath79. This patch adds migration for them. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 53e6cc7a81175728f64f978c2363a18c1fa66d64)
* ath79: use board name in LED migrationsAdrian Schmutzler2019-10-221-4/+3
| | | | | | | | | | | | | | Several devices added to LED migration script will just have their (old) board name converted to tp-link. By using a variable for this, the amount of code in the migration script can be reduced and the chance for typos is reduced. This patch also introduces the marker for beginning of a pattern "^" to the regex, so the match is more specific. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 6b0eb84336edc995f4723f0a005507f158d3e895)
* ath79: fix patching ath9k MAC address for MyNet WiFi Range ExtenderAdrian Schmutzler2019-10-221-1/+1
| | | | | | | | | | | | | | | | | | The code line patching ath9k MAC address for this device contains a wrong number of arguments including an unset "$mac", which looks like a typo or copy/paste mistake. This has been introduced already in the device support commit 745dee11ac78 ("ath79: add support for WD My Net Wi-Fi Range Extender"). This patch just removes the "$mac" argument, leaving a formally valid line. (No on-device test has been performed.) Cc: Christian Lamparter <chunkeey@gmail.com> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 6b5303378315084bf080a6408c2ca5b2a911aa5d)
* ath79: fix SUPPORTED_DEVICES for ubnt_nanostation-mAdrian Schmutzler2019-10-221-1/+1
| | | | | | | | | | | | | | The ar71xx images for the Ubiquiti NanoStation M (XM) devices use "nanostation-m" as board name, but the ath79 images are only compatible with the "nano-m" board name, so sysupgrade complains. By changing this additional supported device, sysupgrade smoothly upgrades from ar71xx to ath79. Ref: openwrt#2418 Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit f473ce6f231bb9f8913be50e850c771b3463fa14)
* ath79: add SUPPORTED_DEVICES to ubnt_nanostation-m-xwRoger Pueyo Centelles2019-10-211-1/+1
| | | | | | | | | | | | | | | | | | The ar71xx images for the Ubiquiti NanoStation M (XW) devices use "nanostation-m-xw" as the board name, but the ath79 images are only compatible with the "nano-m-xw" board name, so sysupgrade complains. By adding this additional supported device, sysuspgrade smoothly upgrades from ar71xx to ath79. Tested on a NanoStation M (XW) running OpenWrt ar71xx r10250-016d1eb. Ref: https://github.com/openwrt/openwrt/pull/2418 Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> [removed duplicate DEVICE_VARIANT, removed uneeded nano-m-xw support] Signed-off-by: Petr Štetiar <ynezz@true.cz> (cherry picked from commit 6dda2ea6ad133705d243d3cc626779ee24bdc88d) Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-10-31 07:27:52 +0000