aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* 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>
* ath79: fix gigabit link pll-data for EX7300Daniel Gimpelevich2019-10-211-2/+2
| | | | | | | | | | | | | | The device did not appear to be reachable unless the connection were forced to 100Mb or lower. Revert to previously working pll-data. Also fix the phy-mode to represent the actual state needed for ethernet to function. Reported-by: Moritz Schreiber <moritz@mosos.de> Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us> [add remark about phy-mode property] Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit ee41b602a2a2ced06c26e6edc160b2a5e9619f0d)
* ipq40xx: essedma: Fix dead lockMasafumi UTSUGI2019-10-201-2/+2
| | | | | | | | | | | | | | | | | | edma_read_append_stats() gets called from two places in the driver. The first place is the kernel timer that periodically updates the statistics, so nothing gets lost due to overflows. The second one it's part of the userspace ethtool ioctl handler to provide up-to-date values. For this configuration, the use of spin_lock() is not sufficient and as per: <https://mirrors.edge.kernel.org/pub/linux/kernel/people/rusty/kernel-locking/c214.html> the locking has to be upgraded to spin_lock_bh(). Signed-off-by: Masafumi UTSUGI <mutsugi@allied-telesis.co.jp> [folded patch into 710-, rewrote message] Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (cherry picked from commit f1d761f95e9664a9c11ce1b98f9e121b43c79d35)
* ath79: correct ar71xx boardname for UniFi AC LiteDavid Bauer2019-10-191-1/+1
| | | | | | | | | | | This corrects the additional boardname for the image metadata to the one used in ar71xx. The previously present additional entry was never used on a running system. Reviewed-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 1a256470e78a90ac97f41e3335b3fc6ee827e4bc) Signed-off-by: David Bauer <mail@david-bauer.net>
* mpc85xx: correct TP-LINK TL-WDR4900 MAC addressesDavid Bauer2019-10-192-4/+4
| | | | | | | | | | | | | | | | This commit fixes TP-Link TL-WDR4900 v1 MAC address assignment. Previously, the MAC addrss was read for the ethernet from the "config" partition. However, the content of this partition is dependent on the firmware which was previously installed on the device. Switch the MAC address source to the U-Boot partition, where the MAC address is always present at a fixed partition. The partition was previously already used for the WiFi MAC-addresses. Reviewed-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 07e555d8735e8fa272e3f6abd35acc9f1ab44367) Signed-off-by: David Bauer <mail@david-bauer.net>
* kirkwood: Fix FS#505 - Can't install LEDE on Linksys EA3500Eubert Bao2019-10-191-0/+3
| | | | | | | | | The default sizes render Device/linksys_audi mage un-flashable. Restore the pagesize, subpagesize, and blocksize for linksys_audi from https://github.com/openwrt/archive. Signed-off-by: Eubert Bao <bunnier@gmail.com> (cherry picked from commit e11fc8439c9f7230441408c4d257efc46f372312)
* kernel: layerscape: fix compilation errorBiwen Li2019-10-191-0/+28
| | | | | | | | | | This fixes a compilation error as follows: drivers/staging/fsl_qbman/qman_config.c:815:29: error: bitwise comparison always evaluates to false [-Werror=tautological-compare] if ((qman_ip_rev & 0xFF00) == QMAN_REV31) { Signed-off-by: Biwen Li <biwen.li@nxp.com> (cherry picked from commit 53b73131e9b38bcae556555de53203d52321794c)
* bcm53xx: sysupgrade: support Luxul NAND devicesDan Haab2019-10-151-0/+2
| | | | | | | This adds support for UBI-aware sysupgrade using Luxul formats. Signed-off-by: Dan Haab <dan.haab@legrand.com> (cherry picked from commit 63c43e5674f346b8ed13377d551e5699afbeb673)
* brcm47xx: fix switch port labels for Asus WL500GP V2Michael Heimpold2019-10-151-1/+5
| | | | | | | | The switch port naming in LuCI does not fit the physical numbers on the front of this device. Since this is confusing, fix it. Signed-off-by: Michael Heimpold <mhei@heimpold.de> (cherry picked from commit e56e5a454e729f1067ba1fc8acfc18b99ccb88b4)
* kernel: bump 4.14 to 4.14.149Koen Vandeputte2019-10-1521-152/+153
| | | | | | | | | | | | Refreshed all patches. Altered patches: - 820-sec-support-layerscape.patch Compile-tested on: ar71xx, brcm2708, cns3xxx, imx6, layerscape, x86_64 Runtime-tested on: ar71xx, cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ramips: remove memory node for ZBT-WE1326Adrian Schmutzler2019-10-111-5/+0
| | | | | | | | | | | | | | | | Memory auto-detection for mt7621 has just been added to 19.07 stable branch. This removes the memory node for the ZBT-WE1326, which will support revision 5 that has 256MiB RAM (Nanya NT5CC128M16IP-DI) instead of 512MiB (up to revision 4). ref: #1930 This is taken from master commit a2c19f1d2f65 ("ramips: dts: drop memory nodes"), where _all_ memory nodes were removed. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: mt7621: add support for memory detectionChuanhong Guo2019-10-111-0/+125
| | | | | | | | | | | | | | | | | | | | | | | mt7621 has the following memory map: 0x0-0x1c000000: lower 448m memory 0x1c000000-0x2000000: peripheral registers 0x20000000-0x2400000: higher 64m memory detect_memory_region in arch/mips/kernel/setup.c only add the first memory region and isn't suitable for 512m memory detection because it may accidentally read the memory area for peripheral registers. This commit adds memory detection capability for mt7621: 1. add the highmem area when 512m is detected. 2. guard memcmp from accessing peripheral registers: This only happens when some weird user decided to change kernel load address to 256m or higher address. Since this is a quite unusual case, we just skip 512m testing and return 256m as memory size. Signed-off-by: Chuanhong Guo <gch981213@gmail.com> (cherry picked from commit 6d91ddf5175d2eac3c4bc4a404cc0f5dd44cf25b) Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: Fix off-by-one error in FIT mtd partition search.Oldřich Jedlička2019-10-091-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | This fixes off-by-one error introduced in commit dc76900021b8 ("kernel: Correctly search for the FIT image in mtd partition.") Function `mtd_read` starts reading at `offset` and needs `hdr_len` number of bytes to be available. Suppose the easiest case when `offset` is `0` and `hdr_len` equals to `mtd->size` - the `for` loop will not be entered even when enough bytes are available to be read. Same happens for any non-zero `offset`, when `hdr_len` is just enough bytes to be read until `mtd->size` is reached. Imagine that for example `mtd->size=5`, `offset=4` and `hdr_len=1`. Then `offset+hdr_len=5` and the check has to be `offset+hdr_len <= mtd->size`, i.e. `5 <= 5`. The check for `offset + hdr_len` value needs to be inclusive, therefore use `<=`. Fixes: dc76900021b8 ("kernel: Correctly search for the FIT image in mtd partition.") Signed-off-by: Oldřich Jedlička <oldium.pro@gmail.com> [adjusted commit ref, fixes tag] Signed-off-by: Petr Štetiar <ynezz@true.cz> (cherry picked from commit e0ce80d42ace6feba509da16795ab0eb81cf5bf4)
* kernel: Correctly search for the FIT image in mtd partition.Fredrik Olofsson2019-10-091-2/+2
| | | | | | | Previously all iterations of the loop checked offset=0 in the partition. Signed-off-by: Fredrik Olofsson <fredrik.olofsson@anyfinetworks.com> (cherry picked from commit dc76900021b880820adf981bb7b1cf5ff3ffe1fd)
* kernel: bump 4.14 to 4.14.148Koen Vandeputte2019-10-084-4/+4
| | | | | | | | | Refreshed all patches. Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.147Koen Vandeputte2019-10-089-42/+38
| | | | | | | | | | | | | Refreshed all patches. Altered patches: - 403-mtd_fix_cfi_cmdset_0002_status_check.patch (ar71xx) - 403-mtd_fix_cfi_cmdset_0002_status_check.patch (ath79) Compile-tested on: ar71xx, cns3xxx, imx6, x86_64 Compile-tested on: ar71xx, cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: add missing symbol when enabling PTP supportKoen Vandeputte2019-10-081-0/+1
| | | | | | | | | | | | | | | | Discovered by enabling PTP_1588_CLOCK: net/sched/Kconfig:44: warning: menuconfig statement without prompt * * Restart config... * * * PTP clock support * PTP clock support (PTP_1588_CLOCK) [Y/n/?] y Driver for the National Semiconductor DP83640 PHYTER (DP83640_PHY) [N/m/y/?] (NEW) Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* treewide: remove 4.19 leftoversKoen Vandeputte2019-10-0822-7419/+0
| | | | | | | 19.07 branch focuses on kernel 4.14 so remove all remaining 4.19 configs Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* bcm53xx: fix serial console on Luxul XWC-2000Rafał Miłecki2019-10-041-0/+11
| | | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit fedc5b65dc67c0687f0d1b8dafbacf8e7ab899d2)
* bcm53xx: fix sysupgrade for Luxul XWC-2000Rafał Miłecki2019-10-041-1/+1
| | | | | | | Use a correct "compatible" value as in the upstream DTS file. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 64b7dbb3000b7e8772fea40b35ac6ec717f9f822)
* bcm53xx: add pending patch adding Luxul XWC-2000 DTS fileRafał Miłecki2019-10-042-1/+81
| | | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 06091afada06183f541106b3c688a5d30d85c25b)
* ath79: image: add supported string for routerstations and ja76pf2Tomasz Maciej Nowak2019-09-292-0/+3
| | | | | | | | | | Now that the md5 check is fixed and metadata present, sysupgrade on ar71xx will complain about device not being supported by the image. Since the cause is not matching strings for supported devices add them accordingly. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl> (cherry picked from commit a45cf75eca4069f24bf5bba8f245de2e553f7f78)
* ath79: image: append metadata to routerstations and ja76pf2 imagesTomasz Maciej Nowak2019-09-292-2/+2
| | | | | | | | | This target enforces metadata check so add the necessary information. It was previously removed because md5 sum check. When using these sysupgrade images on ar71xx target the check would complain about them not matching. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl> (cherry picked from commit 077d06a1a5a23caae4d0c53afb60913955d2a3ea)
* ar71xx: sysupgrade: accept ath79 combined-imageTomasz Maciej Nowak2019-09-291-1/+1
| | | | | | | | | | | There is md5 sum of whole image embedded in combined-image header which is checked on sysupgrade. The check will fail for ath79 images which may have embedded metadata. This is because metadata are appended after the combined image is created. To allow smooth transition from ar71xx to ath79, strip metadata before calculating md5 sum for whole image. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl> (cherry picked from commit 8b4109c2b4d60495d046157d1baca9b1cdbf8dc8)
* ath79: dts: fix ja76pf2 spi frequencyTomasz Maciej Nowak2019-09-291-1/+1
| | | | | | | | | | | | The frequency was filled acording the information from datasheet for particular chip (Winbond 25Q128BVFG). Unfortunately this led to coruption and introduced bad blocks on the chip. Reducing the frequency to commonly used in ath79, made the board more stable and no new bad blocks were spoted. Fixes: b3a0c97 ("ath79: add support for jjPlus JA76PF2") Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl> (cherry picked from commit c1db564cbc7cad88606f3caedf81d07b0a60931f)
* ath79: Restore GL.iNet GL-AR300M-Lite first-boot connectivityJeff Kletsky2019-09-281-1/+5
| | | | | | | | | | | | | | | | | | | The relationship between GMAC0 and GMAC1 and the kernel devices eth0 and eth1 was reversed for many ath79 devices by commit 8dde11d521 ath79: dts: drop "simple-mfd" for gmacs in SoC dtsi The GL-AR300M-Lite is a single-port device, with the "LAN" port of the GL-AR300M board unpopulated and its sole port now referenced as eth1, as a result of commit 8dde11d521. The device was unreachable on first boot or fresh config. By changing &eth1 (GMAC1) to an MFD, GMAC0 is able to associate with the phy and is known by the kernel as "eth0". Thanks to Chuanhong Guo for the suggestion of "simple-mfd" Signed-off-by: Jeff Kletsky <git-commits@allycomm.com> (cherry picked from commit b90ea19860853dd538e704e3e4402686c316e43c)
* ath79: Correct glinet, gl-ar300m-lite in 02_networkJeff Kletsky2019-09-281-1/+1
| | | | | | | | | | | | | | | Previously, the board name for the GL-AR300M-Lite was incorrect in 02_network, resulting in an unintended, fall-through condition when initializing the network configuration. While builds prior to commit 8dde11d521 (merged June 5, 2019) ath79: dts: drop "simple-mfd" for gmacs in SoC dtsi functioned properly, the error was noted in resolving first-boot connectivity issues related to the single-phy nature of the device and the "swap" of eth0 and eth1 related to that commit. Signed-off-by: Jeff Kletsky <git-commits@allycomm.com> (cherry picked from commit 549ea4dc1878d95ee2b752b8840d75a64a67b679)
* ipq806x: remove unsupported hw-crypto qce driverEneas U de Queiroz2019-09-281-9/+0
| | | | | | | | | | | | | | | | | | The following symbols, selected by the qce driver were removed: CONFIG_CRYPTO_CBC CONFIG_CRYPTO_CTR CONFIG_CRYPTO_DES CONFIG_CRYPTO_DEV_QCE CONFIG_CRYPTO_ECB CONFIG_CRYPTO_NULL CONFIG_CRYPTO_SEQIV CONFIG_CRYPTO_XTS CONFIG_CRYPTO_GF128MUL was removed as well, since it is only needed by some cipher modes (LRW, GCM), none of which are selected, and it is packaged as a module. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* ipq40xx: fix hw-crypto detection of qce driverEneas U de Queiroz2019-09-281-0/+31
| | | | | | | | | | | This adds the CRYPTO_ALG_KERN_DRIVER_ONLY flag to Qualcomm crypto engine driver algorithms, so that openssl devcrypto can recognize them as hardware-accelerated. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com> [refresh, move to ipq40xx as its the only target right now] Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (cherry picked from commit 391b14a8927df9cfc1d503459dd772cd582a64e7)
* apm821xx: fix fan control on highest stepChristian Lamparter2019-09-281-1/+1
| | | | | | | | | | This patch removes a typo (extra "0") so that the 'cpu-alert6' step is triggered once the system reaches 85°C. Note: Unless the WNDR4700 is placed in an hot oven, the hardware-monitor will never reach this value. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* kernel: port upstream nft_flow_offload changes to xt_FLOWOFFLOAD and fix ↵Felix Fietkau2019-09-268-121/+170
| | | | | | | | | | | routing issues Replace an old cleanup patch that never made it upstream with the proper upstream fix. This patch was incompatible with the recent changes that affected the way that the flow tuple dst entry was used. Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry-picked from commits 442ecce76169d and c8933ce533656)
* netfilter: fix crash in flow offload by adding netns supportHsiuWen Yen2019-09-261-2/+7
| | | | | | | | | | | | | | | | | | | | | Commit fcb41decf6c6 ("config: enable some useful features on !SMALL_FLASH devices") enabled netns, which in turn lead to the crash in the flow offload target. When the flow offloading framework intends to delete a flow from the hardware table, it is necessary to retrieve the namespace from nf_flowtable->ft_net. However, no one ever wrote the namespace into nf_flowtable->ft_net in advance. So the framework will mistakenly use a NULL namespace to execute dev_get_by_index_rcu(net, ifindex), leading to the kernel panic. Ref: FS#2321 Fixes: fcb41decf6c6 ("config: enable some useful features on !SMALL_FLASH devices") Tested-by: Simon Tretter <simon@mediaarchitectu.re> Signed-off-by: HsiuWen Yen <y.hsiuwen@gmail.com> [merged patch into offload patch, fix for 4.19, SOB fix, commit subj/msg touches] Signed-off-by: Petr Štetiar <ynezz@true.cz> (cherry-picked from commit d344591e72e5ca96a2bf70a2df38961553185ce8)
* brcm47xx: sysupgrade: fix device model detectionRafał Miłecki2019-09-261-2/+2
| | | | | | | | | $(board_name) was providing content on "boardtype" (and optionally "boardnum") NVRAM values. That function requires & expects more specific and detailed model name extracted from the /proc/cpuinfo. Fixes: f12a32630ff5 ("treewide: use the generic board_name function") Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ipq40xx: abort ar40xx probe on missing PHYsDavid Bauer2019-09-251-0/+23
| | | | | | | | | | | | | The ar40xx driver currently panics in case no QCA807x PHY has been successfully probed. This happens when the external PHY is still in reset when probing the ar40xx switch driver. Note that this patch does not fix the root cause, ar40xx_probe now simply fails instead of causing a kernel panic due to a nullpointer dereference. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit e2c084cabc2b2a2fffc36aee3e48874f9862c74a)
* kernel: bump 4.14 to 4.14.146Koen 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, cns3xxx, imx6, x86_64 Runtime-tested on: ar71xx, cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: add disable_eap_hack sysfs attributeEtienne Champetier2019-09-231-4/+55
| | | | | | | | We are not sure if 640-bridge-only-accept-EAP-locally.patch is still needed as a first step, add disable_eap_hack sysfs config to allow to disable it Signed-off-by: Etienne Champetier <champetier.etienne@gmail.com> (cherry picked from commit 7d542dc8047d276517b296132926e722004065e0)
* ath79: remove invalid uses of ath9k_patch_fw_mac_crcAdrian Schmutzler2019-09-221-3/+3
| | | | | | | | | | | | | Some ar9344-based devices are using ath9k_patch_fw_mac_crc, which is meant to generate a checksum, for fixing their ath9k MAC addresses. However, those do not have a checksum field, and the calculated checksum offset would be negative. This patch will use ath9k_patch_fw_mac function for those devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit f8d8b3f85d70a85d4fabc9b8ed4dbc8020be0523)
* kernel: bump 4.14 to 4.14.145Koen Vandeputte2019-09-2012-25/+25
| | | | | | | | | 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.144Koen Vandeputte2019-09-207-180/+97
| | | | | | | | | | | | | | | Refreshed all patches. Altered patches: - 816-pcie-support-layerscape.patch Fixes: - CVE-2019-15030 Compile-tested on: ar71xx, cns3xxx, imx6, x86_64 Runtime-tested on: ar71xx, cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ramips: add factory image for NETGEAR R6220David Bauer2019-09-161-1/+6
| | | | | | | | | | | This adds an easy-installation factory image for the NETGEAR R6220 router. The factory image can either be flashed via the vendor Web-UI or the bootloader using nmrpflash. Tested with NETGEAR V1.1.0.86 firmware. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 607dfdf211bebb5043cbc0267c1e2c3e3c2514b4)
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-07 01:49:03 +0000