aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ar71xx
Commit message (Collapse)AuthorAgeFilesLines
* kernel: bump 4.9 to 4.9.210Koen Vandeputte2020-01-201-1/+1
| | | | | | | | | Refreshed all patches. Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.209Koen Vandeputte2020-01-201-1/+1
| | | | | | | | | Refreshed all patches. Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: really fix Mikrotik board detectionKoen Vandeputte2020-01-021-0/+1
| | | | | | | | | | | | | | | | | | commit e09da0169a08 ("ar71xx: fix Mikrotik board detection") was generated based on testing a rb-912 board, on which detection failed. Testing on more hardware shows something fun: machine : MikroTik RouterBOARD 922UAGS-5HPacD machine : Mikrotik RouterBOARD 912UAG-5HPnD Both lowercase and uppercase are used. So ensure we support both now .. Fixes: e09da0169a08 ("ar71xx: fix Mikrotik board detection") Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> (cherry picked from commit 845b2a1cfe307394f3f2144cce085bbb5e171ecc)
* ar71xx: fix Mikrotik board detectionKoen Vandeputte2020-01-021-1/+1
| | | | | | | | | | | | Fix a typo in the machine type being extracted from /proc/cpuinfo which causes all Mikrotik board to be undetected properly. This lead to sysupgrade issues and probably some others too. Fixes: acf2b6c8881b ("ar71xx: base-files: fix board detect on new MikroTik devices") Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> (cherry picked from commit e09da0169a088663f6dab1f71b2a4b690eab21d3)
* ar71xx: base-files: fix board detect on new MikroTik devicesHenryk Heisig2020-01-021-132/+149
| | | | | | | | | | | | | | | | | | | | | | Move all MikroTik devices to new function to increase script execution speed. Machine name in new version of MikroTik RouterBOARD devices add "RB" before model name: Old machine name: MikroTik RouterBOARD 951Ui-2nD New: MikroTik RouterBOARD RB951Ui-2nD So this patch should fix it for all currently supported MikroTik boards. Signed-off-by: Henryk Heisig <hyniu@o2.pl> [rebased,commit message facelift,script fixes] Signed-off-by: Petr Štetiar <ynezz@true.cz> [spotted missing 922UAGS-5HPacD] Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> (cherry picked from commit acf2b6c8881b432530bd98fa86753bf6a3546ff7) [backport: do not add boards not supported in 18.06] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ar71xx: fix RB941-2nD detectionJulien Rabier2020-01-021-1/+1
| | | | | | | | | | | | | Some hAP lite routers aren't detected because /proc/cpuinfo shows "RouterBOARD RB941-2nD" instead of "RouterBOARD 941-2nD". Fix that. Signed-off-by: Julien Rabier <taziden@flexiden.org> [Alter string to include all flavours + slight rewrite of commit msg] Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> (cherry picked from commit 6570f3c93aa4110efd1466a6b89742c2e11d7c11)
* kernel: bump 4.9 to 4.9.207Hauke Mehrtens2019-12-261-1/+1
| | | | | | | | | Refreshed all patches. Compile-tested on: lantiq Runtime-tested on: none Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ar71xx: fix MAC address setup for TL-WDR4300 boardSungbo Eo2019-12-212-1/+5
| | | | | | | | | | | | | | | | | | The current ethernet MAC address setup of TL-WDR4300 board is different from the setup of stock firmware: OpenWrt: lan = label_mac -2, wan = label_mac -2 stock: lan = label_mac, wan = label_mac +1 This patch applies to all devices using TL-WDR4300 board: TL-WDR3600 v1 TL-WDR4300 v1 TL-WDR4300 v1 (IL) TL-WDR4310 v1 Mercury MW4530R v1 Signed-off-by: Sungbo Eo <mans0n@gorani.run> (cherry picked from commit 9b02d32e34df2bb8821ec6f08f525bee22d0d1ba)
* 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)
* 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)
* ar71xx: fix WLAN LED names for Archer C7Tomislav Požega2019-11-191-2/+2
| | | | | | | | | Update WLAN LED colour identifier for both interfaces on Archer C7 Signed-off-by: Tomislav Požega <pozega.tomislav@gmail.com> (cherry picked from commit 65762cdd2223d759f5836214143888e32ce5766b) [backported to 18.06] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ar71xx: fix system LED names on Archer C5/C7Tomislav Požega2019-11-191-2/+2
| | | | | | | | Move system LED board definitions of Archer C5/C7 to reflect actual system LED colour used Signed-off-by: Tomislav Požega <pozega.tomislav@gmail.com> (cherry picked from commit a73934fc9ad05207e79a3e58abc3d14eee28b6f2)
* 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.9 to 4.9.195Koen Vandeputte2019-10-082-15/+13
| | | | | | | | | | | | Refreshed all patches. Altered patches: - 403-mtd_fix_cfi_cmdset_0002_status_check.patch Compile-tested on: ar71xx Compile-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.194Koen Vandeputte2019-09-241-1/+1
| | | | | | | | | | | | | | | Refreshed all patches. Fixes: - CVE-2019-14814 - CVE-2019-14815 - CVE-2019-14816 - CVE-2019-14821 Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.193Koen Vandeputte2019-09-203-12/+12
| | | | | | | | | | | | Refreshed all patches. Fixes: - CVE-2019-15030 Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: fix potential IRQ misses during dispatch for qca953xKoen Vandeputte2019-09-131-0/+27
| | | | | | | | | | | If both interrupts are set in the current implementation only the 1st will be handled and the 2nd will be skipped due to the "if else" condition. Fix this by using the same approach as done for QCA955x just below it. Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: WNR2200: remove redundant GPIO for WLAN LEDMichal Cieslakiewicz2019-08-301-0/+1
| | | | | | | | | | | | | | | | | | | | | | | Without this patch, an extra entry appears for AR9287 GPIO that duplicates WLAN LED but in fact drives nothing: gpiochip1: GPIOs 502-511, ath9k-phy0: gpio-502 ( |netgear:blue:wlan ) out hi gpio-503 ( |netgear:amber:test ) out hi gpio-504 ( |netgear:green:power ) out lo gpio-505 ( |rfkill ) in hi gpio-507 ( |wps ) in hi gpio-508 ( |reset ) in hi gpio-510 ( |ath9k-phy0 ) out hi <===! The pin pointed above is default LED GPIO (8) for AR9287. For WNR2200 it is not connected anywhere - pin 0 drives blue WLAN LED instead - but initialization code is missing that information. This fix calls ap9x_pci_setup_wmac_led_pin() function at device setup, forcing WLAN LED pin to be 0 and removing redundant entry. Signed-off-by: Michal Cieslakiewicz <michal.cieslakiewicz@wp.pl>
* kernel: bump 4.9 to 4.9.190Koen Vandeputte2019-08-281-1/+1
| | | | | | | | | | | | Refreshed all patches. Fixes: - CVE-2019-3900 Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: wpj531: fix SIG1/RSS1 LED GPIOLeon M. George2019-08-041-1/+1
| | | | | | | | | | | | | | | In commit 6c937df749c7 ("ar71xx: wpj531: fix GPIOs for LED") wrong GPIO 13 for SIG1/RSS1 LED was commited, the correct GPIO number for this LED is 12. It's listed in "Hardware Guide - wpj531 7A06 (02/07/2019)" as GPIO12/RSS1 on the LED header and same GPIO 12 is used in the vendor's SDK as well. Fixes: 6c937df749c7 ("ar71xx: wpj531: fix GPIOs for LED") Signed-off-by: Leon M. George <leon@georgemail.eu> [commit subject/message facelift] Signed-off-by: Petr Štetiar <ynezz@true.cz> (cherry picked from commit c070662980047838004b83f7af59e7015d3c7922)
* ar71xx: fix HiveAP 121 PLL for 1000MDavid Bauer2019-08-011-1/+1
| | | | | | | | | | | | | The Aerohive HiveAP 121 has the wrong PLL value set for Gigabit speeds, leading to packet-loss. 10M and 100M work fine. This commit sets the Gigabit Ethernet PLL value to the correct value, fixing packet loss. Confirmed with iperf and floodping. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit cb49e46a8a4526d86270ced3ba3aa90225ca82d7)
* kernel: bump 4.9 to 4.9.186Koen Vandeputte2019-07-312-2/+2
| | | | | | | | | | | | Refreshed all patches. Fixes: - CVE-2019-3846 Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.183Koen Vandeputte2019-06-243-3/+3
| | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 010-revert-staging-vc04_services-prevent-integer-overflow-in-create_pagelist.patch Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.182Koen Vandeputte2019-06-181-1/+1
| | | | | | | | | | | | | | | Refreshed all patches. Fixes: - CVE-2019-11479 - CVE-2019-11478 - CVE-2019-11477 Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.181Koen Vandeputte2019-06-123-4/+4
| | | | | | | | | Refreshed all patches. Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.177Koen Vandeputte2019-05-212-3/+3
| | | | | | | | | Refreshed all patches. Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: Fix network setup for TP-Link Archer C25 v1Adrian Schmutzler2019-05-191-9/+9
| | | | | | | | | Network for the Archer C25 v1 is set up without switch for no obvious reason. The LED setup is even done switch-based. This patch changes network setup so a switch is created. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: bump 4.9 to 4.9.175Koen Vandeputte2019-05-151-1/+1
| | | | | | | | | Refreshed all patches. Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.172Koen Vandeputte2019-05-061-2/+2
| | | | | | | | | Refreshed all patches. Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: GL.iNet AR300M family: correct LED definitionsAndreas Ziegler2019-04-222-8/+2
| | | | | | | | | remove USB as this is no LED but power control rename WiFi LED with correct color red (like in stock firmware) set middle LED to be used for LAN link/activity Signed-off-by: Andreas Ziegler <dev@andreas-ziegler.de> (cherry picked from commit 53c46b504c630e4c9c5a00bf644a69919bfc0c03)
* ar71xx: Fix IMAGE_SIZE for TP-Link Archer C7 v5Adrian Schmutzler2019-04-111-1/+1
| | | | | | | | | | | | | | IMAGE_SIZE for C7v5 is wrong in openwrt-18.06, looks like it was just copied from C7v4. In master, this got fixed with the introduction of dynamic partitioning in https://github.com/openwrt/openwrt/commit/7c78be1b747eb0c8d64da67deb3a8aec75bd7b9c However, this is not connected to the changes introduced there, but also applies to the static partitioning in openwrt-18.06. It appears to be simply wrong at the moment ... Tested-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ar71xx: Correct MAC address for WAN interface of Archer C7 v5Adrian Schmutzler2019-04-111-0/+4
| | | | | | | | | | | This device shares the network config with v4, thus the WAN MAC also needs to be fixed the same way. However, the partition where the MAC address resides has been changed. Backport of commit 93d23aced24c2e620461e1b0448d35be21f7e501 Tested-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ar71xx: Add "info" partition for TP-Link Archer C7 v5Adrian Schmutzler2019-04-111-1/+1
| | | | | | | | | | | | | | | | This adds the "info" MTD partition, as it is specified in the ath79 DTS: https://github.com/openwrt/openwrt/blob/master/target/linux/ath79/dts/qca9563_tplink_archer-c7-v5.dts#L35 This is required to set the WAN MAC address, as it is build based on the LAN MAC address, which in turn has to be read from the "info" partition: https://github.com/openwrt/openwrt/blob/master/target/linux/ath79/dts/qca9563_tplink_archer-x7-v5.dtsi#L184 Backport of commit 9aa8f87d277bf2f666fa5bf90c5efd59dd044d54 Tested-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ar71xx: Remove ath10k packages from archer-c7-v1 (fixes FS#1743)Aubrey McIntosh, PhD2019-04-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ath10k_pci driver crashes once loaded and causes boot loops on this device as 5GHz radio QCA9880-AR1A shipped with this router is broken. It's not possible to fix this problem in software, miniPCIe radio has to be replaced. We could've probably fixed crashing of the ath10k driver by reverting following upstream commit: commit 1a7fecb766c83dace747f42b25bbb544b00a0163 Author: Michal Kazior <michal.kazior@tieto.com> Date: Sat Jan 24 12:14:48 2015 +0200 ath10k: reset chip before reading chip_id in probe but it's not worth the effort as it wouldn't make that 5GHz radio usable anyway. So it seems more convenient to just remove the crashing driver and provide bootable images, as I believe, that a router that is working but degraded is better than a router that will not work. For details please see discussions in PR[1] and in FS#1743[2]. 1. https://github.com/openwrt/openwrt/pull/1349 2. https://bugs.openwrt.org/index.php?do=details&task_id=1743 Reviewed-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> Signed-off-by: Aubrey McIntosh, PhD <aubrey.mcintosh@utexas.edu> [subject and commit message tweaks] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: bump 4.9 to 4.9.168Koen Vandeputte2019-04-081-1/+1
| | | | | | | | | Refreshed all patches. Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.164Koen Vandeputte2019-03-251-1/+1
| | | | | | | | | Refreshed all patches. Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: Fix 5 GHz MAC address for Archer C60 v2Adrian Schmutzler2019-02-201-1/+6
| | | | | | | | | | Looks like C60 v2 needs the MAC address to be calculated manually, while the C60 v1 gets it correctly without manual interference. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [added id] (cherry picked from commit 319c5d7c49503d1afbfb3164b18cf966e11fac6a)
* kernel: bump 4.9 to 4.9.153Koen Vandeputte2019-01-311-1/+1
| | | | | | | | | Refreshed all patches. Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: use correct wan mac address for the TP-Link Archer C7 v4David Santamaría Rogado2019-01-301-7/+11
| | | | | | | | | | | | | | The correct MAC address for this device is lan_mac +1, there is no need to set lan_mac so use base_mac variable instead lan_mac. Based on this PR for ath79: https://github.com/openwrt/openwrt/pull/1726 Signed-off-by: David Santamaría Rogado <howl.nsp@gmail.com> [fix alphabetical ordering, reword subject] Signed-off-by: Jo-Philipp Wich <jo@mein.io> (cherry picked from commit 4bcf58135210736f2a1603609d2a76b3e188e2ad)
* ar71xx: Add usb drivers in Archer C7 v4/v5 imagesDaniel Halmschlager2019-01-301-1/+1
| | | | | | | | | | | | | This commit adds the default usb packages - kmod-usb-core - kmod-usb2 - kmod-usb-ledtrig-usbport for Archer C7 v4 and v5. (The C7 v5 configuration is based on the v4, therefore the change for v4 also applies for v5.) Signed-off-by: Daniel Halmschlager <dh@dev.halms.at> (backported from commit 99e212171abf44d6e0f7e7ba50a229ad7b3f3a34)
* kernel: bump 4.9 to 4.9.152Koen Vandeputte2019-01-281-2/+2
| | | | | | | | | Refreshed all patches. Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: add support for UniFi-AC-Mesh-ProChristoph Krapp2018-12-155-8/+21
| | | | | | | | | | | | | | | | | This adds the build option for UniFi AC Mesh Pro as well as model detection for it. The device is a hardware clone of the AC Pro. - SoC: QCA9563-AL3A (775Mhz) - RAM: 128MiB - Flash: 16MiB - dual firmware partitions! - LAN: 2x 1000M - POE+ - Wireless: 2.4G: QCA9563 5G: UniFi Chip, QCA988X compatible Signed-off-by: Christoph Krapp <achterin@googlemail.com> (cherry picked from commit 987b961537b7002eda21df97dd8bfebe8882bc6d)
* ar71xx: fix TP-Link Archer C7 v5 switch LEDsRinki Kumari2018-11-171-3/+15
| | | | Signed-off-by: Rinki Kumari <rinki13@gmail.com>
* kernel: bump 4.9 to 4.9.134Koen Vandeputte2018-10-191-5/+5
| | | | | | | | | Refreshed all patches. Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: fix mtd corruptionFabio Bettoni2018-10-172-3/+67
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In commit 9e1530b2a35e ("kernel: bump 4.9 to 4.9.117 for 18.06") [1], the following patch for removed: - 403-mtd_fix_cfi_cmdset_0002_status_check.patch This patch contained fixes for both write and erase functions. While the chip-detects for erase got fixed upstream [2], some modifications are still required, even with the fixes applied. Not doing so results in following errors seen: Collected errors: * pkg_write_filelist: Failed to open //usr/lib/opkg/info/luci-lib-ip.list: I/O error. * opkg_install_pkg: Failed to extract data files for luci-lib-ip. Package debris may remain! * opkg_install_cmd: Cannot install package luci-ssl. * opkg_conf_write_status_files: Can't open status file //usr/lib/opkg/status: I/O error. [ 0.780920] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [ 8.406396] jffs2: notice: (415) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found. [ 8.423476] mount_root: switching to jffs2 overlay [ 270.902671] jffs2: Write of 1989 bytes at 0x005ce6f8 failed. returned -5, retlen 962 [ 270.931965] jffs2: Write of 1989 bytes at 0x005ceec0 failed. returned -5, retlen 0 [ 270.939631] jffs2: Not marking the space at 0x005ceec0 as dirty because the flash driver returned retlen zero [ 270.950397] jffs2: Write of 68 bytes at 0x005ceec0 failed. returned -5, retlen 0 [ 270.957838] jffs2: Not marking the space at 0x005ceec0 as dirty because the flash driver returned retlen zero [ 270.968584] jffs2: Write of 68 bytes at 0x005ceec0 failed. returned -5, retlen 0 [ 270.976027] jffs2: Not marking the space at 0x005ceec0 as dirty because the flash driver returned retlen zero [ 270.986735] jffs2: Write of 68 bytes at 0x005ceec0 failed. returned -5, retlen 0 [ 270.994225] jffs2: Not marking the space at 0x005ceec0 as dirty because the flash driver returned retlen zero [1] https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=fec8fe806963c96a6506c2aebc3572d3a11f285f [2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v4.9.133&id=a0239d83e1cb60de5e78452d4708c083b9e3dcbe Fixes: 9e1530b2a35e ("kernel: bump 4.9 to 4.9.117 for 18.06") Signed-off-by: Fabio Bettoni <fbettoni@gmail.com> Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: Fix installation of fw_setenv in sysupgrade ramdiskSven Eckelmann2018-10-072-6/+6
| | | | | | | | | | | | The install_bin from /lib/upgrade/common.sh is no longer creating the symlinks when a secondary parameter is added. But the fw_setenv program was always copied this way to the ramdisk for the upgrade. Instead, just install fw_setenv and let install_bin handle the detection of the required dependencies. Fixes: 438dcbfe74a6 ("base-files: automatically handle paths and symlinks for RAMFS_COPY_BIN") Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
* ar71xx: flag FritzBox 4020 buttons as active lowDavid Bauer2018-10-021-2/+2
| | | | | | | | | | Buttons of AVM FritzBox 4020 are incorrectly flagged as active high. This was an oversight as RFKill button was working as expected even with incorrectly flagged GPIO. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit cd02d4faf981bd4de0427cd23812b41192635d82)
* kernel: bump 4.9 to 4.9.130Koen Vandeputte2018-10-021-2/+2
| | | | | | | | | Refreshed all patches. Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-29 14:29:38 +0000