Re: [OpenWrt-Devel] Broken GPIO on MT7620 after commit 34ca34b32b02

Hi, On Tue, May 22, 2018 at 1:33 PM, Rosen Penev wrote: > Looks like it's this commit: > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/staging/mt7621-mmc?h=next-20180517=b734735fcaca60e8f07b040cd8a700f6fabe5b39 > > Please try reverting.

Re: [OpenWrt-Devel] Broken GPIO on MT7620 after commit 34ca34b32b02

On Tue, May 22, 2018 at 7:45 AM, Kristian Evensen wrote: > Hi, > > On Tue, May 22, 2018 at 4:33 PM, John Crispin wrote: >> what exactly is the issue ? breaking compat means that rosen either needs to >> fix the regression or we need to revert the

[OpenWrt-Devel] [PATCH v2] brcm47xx: add switch port mapping to Asus WL-500W

Switch ports 0..3 are connected to external ports LAN{1..4} in sequence, switch port 4 is not used, and switch port 5 is connected to the CPU. The WAN port is attached to the CPU's second network interface; it has no connection to the internal switch. Reuse the "Dell TrueMobile 2300" entry, which

Re: [OpenWrt-Devel] [PATCH v2 2/2] fstools: allow the mounting with full access time accounting

On 22/05/18 19:04, Pierre Lebleu wrote: In order to allow the mounting of the filesystem with full access time accounting, a new CMake option (eg: CMAKE_OVL_MOUNT_FULL_ACCESS_TIME) has been added. Signed-off-by: Pierre Lebleu --- v2: change the option name

Re: [OpenWrt-Devel] [PATCH v2 1/2] fstools: allow to compress the filesystem

On 22/05/18 19:04, Pierre Lebleu wrote: In order to allow the mounting of the filesystem with the zlib compression, a new CMake option (eg: CMAKE_OVL_MOUNT_COMPRESS_ZLIB) has been added. Signed-off-by: Pierre Lebleu --- v2: change the option name CMakeLists.txt

Re: [OpenWrt-Devel] [PATCH] arc770: bump kernel to 4.14

On 22/05/18 17:56, Evgeniy Didin wrote: Hello, Now arc770 is no longer marked as "source-only". Could you add this commit to master branch please? Best regards, Evgeniy Didin On Tue, 2018-04-17 at 15:25 +0300, didin wrote: Hello, This patch, as I see in patchwork, is accepted but I can't

[OpenWrt-Devel] [PATCH 2/2] kmod-sched-cake: RFC latest cake

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 bumps to the latest &

[OpenWrt-Devel] [PATCH 1/2] iproute2: RFC update cake support

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 bumps to the latest &

[OpenWrt-Devel] [PATCH 0/2] RFC bumps to latest cake

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 bumps to the latest &

[OpenWrt-Devel] [PATCH v2 2/2] fstools: allow the mounting with full access time accounting

In order to allow the mounting of the filesystem with full access time accounting, a new CMake option (eg: CMAKE_OVL_MOUNT_FULL_ACCESS_TIME) has been added. Signed-off-by: Pierre Lebleu --- v2: change the option name CMakeLists.txt | 6 ++ libfstools/overlay.c |

Re: [OpenWrt-Devel] Broken GPIO on MT7620 after commit 34ca34b32b02

On Tue, May 22, 2018 at 7:33 AM, John Crispin wrote: > > > On 22/05/18 16:18, Kristian Evensen wrote: >> >> On Sun, May 20, 2018 at 10:26 PM, Rosen Penev wrote: Bisecting further is hard, since the commit is a combination of (a lot of) clean-up

Re: [OpenWrt-Devel] [PATCH] arc770: bump kernel to 4.14

Hello, Now arc770 is no longer marked as "source-only".  Could you add this commit to master branch please? Best regards,  Evgeniy Didin On Tue, 2018-04-17 at 15:25 +0300, didin wrote: > Hello, > > This patch, as I see in patchwork, is accepted but I can't  > find it in

Re: [OpenWrt-Devel] Broken GPIO on MT7620 after commit 34ca34b32b02

