aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* rt2x00: add throughput LED triggerDavid Bauer2019-12-301-0/+44
| | | | | | | | | | This adds a (currently missing) throughput LED trigger for the rt2x00 driver. Previously, LED triggers had to be assigned to the netdev, which was limited to a single VAP. Signed-off-by: David Bauer <mail@david-bauer.net> Tested-by: Christoph Krapp <achterin@googlemail.com> (cherry picked from commit 985ec835aea100e9245baaef8ebb15628601fe5e)
* mac80211: fix build without CONFIG_PCIFelix Fietkau2019-12-291-1/+1
| | | | | Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry-picked from commit fa37dbbc43db23a0ce7256f47943f38a1dcc9027)
* mac80211: add patch to include local BSS rx time in survey informationFelix Fietkau2019-12-282-2/+79
| | | | | Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry-picked from commit 6a3739dc42c1d9626e5784d9316c56962bd8f016)
* mac80211: add pcie apsm backport changesFelix Fietkau2019-12-282-0/+67
| | | | | | | Required for newer versions of mt76 Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry-picked from commit d64daf7026ce47788f12130462a3107bdab8718f)
* ramips: remove bogus ralink,mtd-eeprom with offset 0x4Adrian Schmutzler2019-12-286-6/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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> (cherry picked from commit 09d38a3bc328d122b0d84fcf6bb53d2bce7373b6)
* ipq40xx: use ath10k-ct-smallbuffers for 128 MiB devicesPaul Fertser2019-12-261-1/+3
| | | | | Signed-off-by: Paul Fertser <fercerpav@gmail.com> (cherry picked from commit 0b7d779dcfc57507ab1d06ce6f1052d25e9de017)
* kernel: bump 4.14 to 4.14.160Hauke Mehrtens2019-12-2511-18/+18
| | | | | | | | | Refreshed all patches. Compile-tested on: ipq40xx, ath79 Runtime-tested on: ipq40xx Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 4.14 to 4.14.159Koen Vandeputte2019-12-2451-281/+153
| | | | | | | | | | | | | | | 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> (cherry picked from commit 80f06cb601160534f20e61d476dcedba77d5a47d)
* 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> (cherry picked from commit 1ac627024de916eb157659caf49f93fa89d3b19a)
* fstools: update to latest git HEADJo-Philipp Wich2019-12-231-3/+3
| | | | | | | | b4e25d5 libblkid-tiny: fix symbol collision with full libblkid Fixes: FS#2691, FS#2692 Signed-off-by: Jo-Philipp Wich <jo@mein.io> (cherry picked from commit 5f4244150f99d7bf72a96ec4d9c1055386e66b53)
* fstools: update to latest git HEADRafał Miłecki2019-12-231-3/+3
| | | | | | | | | | | | | 111a43f libblkid-tiny: vfat: Change parsing label in special cases f43a1aa libblkid-tiny: vfat: Fix reading labels which starts with byte 0x05 157924d libblkid-tiny: add blkid_probe_set_id_label() stub 0c5761f libblkid-tiny: use separated buffer for each block device read b82c5c1 libblkid-tiny: add functions for allocating & freeing probe struct 12851d6 blockd: don't flush devices list on "hotplug" call 5ea47fe blockd: fix vlist memory corruption Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 4ebc9dc9c4faf8d9abc4197a74b892a66d9c1bcb)
* fstools: bump to version 2019-11-03Yousong Zhou2019-12-231-3/+3
| | | | | | | | | | | | | 2f2a09a block: mount_device: err log only when mp deviates from spec da4edc1 block: mount_device: skip extroot earlier 32c3126 block: mount_action: handle mount/umount deps fb0700f block: support hierarchical mount/umount 1212b5b block: umount: skip / unless -a is given eda8b3f block: use fsck.fat instead of dosfsck d05276d libblkid-tiny: ntfs: fix use-after-free Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com> (cherry picked from commit e4af39d56395738d86daa4babb379ab605b4d277)
* fstools: update to latest Git HEADHauke Mehrtens2019-12-231-3/+3
| | | | | | | | | 4327ed4 mkdev: Avoid out of bounds read 9b3eb63 libblkid-tiny: use blkid_probe_set_utf8label for label set c9d0462 libblkid-tiny: adds blkid_probe_set_utf8label support Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> (cherry picked from commit 541a3210707d1fc4b439ac61dc06816dcec2ab10)
* libubox: bump to version 2019-10-29Yousong Zhou2019-12-231-3/+3
| | | | | | | | It contains a single change to vlist.h header file: "vlist: add more macros for loop iteration". This is needed for newer version of fstools Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com> (cherry picked from commit 51e76247762d265d4a4aac33456876b83b0cca25)
* libubox: update to latest git HEADRoman Yeryomin2019-12-231-3/+3
| | | | | | | eb30a03 libubox, jshn: add option to write output to a file Signed-off-by: Roman Yeryomin <roman@advem.lv> (cherry picked from commit c0e7ec91a0927002942631bbc995b90f5f7dd7ed)
* kernel: remove LINUX_4_9 dependency of kmod-daxSungbo Eo2019-12-231-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | This patch resolves recursive dependency warning on a feed package: $ make defconfig Collecting package info: done tmp/.config-package.in:104721:error: recursive dependency detected! For a resolution refer to Documentation/kbuild/kconfig-language.txt subsection "Kconfig recursive dependency limitations" tmp/.config-package.in:104721:symbol PACKAGE_nfs-kernel-server depends on NFS_KERNEL_SERVER_V4 For a resolution refer to Documentation/kbuild/kconfig-language.txt subsection "Kconfig recursive dependency limitations" feeds/packages/net/nfs-kernel-server/Config.in:4:symbol NFS_KERNEL_SERVER_V4 depends on PACKAGE_nfs-kernel-server # # configuration written to .config # 19.07 branch uses kernel 4.14 only, so CONFIG_LINUX_4_9 symbol is not needed anyway. Ref: https://github.com/openwrt/packages/issues/10490 Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* scripts/dowload.pl: add archive.apache.org to apache mirror listJiri Kastner2019-12-231-0/+1
| | | | | | | | | apache mirrors holds only latest releases, to download older releases, one must use archive.apache.org to get them. Signed-off-by: Jiri Kastner <cz172638@gmail.com> (cherry picked from commit dc34c695c4faa46efc6e2367a2ba06a47caa4840)
* kernel: fix *-gpio-custom module unloadingSungbo Eo2019-12-234-6/+6
| | | | | | | | | | | | | | | | | | | | | | Unloading and reloading the modules fails, as platform_device_put() does not release resources fully. root@OpenWrt:/# insmod i2c-gpio-custom bus0=0,18,0,5 [ 196.860620] Custom GPIO-based I2C driver version 0.1.1 [ 196.871162] ------------[ cut here ]------------ [ 196.880517] WARNING: CPU: 0 PID: 1365 at fs/sysfs/dir.c:31 0x80112158 [ 196.893431] sysfs: cannot create duplicate filename '/devices/platform/i2c-gpio.0' ... [ 197.513200] kobject_add_internal failed for i2c-gpio.0 with -EEXIST, don't try to register things with the same name in the same directory. This patch fixes it by replacing platform_device_put() to platform_device_unregister(). Fixes: da7740853715 ("i2c-gpio-custom: minor bugfix") Fixes: 3bc81edc70e8 ("package: fix w1-gpio-custom package (closes #6770)") Signed-off-by: Sungbo Eo <mans0n@gorani.run> (cherry picked from commit a22b7a60d98836343c4f7b9ec0fcae68d9131522)
* cmake: Install host packages to lib instead of lib64Rosen Penev2019-12-231-0/+1
| | | | | | | | | | Several CMake packages such as log4cplus and protobuf(-c) install to lib64 instead of lib on some hosts. This completely breaks rpath linking. Override it globally to avoid fixing each package individually. Signed-off-by: Rosen Penev <rosenp@gmail.com> Tested-by: Sebastian Kemper <sebastian_ml@gmx.net> (cherry picked from commit 383abffb1179a142b4c8f86559baad5b24d391c3)
* adb: fix for SuperSpeed devicesBjørn Mork2019-12-233-2/+41
| | | | | | | | | | | | | | | The USB descriptor parsing in adb fails to detect SuperSpeed devices because of the SuperSpeed Endpoint Companion Descriptor. This cherry-picks the upstream fix for the problem. Unfortunately there never were a release with this fix before the conversion to C++, so upgrading to a newer version isn't an option. This makes adb work with SuperSpeed devices like the Sierra Wireless EM7565. Tested and verified. Signed-off-by: Bjørn Mork <bjorn@mork.no> (cherry picked from commit d034a1f4577108a465e8347d11a51dc0e5a29298)
* toolchain/gcc: Backport patch to fix unconditional MULTIARCH_DIRNAMEJeffery To2019-12-231-0/+30
| | | | | | | | | | | | | | | | | | | This backports the patch for GCC PR target/89587 (gcc's rs6000 configuration unconditionally sets MULTIARCH_DIRNAME, even when multiarch is disabled). This currently affects apm821xx and may cause issues when cross-compiling packages, e.g. Python 3[1]. This includes patches for GCC 8 (with the changelog diff removed); this change is already included in GCC 9.2 and 7.5. [1]: https://github.com/openwrt/packages/issues/10552 Signed-off-by: Jeffery To <jeffery.to@gmail.com> [Removed patch for GCC 7.4.0, GCC 7.5.0 already contains this] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> (cherry picked from commit c102f702e7dc976c2ad2c04c0ce4462373e62365)
* toolchain/gcc: correct the check expr for newer clangYorkie Liu2019-12-231-1/+1
| | | | | | | | This fixes gcc build error within clang 11.0, it tweaks the version string from LLVM to clang. Signed-off-by: Yorkie Liu <yorkiefixer@gmail.com> (cherry picked from commit 65a561fd0919eafff2363ae8324db64be2a57f77)
* lantiq: fix phys ledAleksander Jan Bajkowski2019-12-231-2/+2
| | | | | | | | | led2l and led2h value is incorrectly set by led3l and led3h. Bug was introduced in commit: 863e79f8d5544a8a884375d7e867f350fddca9b9 Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl> Fixes: 863e79f8d554 ("lantiq: add support for kernel 4.9") (cherry picked from commit 692390225d76de8f2daf582454e74942b82d090a)
* uhttpd: reset PKG_RELEASEJo-Philipp Wich2019-12-221-1/+1
| | | | | Signed-off-by: Jo-Philipp Wich <jo@mein.io> (cherry picked from commit 97af1fc979d0683649c6bea8a9245a6a9fa5413a)
* uhttpd: update to latest Git HEADJo-Philipp Wich2019-12-221-3/+3
| | | | | | | 5f9ae57 client: fix invalid data access through invalid content-length values Signed-off-by: Jo-Philipp Wich <jo@mein.io> (cherry picked from commit f34f9a414dd32311bda950776eb77e63c0c772cb)
* ar71xx: fix MAC address setup for TL-WDR4300 boardSungbo Eo2019-12-212-1/+5
| | | | | | | | | | | | | | | | | | The current ethernet MAC address setup of TL-WDR4300 board is different from the setup of stock firmware: OpenWrt: lan = label_mac -2, wan = label_mac -2 stock: lan = label_mac, wan = label_mac +1 This patch applies to all devices using TL-WDR4300 board: TL-WDR3600 v1 TL-WDR4300 v1 TL-WDR4300 v1 (IL) TL-WDR4310 v1 Mercury MW4530R v1 Signed-off-by: Sungbo Eo <mans0n@gorani.run> (cherry picked from commit 9b02d32e34df2bb8821ec6f08f525bee22d0d1ba)
* ath79: fix MAC address setup for TP-Link TL-WDR3600/TL-WDR4300Sungbo Eo2019-12-212-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | The current ethernet MAC address setup of TL-WDR4300 board is different from the setup of stock firmware: OpenWrt: lan = label_mac -2, wan = label_mac -2 stock: lan = label_mac, wan = label_mac +1 The full address assignment is as follows: LAN label WAN label + 1 5G label 2G label - 1 This patch changes all devices using TL-WDR4300 board: TL-WDR3600 v1 (checked on device) TL-WDR4300 v1 (checked on device) TL-WDR4300 v1 (IL) Signed-off-by: Sungbo Eo <mans0n@gorani.run> [rephrase/extend commit title/message, backport] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit a4260eaab7744c8e3f1f7a62a61aab5e3b562342)
* ramips: fix USB LED for Belkin F9K1109v1Sungbo Eo2019-12-201-1/+1
| | | | | | | | | | | | | | | Device support for Belkin F9K1109v1 was added using set_usb_led() although this was removed in 772b27c20736 ("ramips: set F5D8235 v1 usb led trigger via devicetree"). Use ucidef_set_led_usbport() instead. Fixes: f2c83532f92c ("ramips: add support for Belkin F9K1109v1") Signed-off-by: Sungbo Eo <mans0n@gorani.run> [rephrase commit title and message, backport] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 1f455418ef1ea67fda710e1b86a9e021bb4a2413)
* mac80211: brcm: add support for BCM4359 SDIO chipsetRafał Miłecki2019-12-197-0/+519
| | | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 17e2246eca901fec79fbac5b7a90f68f60785c4e)
* mac80211: brcm: backport 5.5 and 5.6 kernel patchesRafał Miłecki2019-12-1910-1/+325
| | | | | | | | | | This update doesn't include: 3b1e0a7bdfee brcmfmac: add support for SAE authentication offload be898fed355e brcmfmac: send port authorized event for FT-802.1X due to nl80211 dependencies. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit c3aa33bf705027751b344bc668541e5d08ed9495)
* ath79: migrate LED paths of TL-WDR4300 boardSungbo Eo2019-12-171-1/+4
| | | | | | | | | | | | | | TL-WDR4300 board uses only green LED names in DTSI. This patch adds migration for them. The actual LED colors on the devices have been reported to vary across subrevisions (v1.x). Despite, the USB LEDs on the back might have different color than the other LEDs on the front. Signed-off-by: Sungbo Eo <mans0n@gorani.run> [extended commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 01d39cd18c4035e362f179548cd2c051aac03042)
* malta: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-171-2/+0
| | | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit e964338110526b3692847769343816cd2f853d18)
* sunxi: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-171-2/+0
| | | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit 2105354968ed9698709d220ec446b6d9c27da3a5)
* layerscape: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-172-4/+0
| | | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit 414d027ae8ac05ec9aa06bc50afd5458c2da02fc)
* kirkwood: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-171-2/+0
| | | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit 411e824ec371a322b975e90af5a1f32760a61720)
* at91: disable legacy PTYs and virtual terminalsDaniel Golle2019-12-171-6/+0
| | | | | | | | | | Enabling legacy PTYs causes problems with procd-hotplug. And as this is a headless target, no need to have virtual terminals. Remove corresponding kernel config options, they are disabled in generic kernel config. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit c1db4d9c5655e3c74ffdbb6a6a3367269f65c55f)
* mpc85xx: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-171-2/+0
| | | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit d0d7f5d9e49b8632f372c92e0339895fa10904f9)
* uml: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-172-4/+0
| | | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit dcf48fda054c4bbc52f6106250a7e06ab8f5cbdd)
* oxnas: disable legacy PTYs and virtual terminalsDaniel Golle2019-12-171-6/+0
| | | | | | | | | | Enabling legacy PTYs causes problems with procd-hotplug. And as this is a headless target, no need to have virtual terminals. Remove corresponding kernel config options, they are disabled in generic kernel config. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit c881769a558b38ddd5977a50b67cd32c6d3f7d5e)
* odhcpd: optimize syslog priority valuesHans Dedecker2019-12-161-3/+3
| | | | | | e53fec8 treewide: optimize syslog priority values Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* lantiq: remove redundant WiFi LED on FRITZ!Box 7320Manuel Kock2019-12-141-3/+0
| | | | | | | | | | The led wireless trigger is already set correctly to phy0tpt through the alias in the device tree. Signed-off-by: Manuel Kock <github.web@manu.li> [rephrased commit title] Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 509894cffb7ec24ac21a381bed3c035efce42aeb)
* mpc85xx: add support for Enterasys WS-AP3710iDavid Bauer2019-12-147-0/+310
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware -------- SoC: NXP P1020 (2x e500 @ 800MHz) RAM: 256M DDR3 (Micron) FLASH: 32M NOR (Spansion S29GL128S) BTN: 1x Reset WiFi: 1x Atheros AR9590 2.4 bgn 3x3 2x Atheros AR9590 5.0 an 3x3 ETH: 1x Gigabit Ethernet (Atheros AR8033) LED: System (green/red) - Radio{0,1} (green) LAN (connected to PHY) - GE blue - FE green Serial is a Cisco-compatible RJ45 next to the ethernet port. 115200-N-8 are the settings for OS and U-Boot. Installation ------------ 1. Grab the OpenWrt initramfs, rename it to 01C8A8C0.img. Place it in the root directory of a TFTP server and serve it at 192.168.200.200/24. 2. Connect to the serial port and boot the AP. Stop autoboot in U-Boot by pressing Enter when prompted. Credentials are identical to the one in the APs interface. By default it is admin / new2day. 3. Set the bootcmd so the AP can boot OpenWrt by executing $ setenv boot_openwrt "setenv bootargs; cp.b 0xee000000 0x1000000 0x1000000; bootm 0x1000000" $ setenv bootcmd "run boot_openwrt" $ saveenv If you plan on going back to the vendor firmware - the bootcmd for it is stored in the boot_flash variable. 4. Load the initramfs image to RAM and boot by executing $ tftpboot 0x1000000 192.168.200.200:01C8A8C0.img; bootm 5. Make a backup of the "firmware" partition if you ever wish to go back to the vendor firmware. 6. Upload the OpenWrt sysupgrade image via SCP to the devices /tmp folder. 7. Flash OpenWrt using sysupgrade. $ sysupgrade -n /tmp/openwrt-sysupgrade.bin Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 16b01fb1b9c99513c318109bef96a1a3545c57a0)
* glibc: update to latest 2.27 commit (BZ #2503, BZ #2504)Hans Dedecker2019-12-141-2/+2
| | | | | | | | bef0b1cb31 libio: Disable vtable validation for pre-2.1 interposed handles [BZ #25203] 4d5cfeb510 rtld: Check __libc_enable_secure before honoring LD_PREFER_MAP_32BIT_EXEC (CVE-2019-19126) [BZ #25204] 92f04eedb5 mips: Force RWX stack for hard-float builds that can run on pre-4.8 kernels Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* glibc: backport fix for regexec buffer read overrunAlin Nastac2019-12-141-0/+26
| | | | | | | | | | | | | | | | | | | Problem found by AddressSanitizer[1]: Latest `grep` (git commit 1019e6e) compiled with asan may cause a heap-buffer-overflow when `-i` is specified. ./grep -i '\(\(\)*.\)*\(\)\(\)\1' /bin/chvt ================================================================= ==16206==ERROR: AddressSanitizer: heap-buffer-overflow on address 1. https://debbugs.gnu.org/34140 Ref: https://sourceware.org/bugzilla/show_bug.cgi?id=24114 Signed-off-by: Alin Nastac <alin.nastac@gmail.com> [commit title and description facelift] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* glibc: update to latest 2.27 commit (BZ#23637)Hans Dedecker2019-12-141-2/+2
| | | | | | | | | | | | 5b4f7382af Add undef to fix test failure. 9456483fb2 Improve performance of memmem 373f8b06a3 Improve performance of strstr 4ec1b9e913 Fix strstr bug with huge needles (bug 23637) ecd6271ed8 Speedup first memmem match bba6b9288f Simplify and speedup strstr/strcasestr first match 7a4da6ef7a Improve strstr performance Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* glibc: update to latest 2.27 commit (BZ #24228, BZ #24744, BZ #24699)Hans Dedecker2019-12-141-2/+2
| | | | | | | | | | | | | | | | | | | | | | 5f0d2e0491 [AArch64] Add ifunc support for Ares e6b7252040 aarch64,falkor: Use vector registers for memcpy c74b884f70 aarch64,falkor: Ignore prefetcher tagging for smaller copies 0fc5934ebd aarch64/strncmp: Use lsr instead of mov+lsr e0a0bd3acc aarch64/strncmp: Unbreak builds with old binutils 638caf3000 aarch64: Improve strncmp for mutually misaligned inputs d5f45a29ff aarch64/strcmp: fix misaligned loop jump target 7f690fafad aarch64: Improve strcmp unaligned performance 40df047b3b aarch64: Fix branch target to loop16 062139f233 aarch64: Optimized memcmp for medium to large sizes f3e2add213 aarch64: Use the L() macro for labels in memcmp 22bd3ab40e posix: Fix large mmap64 offset for mips64n32 (BZ#24699) bdd16894aa aarch64: handle STO_AARCH64_VARIANT_PCS 0b48caab9a aarch64: add STO_AARCH64_VARIANT_PCS and DT_AARCH64_VARIANT_PCS 949da7f2fd io: Remove copy_file_range emulation [BZ #24744] f056ac8363 libio: do not attempt to free wide buffers of legacy streams [BZ #24228] 5f90e009b1 NEWS: add entries for bugs 22964, 24180, and 24531 Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* ath79: add support for TP-Link TL-WDR4300 v1 (IL)Adrian Schmutzler2019-12-134-0/+21
| | | | | | | | | The TL-WDR4300 v1 sold in Israel has a different TPLINK_HWID. Thanks to Josh4300 for testing on device. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit c642a97aa6b51352a718449cd715b92f94af4a5d)
* ramips: allow JCG_MAXSIZE in kiB in Build/jcg-headerAdrian Schmutzler2019-12-132-2/+4
| | | | | | | | | | | | | | | This allows JCG_MAXSIZE to be specified in kilobytes. This makes this value more consistent and easier comparable with other size variables. This also changes the only occurence of the variable, for Cudy WR1000. This is backported to 19.07 for convenience, as other developers backporting device support might not be aware that JCG_MAXSIZE in kilobytes would not work there. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 0bf4d681d4f2e4bd3c3a61e7fe5dca2a40b1902f)
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-03 08:59:49 +0000