[PATCH v2 1/1] apu2: add definitions for apu4/6

2022-12-27 Thread Philip Prindeville
From: Philip Prindeville Signed-off-by: Philip Prindeville --- target/linux/x86/base-files/etc/board.d/01_leds| 2 +- target/linux/x86/base-files/etc/board.d/02_network | 3 +++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/target/linux/x86/base-files/etc/board.d/01_leds b/

[PATCH 1/1] apu2: add definitions for apu4/6

2022-12-27 Thread Philip Prindeville
From: Philip Prindeville Signed-off-by: Philip Prindeville --- target/linux/x86/base-files/etc/board.d/02_network | 3 +++ 1 file changed, 3 insertions(+) diff --git a/target/linux/x86/base-files/etc/board.d/02_network b/target/linux/x86/base-files/etc/board.d/02_network index 9335e297ba22bb

Re: Updating env/kernel-config after rebasing/kernel version bump

2022-12-27 Thread Philip Prindeville
> On Dec 27, 2022, at 4:50 PM, Robert Marko wrote: > > On Wed, 28 Dec 2022 at 00:48, Philip Prindeville > wrote: >> >> Hi, >> >> I originally set up my env/kernel-config a long time ago (like 2018) by >> hand, and since then the kernel has gone through several bumps. How do I >> easily r

Re: Updating env/kernel-config after rebasing/kernel version bump

2022-12-27 Thread Robert Marko
On Wed, 28 Dec 2022 at 00:48, Philip Prindeville wrote: > > Hi, > > I originally set up my env/kernel-config a long time ago (like 2018) by hand, > and since then the kernel has gone through several bumps. How do I easily > refresh it to pick up new stuff from target/linux/x86/64/config-${KVER}

Updating env/kernel-config after rebasing/kernel version bump

2022-12-27 Thread Philip Prindeville
Hi, I originally set up my env/kernel-config a long time ago (like 2018) by hand, and since then the kernel has gone through several bumps. How do I easily refresh it to pick up new stuff from target/linux/x86/64/config-${KVER} (where KVER=5.15 currently)? Is there a handy script or make targ

Re: [PATCH 1/2] ramips: mt7621: Add Arcadyan WE420223-99 support

2022-12-27 Thread Rafał Miłecki
On 15.08.2022 12:30, Harm Berntsen via openwrt-devel wrote: 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 sof

[PATCH v2 1/2] ramips: mt7621: Add Arcadyan WE420223-99 support

2022-12-27 Thread Harm Berntsen via openwrt-devel
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 --- The Arcadyan WE420223-99 is a WiFi

[PATCH v2 2/2] ramips: mt7621-dts: we420223-99: mux phy0->gmac1

2022-12-27 Thread Harm Berntsen via openwrt-devel
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 gives each port an individual

Re: [PATCH v2] realtek: don't set L2LEARNING flag in rtl83xx TX header

2022-12-27 Thread Sander Vanheule
On Sat, 2022-12-17 at 21:39 +0100, Jan Hoffmann wrote: > As learning for the CPU port is now disabled globally, the bit in the > TX header doesn't have any effect anymore. Remove it to make the header > consistent with the global configuration. > > Originally, this change was intended to be applie

Re: [PATCH v2 0/3] realtek: avoid blocking for too long

2022-12-27 Thread Sander Vanheule
On Sat, 2022-12-17 at 21:45 +0100, Jan Hoffmann wrote: > This fixes multiple instances where the realtek drivers may block for > too long. These issues were discovered on HPE 1920 devices where such > behaviour is made obvious by the short timeout of the hardware watchdog. > > Changes in v2: > - r

[PATCH] Implement Makefile patch by Stijn Tintel and Robert Marko

2022-12-27 Thread Stijn Tintel via openwrt-devel
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 --- My associates have approved this e

Calling all OpenWRT maintainers for an important message

2022-12-27 Thread Stijn Tintel via openwrt-devel
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 --- Dear Open(fucking)WRT maintainers,