aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* ath79: add support for Xiaomi Mi Router 4QDavid Bauer2019-02-113-0/+165
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware -------- CPU: Qualcomm Atheros QCA9561 RAM: 64M DDR2 FLASH: 16M SPI-NOR ETH: 1x WAN - 2x LAN WiFi: QCA9561 3T3R BTN: 1x Reset - 1x WPS LED: 1x Blue - 1x Red - 1x Yellow UART: TX - GND - RX - VCC (From ethernet port) 115200n8 - 3.3V Installation ------------ 1. Connect to the device via UART. 2. Interrupt the U-Boot on power-on by pressing enter when prompted. 3. Connect you computer to one of the routers LAN ports. Assign yourself the IP 192.168.31.10/24. Copy the OpenWRT initramfs image to a tftp server root directory. Rename the image to 'x4q.bin'. 4. Load the initramfs image to the router by executing following command in U-Boot. The image will boot afterwards. > tftpboot 0x81000000 x4q.bin; bootm 5. SCP the sysupgrade-image into '/tmp'. Remember to assign yourself an IP in 192.168.1.0/24 for this step! 6. Install OpenWRT permanently by executing > sysupgrade -n /tmp/<OpenWRT-sysupgrade-image> Signed-off-by: David Bauer <mail@david-bauer.net>
* gemini: Fix kmod-led-trig-heartbeat typoLinus Walleij2019-02-111-1/+1
| | | | | | | | It's kmod-ledtrig-* not kmod-led-trig-*. Signed-off-by: Linus Walleij <linus.walleij@linaro.org> [extended subject] Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* mac80211: ath10k: support for management rate controlSven Eckelmann2019-02-113-1/+156
| | | | | | | | | | | | | Issues a wmi command to firmware when multicast rate change is received with the new BSS_CHANGED_MCAST_RATE flag. Also fixes the incorrect fixed_rate setting for CCK rates which got introduced with addition of ath10k_rates_rev2 enum. By default the firmware uses 1Mbps and 6Mbps rate for management packets in 2G and 5G bands respectively. But when the user selects different basic rates from the userspace, we need to send the management packets at the lowest basic rate selected by the user. Signed-off-by: Sven Eckelmann <sven@narfation.org>
* ath10k-ct: support for management rate controlSven Eckelmann2019-02-113-1/+156
| | | | | | | | | | | | By default the firmware uses 1Mbps and 6Mbps rate for management packets in 2G and 5G bands respectively. But when the user selects different basic rates from the userspace, we need to send the management packets at the lowest basic rate selected by the user. This change makes use of WMI_VDEV_PARAM_MGMT_RATE param for configuring the management packets rate to the firmware. Signed-off-by: Sven Eckelmann <sven@narfation.org>
* ath10k-firmware: update Candela Tech firmware imagesChristian Lamparter2019-02-111-16/+16
| | | | | | | | | | | | | | | | | | Release notes since last time: 2019-02-08: Fix rate-ctrl assert related to bad logic that tried to guess that lower bandwidth probes were automatically successful if higher was. The NSS mismatch that can happen here caused the assert. Just comment out the offending code (per comment from original QCA code). This is bug 69. 2019-02-10: Fix bssid mis-alignment that broke 4-addr vlan mode (bug 67). Original buggy commit was commit 2bf89e70ecd1 ("dev-ds: Better packing of wal_vdev struct.") Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* build: add KERNEL_ENTRY and sort DEFAULT_DEVICE_VARSChristian Lamparter2019-02-111-6/+5
| | | | | | | | | | | | | | | | | The KERNEL_ENTRY was missing from the DEFAULT_DEVICE_VARS. This bug was discovered while preparing alternative images for the mpc85xx's TP-Link WDR4900-V1, which all failed to boot due to this: |## Booting kernel from Legacy Image at 02000000 ... | Image Name: POWERPC OpenWrt Linux-4.14.96 | Image Type: PowerPC Linux Kernel Image (uncompressed) | Data Size: 2056568 Bytes = 2 MiB | Load Address: 01000000 | Entry Point: 00000000 | Verifying Checksum ... OK Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* mac80211: brcmfmac: fix a possible NULL pointer dereferenceRafał Miłecki2019-02-111-4/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes a possible crash in the brcmf_fw_request_nvram_done(): [ 31.687293] Backtrace: [ 31.689760] [<c004fb4c>] (__wake_up_common) from [<c004fc38>] (__wake_up_locked+0x1c/0x24) [ 31.698043] r10:c6794000 r9:00000009 r8:00000001 r7:bf54dda0 r6:a0000013 r5:c78e7d38 [ 31.705928] r4:c78e7d3c r3:00000000 [ 31.709528] [<c004fc1c>] (__wake_up_locked) from [<c00502a8>] (complete+0x3c/0x4c) [ 31.717148] [<c005026c>] (complete) from [<bf54590c>] (brcmf_fw_request_nvram_done+0x5c8/0x6a4 [brcmfmac]) [ 31.726818] r7:bf54dda0 r6:c6794000 r5:00001990 r4:c6782380 [ 31.732544] [<bf545344>] (brcmf_fw_request_nvram_done [brcmfmac]) from [<c0204e40>] (request_firmware_work_func+0x38/0x60) [ 31.743607] r10:00000008 r9:c6bdd700 r8:00000000 r7:c72c3cd8 r6:c67f4300 r5:c6bda300 [ 31.751493] r4:c67f4300 [ 31.754046] [<c0204e08>] (request_firmware_work_func) from [<c0034458>] (process_one_work+0x1e0/0x318) [ 31.763365] r4:c72c3cc0 [ 31.765913] [<c0034278>] (process_one_work) from [<c0035234>] (worker_thread+0x2f4/0x448) [ 31.774107] r10:00000008 r9:00000000 r8:c6bda314 r7:c72c3cd8 r6:c6bda300 r5:c6bda300 [ 31.781993] r4:c72c3cc0 [ 31.784545] [<c0034f40>] (worker_thread) from [<c003984c>] (kthread+0x100/0x114) [ 31.791949] r10:00000000 r9:00000000 r8:00000000 r7:c0034f40 r6:c72c3cc0 r5:00000000 [ 31.799836] r4:c735dc00 r3:c79ed540 [ 31.803438] [<c003974c>] (kthread) from [<c00097d0>] (ret_from_fork+0x14/0x24) [ 31.810672] r7:00000000 r6:00000000 r5:c003974c r4:c735dc00 [ 31.816378] Code: e5b53004 e1a07001 e1a06002 e243000c (e5934000) [ 31.822487] ---[ end trace a0ffbb07a810d503 ]--- Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ar71xx: add rssileds for xw devicesKoen Vandeputte2019-02-111-0/+1
| | | | | | | | | | | Commit 7ebbbda29377 ("ar71xx: ubnt-(xm,xw): fix LED RSSI indication") adds support for using the RSSI strenght via LEDS. The rssileds package addition got lost during altering the patch. Add it again to fix this. Fixes: 7ebbbda29377 ("ar71xx: ubnt-(xm,xw): fix LED RSSI indication") Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* tools/mpfr: Update to 4.0.2Daniel Engberg2019-02-102-5/+5
| | | | | | | | | Update mpfr to 4.0.2 Use official site as last resort Force thread-safety functionality Refresh patches Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
* tools/bison: Update to 3.3.2Daniel Engberg2019-02-102-14/+14
| | | | | | | | Update bison to 3.3.2 Enable pthreads support Refresh patches Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
* tools/sed: Update to 4.7Daniel Engberg2019-02-101-2/+3
| | | | | | | Update sed to 4.7 Enable pthreads support Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
* tools/tar: Update to 1.31Daniel Engberg2019-02-103-6/+6
| | | | | | | | | Update tar to 1.31 Fixes CVE-2018-20482 Switch to tar.xz tarball Refresh patches Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
* glibc: update to latest 2.27 commit [BZ #24180]Hans Dedecker2019-02-091-2/+2
| | | | | | 9f44fa22cb Add compiler barriers around modifications of the robust mutex list for pthread_mutex_trylock. [BZ #24180] Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* vti: remove setting default firewall zone to wanHans Dedecker2019-02-092-3/+1
| | | | | | | | | Same reasoning as in bdedb798150a58ad7ce3c4741f2f31df97e84c3f; don't set default firewall zone to wan as the firewall zone for the vti interface can be configured in the firewall config or it makes it impossible not to specify a firewall zone for the vti interface. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* ipip: remove setting default firewall zone to wanHans Dedecker2019-02-092-3/+1
| | | | | | | | | Same reasoning as in bdedb798150a58ad7ce3c4741f2f31df97e84c3f; don't set default firewall zone to wan as the firewall zone for the ipip interface can be configured in the firewall config or it makes it impossible not to specify a firewall zone for the ipip interface. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* kernel: fold xt_FLOWOFFLOAD fixes into the main patchFelix Fietkau2019-02-093-144/+37
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* netfilter: fix checking method of conntrack helperHsiuWen Yen2019-02-091-0/+51
| | | | | | | | | | | | | | | | This patch uses nfct_help() to detect whether an established connection needs conntrack helper instead of using test_bit(IPS_HELPER_BIT, &ct->status). The reason for this modification is that IPS_HELPER_BIT is only set when the conntrack helper is attached by explicit CT target. However, in the case that a device enables conntrack helper via the other ways (e.g., command "echo 1 > /proc/sys/net/netfilter/nf_conntrack_helper") , the status of IPS_HELPER_BIT will not present any change. That means the IPS_HELPER_BIT might lose the checking ability in the context. Signed-off-by: HsiuWen Yen <y.hsiuwen@gmail.com>
* base-files: do not strip fwtool signature data during checkFelix Fietkau2019-02-091-1/+1
| | | | | | | Same reason as in commit 9808bd279927bcd2d3a78d19a55229b93bbbcf05 - sysupgrade --test must not alter the image in any way Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ar71xx: ubnt-(xm,xw): fix LED RSSI indicationLech Perczak2019-02-082-5/+6
| | | | | | | | | | | | | | | | | When mapping for RSSI LEDs was defined for interface wlan0 on Ubiquiti XM and XW family, it missed connection to actual interface. Therefore create the mapping to interface, so RSSI LEDs work without additional configuration, after starting rssileds service. Also add the required package for this. While at that, remove coefficients needed for PWM LEDs, as XM and XW boards do not support PWM LEDs. Tested-by: Petr Štetiar <ynezz@true.cz> Signed-off-by: Lech Perczak <lech.perczak@gmail.com> [Squashed commits + remove custom device_packages + slighty rewrite the commit msg] Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: fix RB941-2nD detectionJulien Rabier2019-02-081-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>
* ar71xx: fix Arduino Yun enabling of level shifters outputsEdoardo Scaglia2019-02-081-2/+2
| | | | | | | | | | | | | | | As show in Arduino Yun schematic [1] GPIO 21 and 22 are connected to output enable pin (OE) of two NTB01xx level shifters. NTB01xx datasheets [2] [3] states that OE pin are active-high therefore we should initialize GPIO 21 (DS_GPIO_OE) and GPIO 22 (DS_GPIO_OE2) accordingly to actually enable level shifters outputs. [1] https://www.arduino.cc/en/uploads/Main/arduino-Yun-schematic.pdf [2] https://www.nxp.com/docs/en/data-sheet/NTB0102.pdf [3] https://www.nxp.com/docs/en/data-sheet/NTB0104.pdf Signed-off-by: Edoardo Scaglia <edoardo.87@gmail.com>
* kernel: add missing symbols to 4.19Petr Štetiar2019-02-081-0/+10
| | | | | | | | | | | | While preparing 4.19 for imx6 and test building it with CONFIG_ALL_KMODS=y with verbose mode enabled, I was asked by kernel config about few missing symbols/modules Let's add them to the generic config. Signed-off-by: Petr Štetiar <ynezz@true.cz> [slight rewrite of commit log] Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.19 to 4.19.20Koen Vandeputte2019-02-084-84/+10
| | | | | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 100-arm-cns3xxx-fix-writing-to-wrong-PCI-registers-after.patch Altered patches: - 721-phy_packets.patch Compile-tested on: imx6 Runtime-tested on: imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.98Koen Vandeputte2019-02-087-89/+15
| | | | | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 100-arm-cns3xxx-fix-writing-to-wrong-PCI-registers-after.patch Altered patches: - 721-phy_packets.patch 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.9 to 4.9.155Koen Vandeputte2019-02-086-86/+12
| | | | | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 100-arm-cns3xxx-fix-writing-to-wrong-PCI-registers-after.patch Altered patches: - 721-phy_packets.patch Compile-tested on: ar7 Runtime-tested on: none Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 3.18 to 3.18.134Koen Vandeputte2019-02-081-2/+2
| | | | | | | | | Refreshed all patches. Compile-tested on: adm5120 Runtime-tested on: none Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* mac80211: rt2x00: remove patch causing low tx powerDaniel Golle2019-02-081-43/+0
| | | | | | | | | | | | | | | Remove 980-rt2x00-reduce-power-consumption-on-mt7620.patch which in combination with the most recently added patch reportedly causes TX power to be too weak. "without patches rssi on receiver is ~ -23dBm with 980 about -35dBm, with both patches drops below -40dBm. with 987 only ~-28dBm" We may need to reconsider this once we have implemented TSSI. Fixes: cdb58b2bfe ("mac80211: rt2x00: reduce tx power to nominal level on RT6352") Reported-by: Tomislav Požega <pozega.tomislav@gmail.com> Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* curl: bump to 7.64.0Deng Qingfang2019-02-082-4/+4
| | | | | | | | | | | | Fixed CVEs: CVE-2018-16890 CVE-2019-3822 CVE-2019-3823 For other changes in version 7.64.0 see https://curl.haxx.se/changes.html#7_64_0 Signed-off-by: Deng Qingfang <dengqf6@mail2.sysu.edu.cn>
* mac80211: rt2x00: reduce tx power to nominal level on RT6352Daniel Golle2019-02-081-0/+114
| | | | | | | | | | | | Current implementation of RT6352 support provides too high tx power at least on iPA/eLNA devices. Reduce amplification of variable gain amplifier by 6dB to match board target power of 17dBm. Transmited signal strength with this patch is similar to that of stock firmware or pandorabox firmware. Throughput measured with iperf improves. Device tested: Xiaomi Miwifi Mini. Signed-off-by: Tomislav Požega <pozega.tomislav@gmail.com> Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* gre: remove setting default firewall zone to wanFlorian Eckert2019-02-072-2/+1
| | | | | | | | | | | | | | | | | | | | | | There are two problems with this behaviour that the zone is set to wan if no zone config option is defined in the interface section. * The zone for the interface is "normally" specified in the firewall config file. So if we have defined "no" zone for this interface zone option is set now to "wan" additonaly if we add the interface in the firewall config section to the "lan" zone, the interface is added to lan and wan at once. iptables-save | grep <iface> This is not what I expect. * If I do not want to set a zone to this interface it is not possible. Remove the default assigment to wan if no zone option is defined. If some one need the option it stil possible to define this option. Signed-off-by: Florian Eckert <fe@dev.tdt.de> Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> [PKG_RELEASE increase]
* ath79: ag71xx: Fix tx queue timeouts during ifupPetr Štetiar2019-02-071-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On ath79 and UBNT Bullet M XW (ar9342) I was experiencing weird issues during network setup[1] which I was able to reproduce easily with following commands: uci set network.lan.ipaddr='192.168.1.20' uci commit network ifup lan Which resulted after some time in: ... WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:461 dev_watchdog+0x16c/0x280 NETDEV WATCHDOG: eth0 (ag71xx): transmit queue 0 timed out ... Sometimes I wasn't able to use networking anymore, sometimes it was enough to just ifdown/ifup lan and network was backup. On ar71xx it was all working just fine. I've found out, that it was happening because ag71xx_poll() wasn't called, thus the TX queue wasn't emptied. The ag71xx_poll() is being called from napi hrtimer, which is enabled by napi_schedule() in ar71xx_interrupt(), but since no interrupts were ever fired again after ag71xx_stop() was called, it was always leading to tx queue timeouts: *** ag71xx_hard_start_xmit() eth0: packet injected into TX queue eth0: raw intr=00000001 TXPS POLL eth0: enable polling mode eth0: processing TX ring, flush=no eth0: disable polling mode, rx=1, tx=1,limit=32 ( `ifup lan done here` ) *** ag71xx_stop() *** ag71xx_open() *** ag71xx_hw_enable() IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready *** ag71xx_hard_start_xmit() eth0: packet injected into TX queue *** ag71xx_hard_start_xmit() eth0: packet injected into TX queue ... WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:320 dev_watchdog+0x164/0x274 So I've looked at ag71xx_stop() in ar71xx, added the missing bits to ath79 and fixed this issue. 1. https://github.com/openwrt/openwrt/pull/1635#issuecomment-448638246 Signed-off-by: Petr Štetiar <ynezz@true.cz> [move ag->link before ag71xx_hw_disable to retain ordering as original] Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: rename symbol in kernel 4.19 configKoen Vandeputte2019-02-071-1/+1
| | | | | | | | A symbol was renamed upstream starting from kernel 4.18 [1] Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.0-rc5&id=34b13e5e4641c0e9e0aad471a6d8dfb7999276f1
* nat46: Fix mirror hashHauke Mehrtens2019-02-071-1/+1
| | | | | | | | The package hash does not match the one of the package found on the mirrors and which is generated when I do the git clone. Fixes: 4856fa30a6c ("nat46: import for routing, add myself as maintainer") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* brcm2708: fix early bootloader config restoreStijn Tintel2019-02-061-1/+1
| | | | | | | | | Restoring the bootloader config before rebooting fails: tar: invalid tar magic Add the -z option to the tar command to fix this. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* brcm2708: drop 4.9 supportStijn Tintel2019-02-06205-137124/+6
| | | | Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* ath79: add support for TP-LINK Archer C7 v4Oldřich Jedlička2019-02-055-0/+290
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link Archer C7 v4 is a dual-band AC1750 router, based on the Qualcomm/Atheros QCA9561 SoC + QCA9880. Specification: - 775/650/258 MHz (CPU/DDR/AHB) - 128 MB of RAM (DDR2) - 16 MB of FLASH (SPI NOR) - 3T3R 2.4 GHz - 3T3R 5 GHz - 5x 10/100/1000 Mbps Ethernet - 7x LED, 2x button - UART header on PCB Flash instruction: 1. Upload openwrt-ath79-generic-tplink_archer-c7-v4-squashfs-factory.bin via Web interface Flash instruction using TFTP recovery: 1. Set PC to fixed ip address 192.168.0.66 2. Download openwrt-ath79-generic-tplink_archer-c7-v4-squashfs-factory.bin and rename it to ArcherC7v4_tp_recovery.bin 3. Start a tftp server with the file tp_recovery.bin in its root directory 4. Turn off the router 5. Press and hold Reset button 6. Turn on router with the reset button pressed and wait ~15 seconds 7. Release the reset button and after a short time the firmware should be transferred from the tftp server 8. Wait ~30 second to complete recovery. Signed-off-by: Oldřich Jedlička <oldium.pro@gmail.com>
* build: Fix missing device variables for artifactsPetr Štetiar2019-02-051-0/+1
| | | | | | | | | | | | | | It was reported to me today on IRC, that building of artifacts doesn't work properly if the concat_cmd references DEVICE_NAME variable. I've found out, that it's due to missing call of Device/Export in artifacts building code path, so this patch adds the missing Device/Export call which in turn exports DEFAULT_DEVICE_VARS into the artifacts environment. Fixes: 493c9a35516c ("build: Introduce building of artifacts") Tested-by: Oskari Lemmela <oskari@lemmela.net> Reported-by: Oskari Lemmela <oskari@lemmela.net> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: drop m25p,chunked-io from dtsChuanhong Guo2019-02-0562-62/+0
| | | | | | | | This option was a spi nor hack which is dropped in commit bcf4a5f474 ("ramips: remove chunked-io patch and set spi->max_transfer_size instead") Signed-off-by: Chuanhong Guo <gch981213@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [edit message]
* ramips: enable MT7610E 5GHz radio of MT7620a_MT7610e EVBDeng Qingfang2019-02-052-0/+9
| | | | | | This enables MT7610E of the EVB Signed-off-by: Deng Qingfang <dengqf6@mail2.sysu.edu.cn>
* ramips: add kmod-mt76x2 to WeVo 11AC NASJu Se Hoon2019-02-051-1/+1
| | | | | | | | The WeVo 11AC NAS has a MT7612E 802.11ac chip on the PCB. Signed-off-by: Ju Se Hoon <joosahoon@gmail.com> [renamed author from Albis-dev to real name, editted commit message] Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* toolchain/musl: update to version 1.1.21Christian Lamparter2019-02-053-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | <https://www.openwall.com/lists/musl/2019/01/21/8> "This release makes improvements with respect to default thread stack size, including increasing the default from 80k to 128k, increasing the default guard size from 4k to 8k, and allowing the default to be increased via ELF headers so that programs that need larger stacks can be build without source-level changes, using just LDFLAGS. Insufficient stack size for AIO threads on kernels that don't honor the constant MINSIGSTKSZ is also fixed. The glob core has been rewritten to fix inability to see past searchable-but-unreadable path components, and to avoid excessive stack usage and unnecessary syscalls. The tsearch AVL tree implementation has also been rewritten for better size and performance. The math library adds more native single-instruction implementations for arm, s390x, powerpc, and x86_64. Various bugs are fixed, including several possible deadlocks, one of which was a new regression in 1.1.20." detailed release notes can be found in the WHATSNEW file: <http://git.musl-libc.org/cgit/musl/tree/WHATSNEW#n1989> Tested-by: Koen Vandeputte <koen.vandeputte@ncentric.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ramips: dts: Unify naming of gpio-led nodesPetr Štetiar2019-02-05243-243/+243
| | | | | | | | | | | | | | In DTS Checklist[1] we're now demanding proper generic node names, as the name of a node should reflect the function of the device and use generic name for that[2]. Everybody seems to be copy&pasting from DTS files available in the repository today, so let's unify that naming there as well and provide proper examples. 1. https://openwrt.org/submitting-patches#dts_checklist 2. https://github.com/devicetree-org/devicetree-specification/blob/master/source/devicetree-basics.rst#generic-names-recommendation Signed-off-by: Petr Štetiar <ynezz@true.cz> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [split up]
* ramips: dts: Unify naming of gpio-keys nodesPetr Štetiar2019-02-05241-241/+241
| | | | | | | | | | | | | | In DTS Checklist[1] we're now demanding proper generic node names, as the name of a node should reflect the function of the device and use generic name for that[2]. Everybody seems to be copy&pasting from DTS files available in the repository today, so let's unify that naming there as well and provide proper examples. 1. https://openwrt.org/submitting-patches#dts_checklist 2. https://github.com/devicetree-org/devicetree-specification/blob/master/source/devicetree-basics.rst#generic-names-recommendation Signed-off-by: Petr Štetiar <ynezz@true.cz> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [split up]
* ipq40xx: fix ASUS RT-AC58U switch port numberingChristian Lamparter2019-02-051-5/+5
| | | | | | | | This patch fixes the ASUS' RT-AC58U port order by unifying the configuration with the NBG6617. Reported-by: Roberto Socrates (rtac58u-user on the forum) Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: consolidate 02_network board defaultsChristian Lamparter2019-02-051-58/+66
| | | | | | | | This patch splits the big board case switch in 02_network in two functions ipq40xx_setup_interfaces() and ipq40xx_setup_macs() just like ath79 and ramips do. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* brcm63xx: dts: Unify naming of gpio-led nodesPetr Štetiar2019-02-0579-79/+79
| | | | | | | | | | | | | | In DTS Checklist[1] we're now demanding proper generic node names, as the name of a node should reflect the function of the device and use generic name for that[2]. Everybody seems to be copy&pasting from DTS files available in the repository today, so let's unify that naming there as well and provide proper examples. 1. https://openwrt.org/submitting-patches#dts_checklist 2. https://github.com/devicetree-org/devicetree-specification/blob/master/source/devicetree-basics.rst#generic-names-recommendation Signed-off-by: Petr Štetiar <ynezz@true.cz> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [split up]
* brcm63xx: dts: Unify naming of gpio-keys nodesPetr Štetiar2019-02-0569-69/+69
| | | | | | | | | | | | | | In DTS Checklist[1] we're now demanding proper generic node names, as the name of a node should reflect the function of the device and use generic name for that[2]. Everybody seems to be copy&pasting from DTS files available in the repository today, so let's unify that naming there as well and provide proper examples. 1. https://openwrt.org/submitting-patches#dts_checklist 2. https://github.com/devicetree-org/devicetree-specification/blob/master/source/devicetree-basics.rst#generic-names-recommendation Signed-off-by: Petr Štetiar <ynezz@true.cz> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [split up]
* glibc: update to latest 2.27 commit (BZ #24155,BZ #24097)Hans Dedecker2019-02-041-2/+2
| | | | | | | | | | | | | | 2ebadb6451 x86-64 memcmp: Use unsigned Jcc instructions on size [BZ #24155] 3a5ae8db68 x86-64 strnlen/wcsnlen: Properly handle the length parameter [BZ #24097] 2c016ffa24 x86-64 strncpy: Properly handle the length parameter [BZ #24097] d8457edece x86-64 strncmp family: Properly handle the length parameter [BZ #24097] 55f8812858 x86-64 memset/wmemset: Properly handle the length parameter [BZ #24097] efc3714845 x86-64 memrchr: Properly handle the length parameter [BZ #24097] a4690969ed x86-64 memcpy: Properly handle the length parameter [BZ #24097] 6465327195 x86-64 memcmp/wmemcmp: Properly handle the length parameter [BZ #24097] 50117e00a1 x86-64 memchr/wmemchr: Properly handle the length parameter [BZ #24097] Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* ath10k-firmware: update Candela Tech firmware imagesKoen Vandeputte2019-02-041-16/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Jan 2, 2019 Rebase patches to make 9980 bisectable. * Jan 2, 2019 Fix scheduling related assert when wal-peer is deleted with pending tx buffers (bug 54, and others) * Jan 7, 2019: Fix specifying retransmits for AMPDU frames. It was previously ignored since it is a 'software' retransmit instead of a hardware retransmit. * Jan 9, 2019 Fix potential way to get zero rates selected (and then assert) * Jan 18, 2019 pfsched has specific work-around to just return if we find invalid flags AND if we are in an out-of-order situation. Maybe this is last of the pfsched related issues (bug 54 and similar). * Jan 24, 2019 The rcSibUpdate method can be called concurrently with IRQ tx-completion callback, and that could potentially allow the tx-completion callback to see invalid state and assert or otherwise mess up the rate-ctrl logic. So, disable IRQs in rcSibUpdate to prevent this. Related to bug 58. * Jan 28, 2019 Ensure that cached config is applied to ratectrl objects when fetched from the cache. This should fix part of bug 58. * Jan 28, 2019 Ensure that ratectrl objects from cachemgr are always initialized. This fixes another part of bug 58. * Jan 30, 2019 Better use of temporary rate-ctrl object. Make sure it is initialized, simplify code path. This finishes up porting forward similar changes I made for wave-1 firmware long ago, and fixes another potential way to hit bug-58 issues. * Jan 30, 2019 Cachemgr did not have a callback for when memory was logically freed. This means that peers could keep stale references to rate-ctrl objects that were in process of being DMA'd into to load a different peer's rate-ctrl state. This was causing the bugcheck logic to fail early and often, and I suspect it might be a root cause of bug 58 as well. The fix is to add a callback and set any 'deleted' memory references to NULL so that we cannot access it accidentally. Thanks to excellent logs and patience from the bug-58 reporter! Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* toolchain/gcc: backport FORTIFY patch to 5.5.0Hans Dedecker2019-02-041-0/+1092
| | | | | | | | | | | | Commit e61061a0886e2d0d6b075d75ae9b53d0a6bc9042 added support for hardening options in the toolchain. However this breaks the gcc5.5.0 compilation in case FORTIFY_SOURCE is set different from FORTIFY_SOURCE_NONE as reported in [1]. Fix this by backporting the upstream patch which fixes this in later gcc versions [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?format=multiple&id=61164 Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-02 00:59:30 +0000