Re: Reduced throughput with mt7621 and DSA

Hi, On Tue, Dec 21, 2021 at 6:34 PM Kristian Evensen wrote: > Since the only change between my sets of tests is the software, > something has clearly improved in either the kernel or OpenWrt (as > would be expected :)). Are there any particular commits/patches that > would be worthwhile trying

Re: [PATCH v2 1/8] build: add e5500 CPU_TYPE

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 --- Not sure if it makes any

[PATCH] hostapd: keep HE capability after channel switch in AP+STA/Mesh

The auto-ht option already kept HT and VHT support, but wasn't updated to support HE (11ax). Signed-off-by: Arnout Vandecappelle (Essensium/Mind) --- This is a drive-by contribution that I just noticed while looking at the patch. I haven't even build tested. ---

[PATCH fstools] libfstools: avoid segfault in find_mount_point

If block is NULL, find_mount_point will segfault when comparing it against the device name found in /proc/self/mountinfo. Avoid this by checking if block is NULL. Signed-off-by: Stijn Tintel --- libfstools/find.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/libfstools/find.c

Re: [PATCH v2 7/8] qoriq: new target

On 21/12/2021 16:49, Rui Salvaterra wrote: > Hi, Stijn, > > Nice to see this! :) A few nits/comments/questions below… > > On Mon, 20 Dec 2021 at 19:01, Stijn Tintel wrote: >> Add a new target named "qoriq", that will support boards using PowerPC >> processors from NXP's QorIQ brand. >> >> This

Re: Reduced throughput with mt7621 and DSA

Hello again, On Sun, Dec 19, 2021 at 12:29 PM Kristian Evensen wrote: > Based on my measurements, the throughput is reduced by ~50% going from > 19.07 and to 21.02/master (~450Mbit/s vs. ~900Mbit/s). I do not have a > particular commit I can point to, but I believe the regressions is > caused by

Re: [PATCH v2 3/8] toolchain/gcc: use ELFv2 ABI on ppc64 with musl

Hi, Stijn, On Mon, 20 Dec 2021 at 19:01, Stijn Tintel wrote: > > At configuration time, gcc assumes that ppc64be targets use the ELFv1 > ABI, and ppc64le targets use the ELFv2 ABI. However, musl libc does not > support the ELFv1 ABI on ppc64 at all, regardless of the endianness. > > Therefore,

Re: [PATCH v2 1/8] build: add e5500 CPU_TYPE

Hi, Stijn, On Mon, 20 Dec 2021 at 19:01, Stijn Tintel wrote: > > This CPU type is compatible with NXP's PPC based QorIQ processors, and > will be used by the upcoming new qoriq target. > > Signed-off-by: Stijn Tintel > --- > include/target.mk | 1 + > 1 file changed, 1 insertion(+) > > diff

Re: [PATCH v2 7/8] qoriq: new target

Hi, Stijn, Nice to see this! :) A few nits/comments/questions below… On Mon, 20 Dec 2021 at 19:01, Stijn Tintel wrote: > > Add a new target named "qoriq", that will support boards using PowerPC > processors from NXP's QorIQ brand. > > This doesn't actually add support for any board yet, so that

Re: [PATCH 0/3] mikrotik: make soft_config partition writable

Hi, I tested the series on a Mikrotik LHG 2. # cat /proc/mtd dev:size erasesize name mtd0: 0002 0001 "RouterBoot" mtd1: e000 0001 "bootloader1" mtd2: 1000 0001 "hard_config" mtd3: 1000 0001 "bios" mtd4: f000 0001 "bootloader2" mtd5: 1000

Re: [PATCH v2 2/8] toolchain/musl: ppc64: check for AltiVec in setjmp/longjmp

Please ignore this patch, it's not required for the M300 and upstream requested changes. I'll omit it when pushing this series and work on it before continuing on the M200 and BSAP-3040. On 20/12/2021 21:00, Stijn Tintel wrote: Signed-off-by: Stijn Tintel ---