[OpenWrt-Devel] Patch iwinfo to detect wrt3200acm chipsets

A small patch to iwinfo is needed to properly detect and report the Marvell 88W8964 and 88W8887 chipsets in the wrt3200acm. This trivial patch against the latest iwinfo git tree works for me. Signed-off-by: Erik Andersen --- diff --git a/hardware.txt b/hardware.txt index

Re: [OpenWrt-Devel] [LEDE-DEV] Wifi-related kernel-oops on mt7621 after 4.14 update

> [45729.251928] PC is at tcp_push+0x44/0xfc This should be fixed in kernel 4.14.32. Try the latest snapshot. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [LEDE-DEV] Wifi-related kernel-oops on mt7621 after 4.14 update

On 04/12/2018 07:02 AM, John Crispin wrote: On 12/04/18 12:42, Kristian Evensen wrote: Hello, I have recently updated some ramips mt7621-devices (ZBT WG3526) to the latest nightly. Almost everything seems to work fine, but using either wifi interface in client mode seems triggers an oops.

[OpenWrt-Devel] [PATCH] mac80211: pass hostapd control socket to mesh-mode supplicant

Unlike when operating in Ad-Hoc mode, we apparently need to pass the hostapd control socket interface to wpa_supplicant when using 802.11s mesh mode. There also seems to still be something wrong with the logic setting channel and (v)htmode parameters when using AP + mesh... Signed-off-by: Daniel

Re: [OpenWrt-Devel] [PATCH] brcm2708: add squashfs rootfs image

On Thu, Mar 29, 2018 at 02:22:48AM +0200, Daniel Golle wrote: > On Tue, Mar 27, 2018 at 07:42:18PM +0200, Christian Lamparter wrote: > > This patch adds a image with squashfs as the root filesystem. > > A rootfs_data partition will be generated on the first boot > > and placed inside the rootfs

Re: [OpenWrt-Devel] Wifi-related kernel-oops on mt7621 after 4.14 update

Hi, On Thu, Apr 12, 2018 at 1:02 PM, John Crispin wrote: > try enabling KALLSYMS to get a verbose stack trace. Thanks for the pointer. I compiled a new image KALLSYMS, but now I am not able to reproduce the error. Perhaps there was something dirty in my build directory. I will

[OpenWrt-Devel] [PATCH] hostapd: update to git snapshot of 2018-04-08

And import patch to allow 802.11s mesh on DFS channels, see also http://lists.infradead.org/pipermail/hostap/2018-April/038418.html Signed-off-by: Daniel Golle --- package/network/services/hostapd/Makefile | 6 +- ...1-mesh-factor-out-mesh-join-function.patch | 219

Re: [OpenWrt-Devel] Wifi-related kernel-oops on mt7621 after 4.14 update

On 12/04/18 12:42, Kristian Evensen wrote: Hello, I have recently updated some ramips mt7621-devices (ZBT WG3526) to the latest nightly. Almost everything seems to work fine, but using either wifi interface in client mode seems triggers an oops. I see two different oops-messages: Message 1:

Re: [OpenWrt-Devel] Boot Time Reduction

On 12/04/18 06:26, Arjav Parikh wrote: Hi, > (...) Now as mentioned in previous mail only at that two locations I see some process consuming lot of time. Is it possible to reduce the time consumed by the process? Isn't the long time between pre-init and ubi mount due to the lengthy

[OpenWrt-Devel] Wifi-related kernel-oops on mt7621 after 4.14 update

Hello, I have recently updated some ramips mt7621-devices (ZBT WG3526) to the latest nightly. Almost everything seems to work fine, but using either wifi interface in client mode seems triggers an oops. I see two different oops-messages: Message 1: [ 66.442802] CPU 1 Unable to handle kernel