aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* brcm2708-userland: add new package with RPi utilsÁlvaro Fernández Rojas2019-12-282-0/+75
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm2708: image: stop using mkknlimg scriptÁlvaro Fernández Rojas2019-12-281-6/+1
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm2708: switch to upstream cpufreq driverÁlvaro Fernández Rojas2019-12-283-5/+14
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* ubus: update to version 2019-12-27Petr Štetiar2019-12-281-4/+4
| | | | | | | Fixes socket descriptor passing and bumps ABI_VERSION to 20191227. Ref: http://lists.infradead.org/pipermail/openwrt-devel/2019-December/020840.html Signed-off-by: Petr Štetiar <ynezz@true.cz>
* Revert "kernel: fix kmemleak warnings introduced in 305-mips_module_reloc.patch"Felix Fietkau2019-12-272-18/+12
| | | | | | This reverts commit a03afef7f2e8ae363a97357ec75ffbfef372a9ea. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ipq806x: build DEVICE_DTS based on SOC and device nameAdrian Schmutzler2019-12-271-11/+16
| | | | | | | | | | | | | | | | | | | | This patch uses the SOC variable to calculate DTS names automatically based on the SOC and the device definition node name. This reduces redundancy and (by having to choose DTS name appropriately) will unify the naming of a device in different places (image/Makefile, DTS name, compatible, image name). This is supposed to make life easier for developers and reviewers. Since the kernel uses a "soc-device.dts" scheme for this target, we use this for the derivation of DEVICE_DTS, too, leaving the DTS names unchanged for this target. Note that for some devices the kernel itself uses inconsistent names (DTS naming scheme vs. compatible), leaving us with a manual overwrite of DEVICE_DTS for those cases. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ipq40xx: build DEVICE_DTS based on SOC and device nameAdrian Schmutzler2019-12-2715-41/+42
| | | | | | | | | | | | | | | | | | | This patch uses the SOC variable to calculate DTS names automatically based on the SOC and the device definition node name. This reduces redundancy and (by having to choose DTS name appropriately) will unify the naming of a device in different places (image/Makefile, DTS name, compatible, image name). This is supposed to make life easier for developers and reviewers. Since the kernel uses a "soc-device.dts" scheme for this target, we use this for the derivation of DEVICE_DTS, too, and rename the files not having followed it so far. Note that for some devices the kernel itself is inconsistent, leaving us with a manual overwrite for ap.dk01.1-c1 and ap.dk04.1-c1. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: remove bogus ralink,mtd-eeprom with offset 0x4Adrian Schmutzler2019-12-277-8/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Several devices in mt76x8 subtarget use the following line to set up wmac in their DTS(I) files: ralink,mtd-eeprom = <&factory 0x4> This is strange for several reasons: - They should use mediatek,mtd-eeprom on this SOC - The caldata is supposed to start at 0x0 - The parent DTSI mt7628an.dtsi specifies mediatek,mtd-eeprom anyway, starting from 0x0 - The offset coincides with the default location of the MAC address in caldata Based on the comment in b28e94d4bfa1 ("ramips: MiWiFi Nano fixes"), it looks like the author for this device wanted to actually use mtd-mac-address instead of ralink,mtd-eeprom. A check on the same device revealed that actually the MAC address start at offset 4 there, so the correct caldata offset is 0x0. Based on these findings, and the fact that the expected location on this SOC is 0x0, we remove the "ralink,mtd-eeprom = <&factory 0x4>" statement from all devices in ramips (being only mt7628an anyway). Thanks to Sungbo Eo for finding and researching this. Reported-by: Sungbo Eo <mans0n@gorani.run> Fixes: b28e94d4bfa1 ("ramips: MiWiFi Nano fixes") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* wireguard: bump to 20191226Jason A. Donenfeld2019-12-274-34/+61
| | | | | | | | | | | | | | | | As announced on the mailing list, WireGuard will be in Linux 5.6. As a result, the wg(8) tool, used by OpenWRT in the same manner as ip(8), is moving to its own wireguard-tools repo. Meanwhile, the out-of-tree kernel module for kernels 3.10 - 5.5 moved to its own wireguard-linux- compat repo. Yesterday, releases were cut out of these repos, so this commit bumps packages to match. Since wg(8) and the compat kernel module are versioned and released separately, we create a wireguard-tools Makefile to contain the source for the new tools repo. Later, when OpenWRT moves permanently to Linux 5.6, we'll drop the original module package, leaving only the tools. So this commit shuffles the build definition around a bit but is basically the same idea as before. Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
* mt76: update to the latest versionFelix Fietkau2019-12-271-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2a0a19168dce mt7603: remove vif sta from poll list on interface remove dc14ac64e7f3 mt7615: remove vif sta from poll list on interface remove d868638fdd96 mt76: remove obsolete .add_buf() from struct mt76_queue_ops 50b1e9bd25cd mt76: refactor cc_lock locking scheme 1987b741dac2 mt76: mt76x0: remove 350ms delay in mt76x0_phy_calibrate c93a2d1c1304 mt76: mt76x02u: update ewma pkt len in mt76x02u_tx_prepare_skb 58e1e969f03e mt76: mt7615: remove unneeded semicolon c14d6563c492 mt76: mt76x2e: disable pcie_aspm by default f2be00b1011a mt76: dma: fix buffer unmap with non-linear skbs 20f05897873a mt76: mt76u: rely on usb_interface instead of usb_dev 3cbaf81a185e mt76: mt76u: rely on a dedicated stats workqueue ea19cd7ac6c6 mt76: Remove set but not used variable 'idx' a85c06cec844 mt76: use mt76_dev in mt76_is_{mmio,usb} e0731a82a14f mt76: move SUPPORTS_REORDERING_BUFFER hw property in mt76_register_device cfdb75124e7c mt76: mt7615: add ibss support e2f90adcc3b1 mt76: move interface_modes definition in mt76_core module 5dfb0ec9c6d1 mt76: mt7615: disable radar pattern detector during scanning 7121e163c068 mt76: fix possible out-of-bound access in mt7615_fill_txs/mt7603_fill_txs db78ee08d95e mt76: move mt76_get_antenna in mt76_core module faf5e6fedd7e mt76: mt7615: read {tx,rx} mask from eeprom 44825e88a42d mt76: use rcu_read_lock_bh in mt76_dma_rx_poll af83ee8de928 mt76: move initialization of some struct members to mt76_alloc_device 6493e234b40d mt76: introduce struct mt76_phy ea46624355ec mt76: add support for an extra wiphy in the rx path c5f1e83e30d4 mt76: add support for an extra wiphy in the main tx path 1d8011871458 mt76: add support for an extra wiphy in the tx status path e5e755a7a6b0 mt76: add support for an extra wiphy in mt76_sta_state() ee36c8e2170f mt76: move channel state to struct mt76_phy d246beb23350 mt76: keep a set of software tx queues per phy a3e88bcf17e8 mt76: move state from struct mt76_dev to mt76_phy 9cda51d195db mt76: move chainmask back to driver specific structs df74d6993383 mt76: move txpower_conf back to driver specific structs 9e95fa6208a2 mt76: move txpower and antenna mask to struct mt76_phy 502d09a6e806 mt76: add multiple wiphy support to mt76_get_min_avg_rssi 842cae558b82 mt76: add priv pointer to struct mt76_phy 8ca04846857b mt76: add function for allocating an external wiphy 04cd17a64520 mt76: add ext_phy field to struct mt76_wcid 1c8d69e7d666 mt76: move ampdu_ref from mt76_dev to driver struct e6659d12d01e mt76: mt7615: add dual-phy support for mac80211 ops e5ea72ac7158 mt76: mt7615: add multiple wiphy support for smart carrier sense bdcd45dd04e0 mt76: mt7615: add missing register init for dual-wiphy support 0954c37d015f mt76: mt7615: remove useless MT_HW_RDD0/1 enum 705a0fcdc3a5 mt76: mt7615: add multiple wiphy support to the dfs support code 849fefacc48a mt76: mt7615: rework chainmask handling caa47af1d6f2 mt76: mt7615: add multiple wiphy support to the rx path c5585a735864 mt76: mt7615: initialize dbdc settings on interface add 6265fd1954d7 mt76: mt7615: move radio/mac initialization to .start/stop callbacks 5725d1f919ff mt76: mt7615: select the correct tx queue for frames sent to the second phy 993683d62fb7 mt76: mt7615: add support for registering a second wiphy via debugfs 1456a53ddeb3 mt76: mt7615: update beacon contents on BSS_CHANGED_BEACON ea41ad8bdb36 mt76: mt7615: defer mcu initialization via workqueue 59de6c9447a7 mt7615: replace sta_state callback with sta_add/sta_remove 88db676f8517 mt76: fix rx dma ring descriptor state on reset fff2c07193bb Revert "mt76: use rcu_read_lock_bh in mt76_dma_rx_poll" b3bf83d6da1c mt76: disable bh in mt76_dma_rx_poll efcbee1d8bfc mt76: mt76x0u: do not reset radio on resume 5dc6f6fcc027 treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 174 84554a1fbb9a kernel: fix typos and some coding style in comments a116b0a6afe9 mt76: fix possible undetected invalid MAC address becdec318fce mt76: Off by one in mt76_calc_rx_airtime() 683eb244fa55 mt76: mt7603: reset STA_CCA counter setting the channel 812692db171c mt76: eeprom: add support for big endian eeprom partition 8b362382b10c mt76: mt7615: Fix build with older compilers fc24815a2cb4 mt76: mt7615: report firmware version using ethtool 5cec93d57e6d mt76: mt76x02: fix coverage_class type 9354f0f41d1c mt76: mt7603: set 0 as min coverage_class value a589d095eeb6 mt76: mt7615: add set_coverage class support 257c19f5b56f mt76: clear skb pointers from rx aggregation reorder buffer during cleanup 05c87a33831f mt76: do not overwrite max_tx_fragments if it has been set 05fa07c667f3 mt76: use AC specific reorder timeout 3ef5f3444a94 mt76: mt7615: measure channel noise and report it via survey 726fd501651a mt76: mt7615: increase MCU command timeout 99d8cd03edfa mt76: mt7603: fix input validation issues for powersave-filtered frames 32129af2604d net/wireless: Delete unnecessary checks before the macro call “dev_kfree_skb” 85a8abf80385 mt76: mt76x02: omit beacon slot clearing 8b5d3615e1c8 mt76: mt76x02: split beaconing dc364547d91a mt76: mt76x02: add check for invalid vif idx 462a16e185e4 mt76: mt76x02: remove a copy call for usb speedup fa24aba4c280 mt76: speed up usb bulk copy 6a84ad21306e mt76: mt76x02: add channel switch support for usb interfaces 09fcbc214b10 mt76: usb: use max packet length for m76u_copy 584c0784e019 mt76: mt76x02u: do not set NULL beacons ca17e5657e8a mt76: mt76x02: minor mt76x02_mac_set_beacon optimization d5fdd2e7ced8 mt76: mt7615: fix MT7615_CFEND_RATE_DEFAULT value ae25a4bf99a9 mt76: mt7615: introduce LED support cd759b00cc06 mt76: mt76x02: simplify led reg definitions cf00467c5de4 mt76: mt7603: simplify led reg definitions 1c8e76f4de3e mt76: fix compilation warning in mt76_eeprom_override() 960f5cc2390b mt76: mt76u: fix endpoint definition order 15e1c29ed8e3 mt76: mt7615: add missing settings for simultaneous dual-band support e09b9f61eeb3 mt76: mt7615: rework set_channel function 4cb1195a1530 mt76: mt7615: add set_antenna callback Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: fix kmemleak warnings introduced in 305-mips_module_reloc.patchFelix Fietkau2019-12-272-12/+18
| | | | | | | Physically allocated memory for modules needs to be registered with kmemleak, so it can track it as object. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* wolfssl: bump to 4.3.0-stableEneas U de Queiroz2019-12-261-3/+3
| | | | | | | This update fixes many bugs, and six security vulnerabilities, including CVE-2019-18840. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* curl: rename cyassl->wolfsslEneas U de Queiroz2019-12-261-2/+2
| | | | | | The old name was dropped and no longer works. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* ipq40xx: use ath10k-ct-smallbuffers for 128 MiB devicesPaul Fertser2019-12-261-1/+3
| | | | Signed-off-by: Paul Fertser <fercerpav@gmail.com>
* ubus: update to version 2019-12-19Petr Štetiar2019-12-261-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | Contains following changes: a1523d76b016 fix blob parsing vulnerability by using blob_parse_untrusted c60583743ccf ubus_monitor: workaround possibly false positive uses of memory after it is freed dac6c7c575ac ubusd_monitor: fix possible null pointer dereference 060dfbb26da3 ubus_common: remove duplicate ARRAY_SIZE and add missing include c5f2053dfcfd workaround possibly false positive uses of memory after it is freed 72be8e93f07d lua: ubus_lua_do_subscribe: fix copy&paste error a995b1e68129 lua: workaround false positive dereference of null pointer 08f17c87a000 add fuzzer and cram based unit tests c413be9b376c refactor ubusd.c into reusable ubusd_library afd47189e864 examples: remove dead increments b2e544238672 add initial GitLab CI support 058f4e9526ed libubus: fix incompatible pointer types assigment d2e026a33df8 iron out all extra compiler warnings 5d7ca8309d0a ubusd/libubus-io: fix variable sized struct position warning d61282db5640 ubusd: fix comparison of integers of different signs 90fb16234c22 cmake: enable extra compiler checks and bumps ABI_VERSION to 20191219. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ucert: update to version 2019-12-19Petr Štetiar2019-12-261-3/+3
| | | | | | | | | | | | | | 14a279411cff fix certificate blob parsing vulnerability by using blob_parse_untrusted 19a7225ac018 fix leaking memory in cert_dump_blob 9dba44ddd4f5 fix possibly garbage value returned in cert_process_revoker 4462ff9dedfa add cram based unit tests 5fe64b5606aa cmake: split usign bits into static library 5d7626a2b6d8 cmake: reindent the file e284ed941972 cmake: enable hardening compiler flags and fix the reported issues 7e5390666347 add initial GitLab CI support fa0bf4ef45b1 cmake: add proper include and library dependencies Signed-off-by: Petr Štetiar <ynezz@true.cz>
* libubox: update to version 2019-12-26Petr Štetiar2019-12-261-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Contains following changes: eb7eb6393d47 blobmsg: fix array out of bounds GCC 10 warning 86f6a5b8d1f1 blobmsg: reuse blobmsg_namelen in blobmsg_data 586ce031eaa0 tests: fuzz: fuzz _len variants of checking methods b0e21553ae8c blobmsg: add _len variants for all attribute checking methods cd3059796a57 Replace use of blobmsg_check_attr by blobmsg_check_attr_len 143303149c8b Ensure blob_attr length check does not perform out of bounds reads f2b2ee441adb blobmsg: fix heap buffer overflow in blobmsg_parse 4dfd24ed88c4 blobmsg: make blobmsg_len and blobmsg_data_len return unsigned value 2df6d35e3299 tests: add test cases for blobmsg parsing 8a34788b46c4 test: fuzz: add blobmsg_check_attr crashes 478597b9f9ae blob: fix OOB access in blob_check_type 325418a7a3c0 tests: use blob_parse_untrusted variant 0b24e24b93e1 blob: introduce blob_parse_untrusted 6d27336e4a8b blob: refactor attr parsing into separate function 833d25797b16 test: fuzz: add blob_parse crashes 09ee90f8d6ed tests: add test cases for blob parsing 436d6363a10b tests: add libFuzzer based tests bf680707acfd tests: add unit tests covered with Clang sanitizers f804578847de cmake: add more hardening compiler flags 46f8268b4b5b blobmsg/ulog: fix format string compiler warnings eb216a952407 cmake: use extra compiler warnings only on gcc6+ and bumps ABI_VERSION to 20191226. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ipq806x: fix wrong definition for tsense calibAnsuel Smith2019-12-261-2/+2
| | | | | | | | | We have only 11 sensors on ipq806x. Fix the reg property to load the right amount of data instead of the entire space. Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: rework ipq806x specific tsense temp driverAnsuel Smith2019-12-261-0/+107
| | | | | | | | | | | | | | | | | | | | | | | | | | | Tsense driver for ipq806x have various problem. - Emit wrong error. On probing of this driver, nvmem driver can be not ready and this cause a EDEFER error. Actually this is not an error as the kernel will retry to probe the driver after the nvmem driver is loaded. - Use uninitialized value on trigger of critical temp - Doesn't free allocated memory Because of this, rework the driver and improve it by removing extra load of data. Change the logic of loading data. Use the backup calib data only when the calib data is not present. As the calibration is only needed to set the temp offset, we don't really need to read both calib data and set the offset based only on the backup one. Also change how the notifier function work. At times when we output the trigger message, we already have read the temp so remove the extra read and the wrong uninitialized data that probably caused a kernel panic for null pointer exception. (Think we never experience this bug because the router never reached that temp ever... So just lucky) Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: update kernel config with new driverAnsuel Smith2019-12-261-1/+1
| | | | | | | The config name for cpufreq driver has changed. Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: refresh new and changed patchesAnsuel Smith2019-12-269-212/+496
| | | | | | | Refresh patches to remove fuzz Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq8065: update dtsi with new opp tableAnsuel Smith2019-12-261-53/+91
| | | | | | | | The new driver use opp table to register frequency. Drop psv bindings as they are not used anymore. Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq8064: update dtsi with new opp tableAnsuel Smith2019-12-261-44/+80
| | | | | | | | | The new driver use opp table to register frequency. Drop psv bindings as they are not used anymore. Adds speedbin definition for nvmem driver Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: add patch to support krait cpu scaling driverAnsuel Smith2019-12-261-0/+351
| | | | | | | | | | This patch has been proposed but never actually merged to mainline. It was accepted but never re proposed by the creator. Rework it, fix kernel panic cause by double kfree. Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: backport qcom-cpufreq-kryo patchAnsuel Smith2019-12-263-0/+551
| | | | | | | | Backport patch applied to qcom-cpufreq-kryo driver as krait cpu will base on this driver. Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: drop old cpufreq patchAnsuel Smith2019-12-263-399/+0
| | | | | | | | Drop old cpufreq as now we have new driver that can use normal kernel opp definition Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: opp/core: update patch updating voltage tolerance on voltage adjustAnsuel Smith2019-12-261-12/+21
| | | | | | | | | | | Rework 0052-PM-OPP-Update-the-voltage-tolerance-when-adjusting-t to reflect changes upstream. - Skip unnecessary allocation of buffer to set u_volt - Change opp u_volt directly Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: opp/core: update patch allowing adjusting of OPP voltages at runtimeAnsuel Smith2019-12-261-61/+71
| | | | | | | | Update 0049-PM-OPP-Support-adjusting-OPP-voltages-at-runtime with upstream version. Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: fix bug in L2 cache scalingAnsuel Smith2019-12-261-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It has been notice a buf in L2 cache scaling where the scaling is not done proprely if the frequency is set to the initial state before the new frequency. From: https://patchwork.kernel.org/patch/10565443/ * The clocks are set to aux clock rate first to make sure the * secondary mux is not sourcing off of QSB. The rate is then set to * two different rates to force a HFPLL reinit under all * circumstances. In the initial stage of boot to force a new frequency to apply, is needed to first set the frequency back to the lowest one (aux_rate) and then to the target one. This force and make sure the controller actually switch the frequency to the right one. Apply the same mechanism to L2 frequency scaling. Before scaling to the target frequency, first set the frequency to the aux_rate to force the transition, then scale it to the target frequency. Doing the wrong way can produce unexpected results and could lock the scaling mechanism until a full reboot is done (Causing a full reset by the krait-cc driver) From: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=77612720a2362230af726baa4149c40ec7a7fb05 When the Hfplls are reprogrammed during the rate change, the primary muxes which are sourced from the same hfpll for higher frequencies, needs to be switched to the 'safe secondary mux' as the parent for that small window. This is done by registering a clk notifier for the muxes and switching to the safe parent in the PRE_RATE_CHANGE notifier and back to the original parent in the POST_RATE_CHANGE notifier. This should apply also to L2 scaling... as we can't relly use the notifier, we manually do this on L2 scaling. Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ath79: tp-link: use ath10k-ct-smallbuffers for 64 MiB devicesPaul Fertser2019-12-251-5/+6
| | | | Signed-off-by: Paul Fertser <fercerpav@gmail.com>
* brcm2708: fix malformed patchÁlvaro Fernández Rojas2019-12-251-2/+2
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* wireguard: bump to 20191219Kevin Darbyshire-Bryant2019-12-241-4/+3
| | | | | | | | | | edad0d6 version: bump snapshot 0e38a3c compat: ipv6_dst_lookup_flow was backported to 5.3 and 5.4 2e52c41 wg-quick: linux: use already configured addresses instead of in-memory 3721521 tools: adjust wg.8 syntax for consistency in COMMANDS section 21a1498 wg-quick: linux: try both iptables(8) and nft(8) on teardown Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* brcm2708: update to latest patches from RPi FoundationÁlvaro Fernández Rojas2019-12-24803-2031/+8999
| | | | | | Also removes reverted patches. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm2708: organize kernel patchesÁlvaro Fernández Rojas2019-12-241372-95751/+95751
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: bump 4.9 to 4.9.207Hauke Mehrtens2019-12-2423-49/+49
| | | | | | | | | Refreshed all patches. Compile-tested on: ar7 Runtime-tested on: none Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 4.14 to 4.14.160Hauke Mehrtens2019-12-2411-18/+18
| | | | | | | | | Refreshed all patches. Compile-tested on: ipq40xx, apm821xx Runtime-tested on: ipq40xx Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 4.19 to 4.19.91Hauke Mehrtens2019-12-2412-24/+24
| | | | | | | | | Refreshed all patches. Compile-tested on: ipq40xx, apm821xx Runtime-tested on: ipq40xx Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 4.19 to 4.19.90Koen Vandeputte2019-12-2435-388/+155
| | | | | | | | | | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 010-dmaengine-dw-dmac-implement-dma-prot.patch - 950-0148-Increase-firmware-call-buffer-size-to-48-bytes.patch - 950-0206-Mailbox-firmware-calls-now-use-kmalloc-2749.patch - 402-leds-trigger-netdev-fix-handling-on-interface-rename.patch Fixes: - CVE-2019-19332 Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> [Add 010-dt-bindings-dmaengine-dw-dmac-add-protection-control.patch] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 4.14 to 4.14.159Koen Vandeputte2019-12-2444-270/+142
| | | | | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 302-0002-dmaengine-dw-implement-per-channel-protection-contro.patch Fixes: - CVE-2019-19332 Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ath79: use ath10k-ct-smallbuffers for 64 MiB devicesPaul Fertser2019-12-243-14/+14
| | | | Signed-off-by: Paul Fertser <fercerpav@gmail.com>
* ath10k-firmware: Add kmod-ath10k-ct-smallbuffers to dependsHauke Mehrtens2019-12-241-6/+6
| | | | | | | Only select ath10k-ct-regular when smallbuffers version was not selected. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: ath10k-ct: provide a build variant for small RAM devicesPaul Fertser2019-12-243-1/+141
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | According to many bugreports [0][1][2] the default ath10k-ct kernel module is unusable on devices with just 64 MiB RAM or with 128 MiB and dual ath10k cards. The target boards boot but eventually oom-killer starts to interfere with normal operation, so the current state is effectively broken. Since the two patches in question have a performance impact (and possibly some other unexpected side-effects) a dedicated build variant is added so that users of the low RAM devices can still benefit from all the ath10k-ct advantages. According to testing [3] results, the issue can be experienced even with "a 256MB device with three radios". Measured performance impact of implementing small buffers was lowering "the maximum 5 GHz throughput on an IPQ40xx device without RPS/XPS optimizations from 494/432 Mbit/s for TCP transfers (download/upload) to 438/343 Mbit/s" The patches were apparently inspired by QSDK tweaks used by ODMs for the affected devices. [0] http://lists.infradead.org/pipermail/openwrt-devel/2019-December/020573.html [1] https://github.com/openwrt/openwrt/pull/1077 [2] https://bugs.openwrt.org/index.php?do=details&task_id=2664 [3] https://github.com/freifunk-gluon/gluon/pull/1440#issue-195607701 Signed-off-by: Paul Fertser <fercerpav@gmail.com> [Remove double CONFIG_ATH10K-CT_LEDS entry] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* treewide: Remove self from MAINTAINER entriesFlorian Fainelli2019-12-238-9/+1
| | | | Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
* brcm2708-gpu-fw: update to latest firmwareÁlvaro Fernández Rojas2019-12-231-16/+16
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: Deactivate CONFIG_SFP in generic configHauke Mehrtens2019-12-235-4/+1
| | | | | | | | Deactivate CONFIG_SFP for kernel 4.19 in the generic configuration. The CONFIG_SFP configuration option was not set to anything in the ath79 build for me, set it to deactivated by default. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ath79: Do not build dlink_dir-615-e4 by defaultHauke Mehrtens2019-12-231-0/+1
| | | | | | | The factory image for the dlink_dir-615-e4 is getting too big which makes the full ath79 tiny build fail, deactivate it by default. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* brcm2708: remove unneeded patchesÁlvaro Fernández Rojas2019-12-2383-183652/+3
| | | | | | | - wireless patches - defconfig patches Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* libcxx: Depenency fixesRosen Penev2019-12-232-4/+5
| | | | | | | | | | | | | Don't build with uClibc-ng. It's totally unsupported as several functions are missing. Make the musl libc support conditional. Fix hash with make check FIXUP=1. Apparently I based the Makefile off of libedit and forgot to fix the hash. Signed-off-by: Rosen Penev <rosenp@gmail.com> Fixes: 856ea2bad3b3 ("libcxx: Add package")
* ramips: add label MAC address for Mikrotik RB750Gr3Sven Roederer2019-12-231-3/+1
| | | | | | | | | | | | The device label contains: E01: 74:4D:28:xx:xx:30 E05: 74:4D:28:xx:xx:34 The first value corresponds to the address set in hard_config 0x10. That one is taken for the label MAC address. Signed-off-by: Sven Roederer <freifunk@it-solutions.geroedel.de>
* ramips: simplify state_default/pinctrl0 in device DTS filesAdrian Schmutzler2019-12-23295-1941/+1355
| | | | | | | | | The node pinctrl0 is already set up in the SOC DTSI files, but defined again as member of pinctrl in most of the device DTS(I) files. This patch removes this redundancy for the entire ramips target. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-28 12:58:53 +0000