[OpenWrt-Devel] [PATCH] wireguard: bump to 20180519

* chacha20poly1305: add mips32 implementation "The OpenWRT Commit" - this significantly speeds up performance on cheap plastic MIPS routers, and presumably the remaining MIPS32r2 super computers out there. * timers: reinitialize state on init * timers: round up instead of down in slack_time *

[OpenWrt-Devel] [PATCH] ar71xx: add support for GL.iNet GL-AR750S

This patch adds supports for GL-AR750S. Specification: - SOC: QCA9563 (775MHz) - Flash: 16 MiB (W25Q128FVSG) - RAM: 128 MiB DDR2 - Ethernet: 2x 1Gbps LAN + 1x 1Gbps WAN - Wireless: 2.4GHz (bgn) and 5GHz (ac) - USB: 1x USB 2.0 port - Button: 1x switch button, 1x reset button - LED: 3x LEDS (green)

[OpenWrt-Devel] [PATCH] libevent2: update to version 2.1.8

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- This version is compatible with

[OpenWrt-Devel] [PATCH] openssl: Upgrade to 1.1.0h

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- This version brings major changes

Re: [OpenWrt-Devel] Build failure ath10k-CT without mac80211 debug

On 05/18/2018 02:34 AM, Koen Vandeputte wrote: Hi Ben, I'm trying to build todays OpenWrt master with following options: - ath10k-ct - qca988x-ct-htt When disabling this option (CONFIG_PACKAGE_MAC80211_DEBUGFS), I'm getting the build errors below. Is it *really* required to have this

[OpenWrt-Devel] [PATCH] mtd: skip bad blocks when writing

--- package/system/mtd/src/jffs2.c | 10 ++ 1 file changed, 10 insertions(+) diff --git a/package/system/mtd/src/jffs2.c b/package/system/mtd/src/jffs2.c index b432f64ac0..5bf3eec328 100644 --- a/package/system/mtd/src/jffs2.c +++ b/package/system/mtd/src/jffs2.c @@ -308,6 +308,16 @@ int

[OpenWrt-Devel] [PATCH] fstools: Add the new options available in the menuconfig

The mounting flags and the extra mounting options are available in the menuconfig. Signed-off-by: Pierre Lebleu --- package/system/fstools/Makefile | 16 1 file changed, 16 insertions(+) diff --git a/package/system/fstools/Makefile

[OpenWrt-Devel] [PATCH 1/2] fstools: allow to customize the mount option for the overlay

In order to give some extra options (specific to the filesystem used), a new CMake option (eg: CMAKE_OVL_MOUNT_OPTION) has been added. Example: cmake -DCMAKE_OVL_MOUNT_OPTION="compr=zlib" Signed-off-by: Pierre Lebleu --- CMakeLists.txt | 6 ++

[OpenWrt-Devel] [PATCH 2/2] fstools: allow to customize the mount flags for the overlay

In order to customize the mount flags, a new CMake option (eg: CMAKE_OVL_MOUNT_FLAGS) has been added. Example: cmake -DCMAKE_OVL_MOUNT_FLAGS="MS_RELATIME" Signed-off-by: Pierre Lebleu --- CMakeLists.txt | 6 ++ libfstools/overlay.c | 2 +- 2 files changed, 7

[OpenWrt-Devel] [PATCH] ar71xx: add support for GL.iNet GL-AR750S

This patch adds supports for GL-AR750S. Specification: - SOC: QCA9563 (775MHz) - Flash: 16 MiB (W25Q128FVSG) - RAM: 128 MiB DDR2 - Ethernet: 2x 1Gbps LAN + 1x 1Gbps WAN - Wireless: 2.4GHz (bgn) and 5GHz (ac) - USB: 1x USB 2.0 port - Button: 1x switch button, 1x reset button - LED: 3x LEDS (green)

Re: [OpenWrt-Devel] OpenWRT mtd tooling vs mtd-utils

Thanks for the clarification! Just out of curiosity, is there a specific reason why OpenWRT uses its own formatting utility here instead of using the tools from mtd-utils? - Original Message - From: "Jo-Philipp Wich" To: "David Oberhollenzer" ,

Re: [OpenWrt-Devel] [PATCH 2/2] wpad-mini: Enable 802.11r

On Fri, 2018-05-18 at 09:39 +0100, David Woodhouse wrote: > With so many devices having dual 2.4GHz + 5GHz radios, this isn't a > particularly esoteric use case any more. Luci offers it by default too, > with no check for whether wpad is actually going to do it or not AFAICT. I was wrong about

Re: [OpenWrt-Devel] OpenWRT mtd tooling vs mtd-utils

Hello David, this was actually my fault. I didn't pay close attention and assumed the code to be related to the kernel MTD subsystem. Only now after your mail I realized that it affects the OpenWrt specific formatting utility. I am very sorry for the confusion caused. Kind regards, Jo

[OpenWrt-Devel] OpenWRT mtd tooling vs mtd-utils

Hi all, I'm the current maintainer of upstream mtd-utils. Earlier today, Levente tried to submit a patch for a "package/system/mtd/src/jffs2.c" on the mtd mailing list: http://lists.infradead.org/pipermail/linux-mtd/2018-May/081087.html I took a brief look a the OpenWRT source tree and to me,

[OpenWrt-Devel] Build failure ath10k-CT without mac80211 debug

Hi Ben, I'm trying to build todays OpenWrt master with following options: - ath10k-ct - qca988x-ct-htt When disabling this option (CONFIG_PACKAGE_MAC80211_DEBUGFS),  I'm getting the build errors below. Is it *really* required to have this enabled for the driver to function properly? Is

[OpenWrt-Devel] [PATCH 2/2] wpad-mini: Enable 802.11r

With so many devices having dual 2.4GHz + 5GHz radios, this isn't a particularly esoteric use case any more. Luci offers it by default too, with no check for whether wpad is actually going to do it or not AFAICT. On my test build the size increase is relatively modest: textdata bss

[OpenWrt-Devel] [PATCH 1/2] hostapd: fix IEEE 802.11r (fast roaming) defaults

From: devianceluka Use ft_psk_generate_local=1 by default, as it makes everything else fairly trivial. All of the r0kh/r1kh and key management stuff goes away and hostapd fairly much does it all for us. We do need to provide nas_identifier, which can be derived from the