ar71xx: rb941-2nd 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 --- Hi, is there any chance of gett

Archer C50v1 causing "transmit queue 0 timed out" on other devices

Hi, I have an Archer C50v1 running gluon based on "19.07-SNAPSHOT r11019+10-5feb0df9bb" It seems to cause "transmit queue 0 timed out"[1] of a r8169 system. First I thought the r8169 nic is broken and changed the motherboard, but with another board with r8169 the issue is also appearing. Cha

Re: image size on 20.xx builds -- what about a new SMALL target

Hi, Keep in mind master sets CONFIG_KERNEL_KALLSYMS whereas stable builds do not. That alone makes a bit of a size difference (never checked how much). Other than that, 5.4 needs more space than 4.14 does (again, how much exactly I have not quantified). Thanks for that hint. Disabling CONFIG_

Re: image size on 20.xx builds

Hi, Apart from the usual kernel growth we have also enabled a bunch of previously disabled kernel features on targets which are not marked as SMALL_FLASH[1]. MT7620 is a mixed bag in that regard and it would make sense to split it similar to ath79 into a 'tiny' and a 'generic' variant. The 'mt76

Re: image size on 20.xx builds

Hi, Your Filesystem has a size of 5.81M. MT7620 has a kernel size of around 2M, which exceeds the available space on flash. On 19.07.3, the listed lineup of packages has 5.54M and it fits: Exportable Squashfs 4.0 filesystem, xz compressed, data block size 262144 compressed data, com

image size on 20.xx builds

Hi, I'm trying to create an image for an Archer C50v1 (mt7620). Tryin to build an image with the following packages[1] using the imagebuilder was impossible because the image got too big: Building images... Parallel mksquashfs: Using 1 processor Creating 4.0 filesystem on /data2/openwrt/openw

[OpenWrt-Devel] Support for TP-Link MR3420v3

Hi, some time ago Jacek Trzcinski sent a patch[1] for supporting the MR3420v3, which unfortunately wasn't developed further to be included. I'm using a MR3420v3 and would like to have official support for this router; I think I could modify the patch for the master branch, but I have no knowledge