aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* ramips: increase max SPI frequency to 50 MHz for EX3700/EX6130Frederik Noe-Sdun2019-11-081-1/+1
| | | | | | | | | Based on Macronix MX25L3205DM2I datasheet this is maximum supported speed. Signed-off-by: Frederik Noe-Sdun <Frederik.Sdun@googlemail.com> [rebased, improved commit title/message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: add support for Netgear EX6130Frederik Noe-Sdun2019-11-086-114/+189
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Specifications: * SoC: MT7620A * RAM: 64 MB DDR * Flash: 8MB NOR SPI flash * WiFi: MT7612E (5Ghz) and builtin MT7620A (2.4GHz) * LAN: 1x100M The -factory images can be flashed from the device's web interface or via nmrpflash. The device seems to use base PCB as EX3700/EX3800, but supporting AC1200 using MT7612E. MAC adresses: 5.0 GHz 0x8004 *:9a 2.4 GHz 0x4 *:9b lan 0x28 *:9b wan 0x2e *:9c Since this is a one-port device, although wan MAC address is set in flash, it is not used in OpenWrt setup. Signed-off-by: Frederik Noe-Sdun <Frederik.Sdun@googlemail.com> [rebased, extended commit message, tiny DTS style fixes] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ar71xx: fix tl-wdr3320-v2 upgrade南浦月2019-11-081-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>
* ar71xx: update uboot-envtools for Netgear WNR routersMichal Cieslakiewicz2019-11-081-1/+10
| | | | | | | Boards added: WNR1000v2, WNR2000v3, WNR2200, WNR612v2, WNDR4300. Boards changed: WNDR3700 (u-boot env size is 2 sectors not 1). Signed-off-by: Michal Cieslakiewicz <michal.cieslakiewicz@wp.pl>
* ath79: update uboot-envtools for Netgear WNR routersMichal Cieslakiewicz2019-11-081-0/+6
| | | | | | Boards added: WNR1000v2, WNR2000v3, WNR612v2, WNDR3700. Signed-off-by: Michal Cieslakiewicz <michal.cieslakiewicz@wp.pl>
* build: image: fix build breakage of some imagesPetr Štetiar2019-11-081-0/+1
| | | | | | | | | | | | | Commit 881ed09ee6e2 ("build: create JSON files containing image info") has removed the crucial empty new line from the image copy step resulting in the following errors during make function expansion: GZ_SUFFIX := bash: GZ_SUFFIX: command not found Makefile:86: recipe for target 'openwrt-ath79-generic-tplink_archer-c7-v5-squashfs-sysupgrade.bin' failed Fixes: 881ed09ee6e2 ("build: create JSON files containing image info") Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ipq40xx: u4019: use reset-gpios instead of phy-reset-gpioKristian Evensen2019-11-071-1/+2
| | | | | | | | Use reset-gpio instead of the custom phy-reset-gpio property to do phy reset on the U4019. phy-reset-gpio was incorrectly introduced when we added support for the U4019, and will be deprecated. Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
* ipq40xx: wpj419: use reset-gpios property for phy resetDaniel Danzberger2019-11-071-1/+2
| | | | | | | The old GPIO based phy reset (phy-reset-gpio) will be removed form the ipq40xx mdio driver in the future. Signed-off-by: Daniel Danzberger <daniel@dd-wrt.com>
* ipq40xx: mdio: remove support for phy-reset-gpioDENG Qingfang2019-11-071-65/+2
| | | | | | | | | | | | | Commit 6f6c00cfc95f ("ipq40xx: Add support for Unielec U4019") has introduced support for `phy-reset-gpio` DT property, which isn't needed as the MDIO already supports `reset-gpios`[1] which could be used instead. 1. https://elixir.bootlin.com/linux/v4.19.81/source/Documentation/devicetree/bindings/net/mdio.txt Ref: PR#2511 Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn> [commit title and description facelift] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* busybox: disable default config option FEATURE_SUID=yHenrique de Moraes Holschuh2019-11-071-1/+1
| | | | | | | | | | | | | | | | | | | | | Commit ad7c6102f209 ("busybox: fix missing install with suid bit set if FEATURE_SUID=y") actually fixes BUSYBOX_CONFIG_FEATURE_SUID option and thus would install busybox setuid root by default which would result in possibly unwanted change of current behaviour, so let's disable this option by default in order to preserve the current status-quo. For the record: disabling FEATURE_SUID to preserve the status-quo does *not* imply the current status-quo is "safer", or for that matter, in any way desireable. That is a discussion to be had on the mailing lists. Switching the FEATURE_SUID default to "n" is simply a compromise to facilitate the merge of the changes that unbreak FEATURE_SUID. Ref: PR#2502 Signed-off-by: Henrique de Moraes Holschuh <henrique@nic.br> [commit title/description facelift] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* busybox: fix missing install with suid bit set if FEATURE_SUID=yHenrique de Moraes Holschuh2019-11-071-0/+3
| | | | | | | | | | | | | | | | | | | | With FEATURE_SUID=y one can install busybox binary belonging to root with the suid bit set, enabling some applets to perform root-level operations even when run by ordinary users. Busybox then drops privileges for applets that don't need root access, before entering their main() function. Currently we don't install busybox binary with suid bit set, rendering this feature unusable. Note that we can't just "chmod u+s /bin/busybox" at runtime as a "cheaper" solution: it would waste approximately 200KiB of FLASH (the whole /bin/busybox binary gets copied into the overlay). Ref: PR#2502 Signed-off-by: Henrique de Moraes Holschuh <henrique@nic.br> [commit title/description facelift, use INSTALL_SUID variable] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* Revert "base-files: rename hostname with EUI of mac address"Adrian Schmutzler2019-11-071-15/+1
| | | | | | | | | | | | This reverts commit 6170c46b477d4953f91b99e805a276de444913cf. There has been demand for further evaluation of the impact of a changed hostname, so this is reverted for now. The default hostname will be "OpenWrt" again after this commit. The macaddr_geteui() function is not removed by this revert. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* base-files: rename hostname with EUI of mac addressRosy Song2019-11-072-1/+22
| | | | | | | | | | | | | | | If a label MAC address is provided for device, system will rename the hostname with OpenWrt_{eui mac address}. This helps to distinguish between different devices. Since it's no good idea to nest json_* functions, this code does not use get_mac_label directly, but only get_mac_label_dt as external resource. Signed-off-by: Rosy Song <rosysong@rosinson.com> [merged with commit introducing macaddr_geteui, rebased on updated label MAC address storage, extended commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* base-files: don't store label MAC address in uci system configAdrian Schmutzler2019-11-072-8/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | If set, label MAC address is available from one of two sources, device tree or board.json. So far, the function get_mac_label was meant for retrieving the address, while an option in uci system config was specified only for case 2 (board.json). The uci config option has several drawbacks: - it is only used for a fraction of devices (those not in DT) - label MAC address is a device property, while config implies user interaction - label_macaddr option will only be set if /etc/config/system does not exist (i.e. only for new installations) Thus, this patch changes the behavior of get_mac_label: Instead of writing the value in board.json to uci system config and reading from this location afterwards, get_mac_label now extracts data from board.json directly. The uci config option won't be used anymore. In addition, two utility functions for extraction only from DT or from board.json are introduced. Since this is only changing the access to the label MAC address, it won't interfere with the addresses stored in the code base so far. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: rename keys node formerly named buttonAdrian Schmutzler2019-11-073-3/+3
| | | | | | | For some devices, the keys node is named "button". Change name to match the rest of the target. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: replace generic button node namesAdrian Schmutzler2019-11-0718-30/+30
| | | | | | | | | | In several DTS files, button nodes are just named buttonX or xxx_button. This replaces the names with more specific names matching the majority of key definitions. While at it, fix name of keys node in one case. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: fix LED netdev trigger on interface renameMartin Schiller2019-11-072-0/+108
| | | | | | | | | 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>
* kernel: add crypto_user mod to crypto-user pkgEneas U de Queiroz2019-11-061-2/+4
| | | | | | | | This is needed to export crypto information to netfilter, allowing the alt. afalg openssl engine to obtain information about the drivers being used. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* wolfssl: update to v4.2.0-stableEneas U de Queiroz2019-11-063-142/+4
| | | | | | | | | | | | | | | Many bugs were fixed--2 patches removed here. This release of wolfSSL includes fixes for 5 security vulnerabilities, including two CVEs with high/critical base scores: - potential invalid read with TLS 1.3 PSK, including session tickets - potential hang with ocspstaping2 (always enabled in openwrt) - CVE-2019-15651: 1-byte overread when decoding certificate extensions - CVE-2019-16748: 1-byte overread when checking certificate signatures - DSA attack to recover DSA private keys Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* ramips, mt7620: reproducible elecom-header uid/gidPaul Spooren2019-11-061-1/+1
| | | | | | | | | | | | | | | | | | | | | The elecom-header renames the firmware image to v_0.0.0.bin, stores its MD5 sum as v_0.0.0.md5 and tars both files again. Both v_0.0.0 files are created as the build user making it harder to reproduce. This commit sets the owner/group of both files to root by adding extra options to the final tar command. Before: 0 buildbot (101) buildbot (102) 3932164 2019-11-05 14:43:22.000000 v_0.0.0.bin 0 buildbot (101) buildbot (102) 33 2019-11-05 14:43:22.000000 v_0.0.0.md5 After: 0 root (0) root (0) 3932164 2019-11-05 23:43:08.000000 v_0.0.0.bin 0 root (0) root (0) 33 2019-11-05 23:43:08.000000 v_0.0.0.md5 Signed-off-by: Paul Spooren <mail@aparcar.org>
* libnl-tiny: update to latest Git headPetr Štetiar2019-11-061-16/+9
| | | | | | | | | | | | | | Includes following changes: 0230d0698e59 add initial GitLab CI support 5e13b797a988 iron out all extra compiler warnings 802fbd4d6f39 cmake: enable extra compiler checks 050bb5c4431b convert into CMake project 5b350e42d1fd refactor into separate Git project and converts the package build to utilize CMake. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: specify N and ND subversions of TL-WR941 with ALT0_MODELAdrian Schmutzler2019-11-061-2/+8
| | | | | | | | | | | | | | | | | | TP-Link's TL-WR941 is sold with detachable antennas internationally (ND version), but with fixed antennas in China (N version). While hardware and images are similar for both variants of v2 and v4, they are different for v6. Having both explicitly will make it easier for user to identify the correct image, and most importantly will raise awareness that N and ND are not necessarily always the same as for TL-WR841 series. With an image selection webpage, using ALT0_MODEL as in this patch will provide the option to list versions for N and ND separately. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: reorganize DTSI files for Netgear R devicesAdrian Schmutzler2019-11-068-217/+141
| | | | | | | | | This reorganizes DTSI files for the Netgear R devices in mt7621 (and the WNDR3700 v5). It creates a common DTSI for all R (sercomm) devices and distributes the remaining code in r6220.dtsi to R6220 and WNDR3700 v5. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: improve support for WeVO 11AC NAS and W2914NS v2Sungbo Eo2019-11-062-11/+25
| | | | | | | | | | | | | | | | | | | | | | | | | - remove WAN port index - load WAN MAC address directly from the flash - provide label MAC address - increase flash's SPI frequency to 80MHz - add mt76 led nodes to make WiFi LEDs work - drop unnecessary pinmux groups The factory partition scheme for MAC addresses (verified on both devices): 0x4 : WiFi 2.4GHz (label_mac-9) 0x28 : unused 0x2e : WAN (label_mac) 0x8004: WiFi 5GHz (label_mac-5) 0xe000: LAN (label_mac-1) 0xe006: unused By improving flash speed, `time dd if=/dev/mtdblock3 of=/dev/null bs=64k` has been reduced from 14.51s to 3.11s. Signed-off-by: Sungbo Eo <mans0n@gorani.run> [rebased] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: move eth0 to parent DTSI for ar9344 TP-Link CPE devicesAdrian Schmutzler2019-11-064-28/+11
| | | | | | | | The &eth0 node is the same for all TP-Link CPE devices in ar9344, so move it to parent DTSI. While at it, do some minor DTS harmonizations. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for the TP-LINK CPE220 V3Andrew Cameron2019-11-068-125/+224
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds support for a popular low-cost 2.4GHz N based AP Specifications: SoC: Qualcomm Atheros QCA9533 (650MHz) RAM: 64MB Storage: 8 MB SPI NOR Wireless: 2.4GHz N based built into SoC 2x2 Ethernet: 2x 100/10 Mbps, integrated into SoC 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 adress:192.168.0.254 This also applies some minor changes to the common DTSI: - use &wmac for label-mac-device, as this one is actually set up in common DTSI - move &eth0 to parent DTSI - fix several leading spaces, added/removed newlines Signed-off-by: Andrew Cameron <apcameron@softhome.net> [DTS style fixes/improvements, updated commit message/title] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: remove default case for MAC address assignmentAdrian Schmutzler2019-11-066-30/+152
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | So far, MAC address assignment in ramips has contained a default case, which defined wan_mac = eth0 + 1 for _every_ device not having an explicit case there. This is not desirable, as many device supporters will just not care or know about this definition, so another MAC address will be introduced by accident. In some cases the wan_mac is assigned although it is not needed, in other cases even addresses not dedicated to the device will be used (e.g. wan_mac actually is eth0 - 1, but during support nobody cared, so eth0 + 1 is used now, which might actually belong to another device ...). Thus, in this PR the former default case is converted to an explicit case. This one comprises all devices not being accounted for by other cases, reduced by those not having wan at all. The big number of entries for this node might be another indication that many of them wouldn't actually be there if there hadn't been default wan_mac setup. In exchange, the current "do nothing" case can be removed, as it will be the new default case. The devices being put in the newly created explicit case were determined as follows: 1. Create a list of all devices based on the DTS files. 2. Remove all devices already having an explicit entry setting their address. 3. Remove all devices that only have lan set up in the first part of 02_network: mt7620: - alfa-network,tube-e4g - asus,rp-n53 - buffalo,wmr-300 - comfast,cf-wr800n - edimax,ew-7476rpc - edimax,ew-7478ac - elecom,wrh-300cr - hnet,c108 - kimax,u25awf-h1 - kimax,u35wf - kingston,mlw221 - kingston,mlwg2 - microduino,microwrt - netgear,ex2700 - netgear,ex3700 - netgear,wn3000rp-v3 - planex,cs-qr10 - planex,mzk-ex300np - planex,mzk-ex750np - ravpower,wd03 - sercomm,na930 - yukai,bocco - zbtlink,zbt-cpe102 - zte,q7 mt7621: - gnubee,gb-pc1 - gnubee,gb-pc2 - linksys,re6500 - mikrotik,rbm11g - netgear,ex6150 - thunder,timecloud - tplink,re350-v1 - tplink,re650-v1 mt76x8: - alfa-network,awusfree1 - d-team,pbr-d1 - glinet,vixmini - vocore,vocore2-lite - tama,w06 - tplink,tl-mr3020-v3 - tplink,tl-wa801nd-v5 - tplink,tl-wr802n-v4 - tplink,tl-wr902ac-v3 - vocore,vocore2 - widora,neo-16m - widora,neo-32m rt288x: - buffalo,wli-tx4-ag300n - dlink,dap-1522-a1 rt305x: - allnet,all0256n-4m - allnet,all0256n-8m - allnet,all5002 - allnet,all5003 - alphanetworks,asl26555-16m - alphanetworks,asl26555-8m - asus,wl-330n - aximcom,mr-102n - dlink,dcs-930 - easyacc,wizard-8800 - hame,mpr-a2 - hootoo,ht-tm02 - huawei,d105 - intenso,memory2move - planex,mzk-dp150n - rt305x dlink,dcs-930l-b1 - sparklan,wcr-150gn - tenda,3g150b - tenda,3g300m - tenda,w150m - trendnet,tew-638apb-v2 - unbranded,a5-v11 - vocore,vocore-16m - vocore,vocore-8m - wansview,ncs601w - zorlik,zl5900v2 rt3883: - loewe,wmdr-143n - omnima,hpm 4. Put the remaining devices in the new case. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: DTS file style update and harmonizationAdrian Schmutzler2019-11-06120-660/+749
| | | | | | | | | | | | | | | | | | This applies several style adjustments that have been requested in recent reviews to older DTS files. Despite making the code base more consistent, this will also help to reduce review time when DTSes are copy/pasted. Applied changes: - Rename gpio-keys/gpio-leds to keys/leds - Remove node labels that are not used - Use label property for partitions - Prefix led node labels with "led_" - Remove redundant includes - Harmonize new lines after status property - Several smaller style fixes Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: improve netis WF-2881 supportSungbo Eo2019-11-062-14/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch does the following: 1. remove u-boot-env partition Stock bootloader saves env variables at 0x80000 in flash, and there is nothing stored at 0x30000. By merging the partition "u-boot-env" with "u-boot", the partition table becomes the same as used in stock firmware: 00000000-00080000: "Bootloader" 00080000-00100000: "Config" 00100000-00140000: "Factory" 00140000-07f80000: "Kernel" 2. fix LAN/WAN MAC addresses and provide label MAC address Ethernet MAC addresses are stored in factory partition at: 0xe000: LAN (label_mac) 0xe006: WAN (label_mac+1) 3. fix LAN port order WF-2881 LAN ports are in reverse order of switch ports. 4. fix WiFi LEDs mt76 led nodes are added to make WiFi LEDs work. On top of this, mt76 node names are changed to more generic ones, and compatible strings are also added. 5. fix pinmux groups uart3 and uart2 pins are used as button and led, but jtag pins are not. Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* gitignore: ignore patches in OpenWrt root directoryAdrian Schmutzler2019-11-061-0/+1
| | | | | | | This will have GIT ignore patches in root directory, as created when using "git format-patch". Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* tools/automake: Revert "Do not use $(V) - force AM_V=1"Fredrik Olofsson2019-11-061-13/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 43365ca66253 ("Do not use $(V) - force AM_V=1") as it breaks verbose output in automake packages, deviating from the upstream and expected behaviour. As you can see, neither make command outputs the expected verbose compile command lines: ``` $ make package/mtd-utils/{clean,compile} V=sc ... CCLD lsmtd CC nand-utils/nanddump.o CCLD nanddump ... ``` ``` $ make -C build_dir/target*/mtd-utils-2.1.1 clean ... $ make -C build_dir/target*/mtd-utils-2.1.1 V=1 ... CC lib/libmtd.o CC lib/libfec.o CC lib/common.o CC lib/libcrc32.o ``` The original reason for this commit was some packages failing to build if V is set to something other than 0 or 1. See the discussion in PR https://github.com/openwrt/openwrt/pull/2481 for how to fix this in the package Makefile. Ref: PR#2481 Acked-by: Mirko Vogt <mirko-openwrt@nanl.de> Signed-off-by: Fredrik Olofsson <fredrik.olofsson@anyfinetworks.com> [commit title/description facelift] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* 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>
* mac80211 ath9k: force QCA953x clock to 25MHzDavid Bauer2019-11-051-6/+13
| | | | | | | | | | | The QCA953x only supports 25 MHz refclk, however some OEMs set an invalid bootstrap value for the REF_CLK option, which would break the clock detection in ath9k. Force the QCA953x refclk to 25MHz in ath9k, as this is (according to the datasheet) the only valid frequency. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath10k-firmware: update Candela Tech firmware imagesKoen Vandeputte2019-11-051-24/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | The release notes since last time for wave-1: * October 5, 2019: Fix too-short msg caused by invalid use of PayloadLen in receive path. This appears to resolve the issue of getting (and ignoring) too-short commands when we detect loss of CE interrupts and go into polling mode. * October 12, 2019: Fix regression in IBSS mode that caused SWBA overrun issues. Related to regression added during the ct-station logic, specifically TSF allocation. Thanks for Ahmed Zaki @ Mage-Networks for helping to diagnose and test. * October 15, 2019: Only send beacon tx completion events if we can detect CT driver is being used (based on CT_STATS_OK flag being set). This should help CT firmware work better on stock driver. The release notes since last time for wave-2: * October 15, 2019: Only send beacon tx completion events if we can detect CT driver is being used (based on ATH10k_USE_TXCOMPL_TXRATE2 | ATH10k_USE_TXCOMPL_TXRATE1 flags being set). This should help CT firmware work better on stock driver. * October 31, 2019: Compile out peer-ratecode-list-event. ath10k driver ignores the event. * November 1, 2019: Fix rate-ctrl related crash when nss and other things were changed while station stays associated. See bug: https://github.com/greearb/ath10k-ct/issues/96 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ustream-ssl: update to latest Git HEADJo-Philipp Wich2019-11-051-3/+3
| | | | | | | c9b6668 ustream-ssl: skip writing pending data if .eof is true after connect Fixes: CVE-2019-5101, CVE-2019-5102 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* mac80211: fix build without CONFIG_PCIFelix Fietkau2019-11-051-1/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ath79: fix sorting and harmonize indent in tiny board.d filesAdrian Schmutzler2019-11-052-33/+33
| | | | | | This seems to have been overlooked when splitting base files. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mac80211: add support for multiple wiphys behind a single deviceFelix Fietkau2019-11-054-19/+48
| | | | | | | | | | The device path will be the same for the first phy. For all subsequent phys, the path gets an extra +1, +2, ... Move the code for converting path to phy and vice versa to a separate library script shared by config detection code and the netifd wireless handler script Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mac80211: add pcie apsm backport changesFelix Fietkau2019-11-052-0/+67
| | | | | | Required for newer versions of mt76 Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ipq806x: use switch trigger for WAN LED on NETGEAR boardsDavid Bauer2019-11-041-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>
* hostapd: enable PMKSA and OK caching for WPA3-PersonalDavid Bauer2019-11-041-1/+8
| | | | | | | | | | | | | This enables PMKSA and opportunistic key caching by default for WPA2/WPA3-Personal, WPA3-Personal and OWE auth types. Otherwise, Apple devices won't connect to the WPA3 network. This should not degrade security, as there's no external authentication provider. Tested with OCEDO Koala and iPhone 7 (iOS 13.1). Signed-off-by: David Bauer <mail@david-bauer.net>
* ramips: fix MTK_SOC for RT3662 devicesSungbo Eo2019-11-047-12/+12
| | | | | | | | | | | rt3883.mk contains both RT3662 and RT3883 device profiles, but commit 6a104ac77206 set MTK_SOC to rt3883 for all devices. This patch fixes it, and renames dts files accordingly. And SoC compatible strings are also appended in the dts. Fixes: 6a104ac77206 ("ramips/rt288x,rt3883: Name DTS files based on scheme") Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* mediatek: add mt7629 subtarget with rfb imageChuanhong Guo2019-11-048-4/+471
| | | | | | | | | | base-files are added into subtarget directory like what's done recently in ath79. For this subtarget, metadata checks are enforced and a SUPPORTED_DEVICE is added to generate proper metadata. Since we only have mt7629 support in 4.19, override KERNEL_PATCHVER in target.mk for now. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* mediatek: cosmetic fixes for mt7629-lynx-rfbChuanhong Guo2019-11-041-33/+36
| | | | | | | | | | | This patch did the following things: 1. rename device compatible string 2. add earlycon into cmdline 3. add mac address location according to mt7629 eeprom layout 4. rename mtd partitions 5. replace spaces for indentation with tabs Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* mediatek: backport upstream patches related to mt7629 supportChuanhong Guo2019-11-045-0/+17403
| | | | Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* mediatek: fix Unielec U7623 dts in 4.19Chuanhong Guo2019-11-041-18/+1
| | | | | | remove duplicated pinctrl nodes. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* scripts/dl_github_archive.py: fix python3 str, bytes confusionYousong Zhou2019-11-041-2/+2
| | | | Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* x86: delete empty Makefile introduced by accidentAdrian Schmutzler2019-11-041-0/+0
| | | | | | | | | When changing profile titles for this target, an empty Makefile has been added by accident. Fixes: 14d17306bc73 ("x86: make profile titles more verbose") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* procd: Update to version 2019-11-02Hauke Mehrtens2019-11-031-3/+3
| | | | | | | | | | | | | | f47622e instance: Warn about unexpected number of parameters 564ecdf instance: ujail: Fix allocated size for no_new_privs parameter 7fb2e1d procd: simplify code in procd_inittab_run 4a127c3 procd: replace exit(-1) with exit(EXIT_FAILURE) bc0a73e procd: add upgraded binary to .gitignore ba4c4db procd: add start-console support 3e39fe5 procd: shift arguments for askfirst only once 5d62829 procd: skip respawn in case device disappeared d27949f procd: guard fork_worker calls Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mac80211: rt2x00: remove errornous duplicate conditionDaniel Golle2019-11-038-13/+101
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | https://patchwork.kernel.org/patch/11224189/ -- On 2019-10-28 06:07, wbob wrote: > Hello Roman, > > while reading around drivers/net/wireless/ralink/rt2x00/rt2800lib.c > I stumbled on what I think is an edit of yours made in error in march > 2017: > > https://github.com/torvalds/linux/commit/41977e86#diff-dae5dc10da180f3b055809a48118e18aR5281 > > RT6352 in line 5281 should not have been introduced as the "else if" > below line 5291 can then not take effect for a RT6352 device. Another > possibility is for line 5291 to be not for RT6352, but this seems > very unlikely. Are you able to clarify still after this substantial time? > > 5277: static int rt2800_init_registers(struct rt2x00_dev *rt2x00dev) > ... > 5279: } else if (rt2x00_rt(rt2x00dev, RT5390) || > 5280: rt2x00_rt(rt2x00dev, RT5392) || > 5281: rt2x00_rt(rt2x00dev, RT6352)) { > ... > 5291: } else if (rt2x00_rt(rt2x00dev, RT6352)) { > ... Hence remove errornous line 5281 to make the driver actually execute the correct initialization routine for MT7620 chips. As it was requested by Stanislaw Gruszka remove setting values of MIMO_PS_CFG and TX_PIN_CFG. MIMO_PS_CFG is responsible for MIMO power-safe mode (which is disabled), hence we can drop setting it. TX_PIN_CFG is set correctly in other functions, and as setting this value breaks some devices, rather don't set it here during init, but only modify it later on. Fixes: 41977e86c984 ("rt2x00: add support for MT7620") Reported-by: wbob <wbob@jify.de> Reported-by: Roman Yeryomin <roman@advem.lv> Signed-off-by: Daniel Golle <daniel@makrotopia.org> Acked-by: Stanislaw Gruszka <sgruszka@redhat.com> -- Signed-off-by: Daniel Golle <daniel@makrotopia.org>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-03 08:12:50 +0000