Hi, On Tue, May 22, 2018 at 4:33 PM, John Crispin wrote: > what exactly is the issue ? breaking compat means that rosen either needs to > fix the regression or we need to revert the patch. The issue I saw is that writing to GPIO has no effect. On my device (mt7620-based), I

Re: [OpenWrt-Devel] Broken GPIO on MT7620 after commit 34ca34b32b02

On 22/05/18 16:18, Kristian Evensen wrote: On Sun, May 20, 2018 at 10:26 PM, Rosen Penev wrote: Bisecting further is hard, since the commit is a combination of (a lot of) clean-up and some functional changes. Changes can be viewed on the linux-next tree. It should be as

Re: [OpenWrt-Devel] Broken GPIO on MT7620 after commit 34ca34b32b02

On Sun, May 20, 2018 at 10:26 PM, Rosen Penev wrote: >> Bisecting further is hard, since the >> commit is a combination of (a lot of) clean-up and some functional >> changes. > Changes can be viewed on the linux-next tree. It should be as simple > as dropping in the relevant

[OpenWrt-Devel] 18.06 Bug: HW Flow Offload + Wireguard Bug

Dear Felix & others, I am currently running a 18.06 snapshot image to start testing the stability of the firmware and new features, including the lovely hardware flow offload. While it is working extremely well (I am finally able to max out my connection, but with hardly any CPU load!), pushing

[OpenWrt-Devel] Fwd: 18.06 Bug: Baby Jumbo Frames on mt7621

Dear all, The switch to the 4.14 kernel apparently broke the baby jumbo frames support of 2048 bytes that the switch is capable off. I found out that changing the mtu above 1500 via Luci no longer applies properly. Trying to manually change the mtu via ssh also fails: root@LEDE:~# ifconfig eth0

[OpenWrt-Devel] [PATCH 1/2] kernel: bump 4.9 to 4.9.101

Refreshed all patches Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte --- include/kernel-version.mk | 4 ++-- .../090-net-generalize-napi_complete_done.patch| 4 ++--

[OpenWrt-Devel] [PATCH 2/2] kernel: bump 4.14 to 4.14.42

Refreshed all patches Compile-tested on: cns3xxx, imx6, x86_64 Runtime-tested on: cns3xxx, imx6, x86_64 Signed-off-by: Koen Vandeputte --- Contains an important fix for UDP sockets! ("udp: fix SO_BINDTODEVICE") include/kernel-version.mk

[OpenWrt-Devel] [PATCH 4/4] ustream-ssl: openssl-1.1 compatibility

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 --- Patch to compile ustream-ssl with

[OpenWrt-Devel] [PATCH 3/4] adb: added patch for openssl 1.1.0 compatibility

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 --- Signed-off-by: Eneas U de Queiroz

[OpenWrt-Devel] [PATCH 1/4] 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

[OpenWrt-Devel] [PATCH 2/4] libevent2: Make it build using OpenSSL 1.1.0

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 is a backport of @kroeckx

[OpenWrt-Devel] 18.06 Bug: Baby Jumbo Frames on mt7621

Dear all, The switch to the 4.14 kernel apparently broke the baby jumbo frames support of 2048 bytes that the switch is capable off. I found out that changing the mtu above 1500 via Luci no longer applies properly. Trying to manually change the mtu via ssh also fails: root@LEDE:~# ifconfig eth0

[OpenWrt-Devel] Bug: HW Flow Offload + Wireguard Bug

Dear Felix & others, I am currently running a 18.06 snapshot image to start testing the stability of the firmware and new features, including the lovely hardware flow offload. While it is working extremely well (I am finally able to max out my connection, but with hardly any CPU load!), pushing

Re: [OpenWrt-Devel] Why nftables does not work in OpenWrt ?

Hi Hauke, Do you mean my nftables commands (limit rate xxx) can work on your lantiq (4.14 kernel) target ? I also choose kmod-nf-flow and kmod-nft-offload modules, but it can not restrict the traffic flow on specific ip address yet. >On 05/20/2018 12:25 PM, Rosysong