Re: [OpenWrt-Devel] [PATCH v2 1/2] pinctrl/lantiq: split xway_mfp into dedicated tables

Hi, Mit freundlichen Grüßen, Kind regards Martin Schiller Dipl.-Inf. FH Entwicklung Development TDT GmbH Tel. +49 (0) 8703 929 00 Siemensstr. 18 Fax +49 (0) 8703 929 201 84051 Essenbach E-Mailmschil...@tdt.de Germany Internet www.tdt.de

[OpenWrt-Devel] [PATCH] pinctrl/lantiq: split xway_mfp into dedicated tables

n it turend out, that there are some differences in the GPIO alternative functions of the Danube, xRX100 and xRX200 families, which makes it impossible to use only one xway_mfp table. This patch is also the first step to add support for the xRX300 family. Signed-off-by: Martin Schiller <

Re: [OpenWrt-Devel] [PATCH] pinctrl/lantiq: split xway_mfp into dedicated tables

-devel@lists.openwrt.org Betreff: Re: [OpenWrt-Devel] [PATCH] pinctrl/lantiq: split xway_mfp into dedicated tables Hi, the dts and kernel changes should be in separate patches. also please send the pinctrl patch upstream. John On 16/11/2015 10:42, Martin Schiller wrote: > This patch spl

[OpenWrt-Devel] [PATCH v2 1/2] pinctrl/lantiq: split xway_mfp into dedicated tables

n it turend out, that there are some differences in the GPIO alternative functions of the Danube, xRX100 and xRX200 families, which makes it impossible to use only one xway_mfp table. This patch is also the first step to add support for the xRX300 family. Signed-off-by: Martin Schiller <mschil.

[OpenWrt-Devel] [PATCH v2 2/2] pinctrl/lantiq: adapt device-trees to new tables

This patch adapts the "pinctrl-xway" and "pinctrl-xr9" settings in the dts files into dedicated "pinctrl-ase", "pinctrl-danube", "pinctrl-xrx100" and "pinctrl-xrx200" settings. Signed-off-by: Martin Schiller <mschil...@tdt.de>

[OpenWrt-Devel] [PATCH v3 2/2] pinctrl/lantiq: adapt devicetrees to new tables

This patch adapts the "pinctrl-xway" and "pinctrl-xr9" settings in the dts files into dedicated "pinctrl-ase", "pinctrl-danube", "pinctrl-xrx100" and "pinctrl-xrx200" settings. Signed-off-by: Martin Schiller <mschil...@tdt.de>

[OpenWrt-Devel] [PATCH v3 1/2] pinctrl/lantiq: introduce new dedicated tables

nctions of the Danube, xRX100 and xRX200 families, which makes it impossible to use only one xway_mfp table. This patch is also the first step to add support for the xRX300 family. Signed-off-by: Martin Schiller <mschil...@tdt.de> --- .../patches-3.18/0150-lantiq-pinctrl-xway.patch| 1118 +++

[OpenWrt-Devel] Review of 0012-pinctrl-lantiq-fix-up-pinmux.patch

Hi, here follows a little review of the 0012-pinctrl-lantiq-fix-up-pinmux.patch to get this stuff upstream: > From 25494c55a4007a1409f53ddbafd661636e47ea34 Mon Sep 17 00:00:00 2001 > From: John Crispin > Date: Fri, 9 Aug 2013 20:38:15 +0200 > Subject: [PATCH 12/36]

Re: [OpenWrt-Devel] [PATCH] pinctrl/lantiq: split xway_mfp into dedicated tables

Hi, On 11/16/2015 at 9:28 PM, Hauke Mehrtens wrote: > Hi Martin, > > The get_maintainer.pl helps to find the correct mailing list, it > searches the MAINTAINERS file. > > ./scripts/get_maintainer.pl -f drivers/pinctrl/pinctrl-xway.c > Linus Walleij (maintainer:PIN

[OpenWrt-Devel] [PATCH] lantiq, xrx200-net: add new 'id' devicetree property

This patch adds the new 'id' devicetree property, which makes it possible to renumber the physical mac ports. This change has only cosmetical reasons (e.g. appearance in swconfig, kernel messages on link change). Signed-off-by: Martin Schiller <mschil...@tdt.de> --- .../0025-NET-MIPS-

[OpenWrt-Devel] [PATCH v2] lantiq, xrx200-net: add devicetree aliases support for port->mac mapping

This patch adds devicetree aliases support, which makes it possible to renumber the physical mac ports. This change has only cosmetical reasons (e.g. appearance in swconfig, kernel messages on link change). Signed-off-by: Martin Schiller <mschil...@tdt.de> --- Changes in v2: - use devi

Re: [OpenWrt-Devel] [PATCH v2] lantiq, xrx200-net: add devicetree aliases support for port->mac mapping

On 12/17/2015 at 12:13 PM, John Crispin wrote: > > > On 17/12/2015 12:03, Martin Schiller wrote: > > On 12/17/2015 at 9:20 AM, John Crispin wrote: > >> > >> > >> On 14/12/2015 10:18, Martin Schiller wrote: > >>> This patch ad

Re: [OpenWrt-Devel] [PATCH v2] lantiq, xrx200-net: add devicetree aliases support for port->mac mapping

On 12/17/2015 at 9:20 AM, John Crispin wrote: > > > On 14/12/2015 10:18, Martin Schiller wrote: > > This patch adds devicetree aliases support, which makes it possible > to > > renumber the physical mac ports. > > > > This change has only cosmetical reasons (e.g

Re: [OpenWrt-Devel] Review of 0012-pinctrl-lantiq-fix-up-pinmux.patch

On 11/17/2015 at 8:50 AM, Martin Schiller wrote: > Hi, > > here follows a little review of the 0012-pinctrl-lantiq-fix-up- > pinmux.patch > to get this stuff upstream: > > > From 25494c55a4007a1409f53ddbafd661636e47ea34 Mon Sep 17 00:00:00 > 2001 > > From:

Re: [OpenWrt-Devel] Review of 0012-pinctrl-lantiq-fix-up-pinmux.patch

On 11/19/2015 at 8:15 AM, John Crispin wrote: > > > On 19/11/2015 06:39, Martin Schiller wrote: > > On 11/17/2015 at 8:50 AM, Martin Schiller wrote: > >> Hi, > >> > >> here follows a little review of the 0012-pinctrl-lantiq-fix-up- > >> pinmux.pat

Re: [OpenWrt-Devel] [PATCH 2/5] lantiq/xrx200-net: fix PCE_MAPx handling

On 02/20/2016 at 10:59 AM, Felix Fietkau wrote: > On 2016-02-18 14:13, Martin Schiller wrote: > > Remove unnecessary MPMAP (PCE_MAP1) initialization and make > DMCPMAP (PCE_MAP2) > > and UUCMAP (PCE_MAP3) configurable from user space. > > > > Signed-off-by: Mar

[OpenWrt-Devel] lantiq/xrx200-net: separate lan and wan ports

Hi! I need to set up the xrx200 switch with one LAN switch part (phy2-phy5) and one WAN port (phy1). The problem is, that I can see the LAN traffic on the WAN port and vice versa. It doesn't also matter if SW_PORTMAP is defined or not. I think it maybe has something to do with the PCE_PMAPx

Re: [OpenWrt-Devel] lantiq/xrx200-net: separate lan and wan ports

On 02/16/2016 at 9:46 AM, Martin Schiller wrote: > On 02/16/2016 at 8:32 AM, Martin Blumenstingl wrote: > > On Tue, Feb 16, 2016 at 8:06 AM, Martin Schiller <mschil...@tdt.de> wrote: > > > Hi! > > > > > > I need to set up the xrx200 switch with one LAN sw

[OpenWrt-Devel] [PATCH 1/5] lantiq/xrx200-net: Add support for eth0 as WAN interface if the SW_PORTMAP is disabled

Use priv->wan instead of priv->id as indicator if packets should go to the Ethernet WAN group (DPID=1) or not (DPID=0). This way, it's independant of interface names or indexes. Signed-off-by: Martin Schiller <mschil...@tdt.de> --- .../linux/lantiq/patches-4.4/0025-NET-MIPS-lantiq

[OpenWrt-Devel] [PATCH 2/5] lantiq/xrx200-net: fix PCE_MAPx handling

Remove unnecessary MPMAP (PCE_MAP1) initialization and make DMCPMAP (PCE_MAP2) and UUCMAP (PCE_MAP3) configurable from user space. Signed-off-by: Martin Schiller <mschil...@tdt.de> --- .../0025-NET-MIPS-lantiq-adds-xrx200-net.patch | 42 ++ 1 file changed, 28 inse

[OpenWrt-Devel] [PATCH 3/5] lantiq/xrx200-net: fix VID max value

The correct possible VID range is 0-4095. Signed-off-by: Martin Schiller <mschil...@tdt.de> --- .../lantiq/patches-4.4/0025-NET-MIPS-lantiq-adds-xrx200-net.patch | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/target/linux/lantiq/patches-4.4/0025-NET-MIPS-lanti

[OpenWrt-Devel] [PATCH 4/5] lantiq/xrx200-net: add FID (filtering identifier) setting

By setting the FID of a VLAN group to a value other then the default (0) it is possible to switch from Shared VLAN Learning to Independant VLAN Learning. Signed-off-by: Martin Schiller <mschil...@tdt.de> --- .../0025-NET-MIPS-lantiq-adds-xrx200-net.patch | 39 +-

[OpenWrt-Devel] [PATCH 5/5] lantiq/xrx200-net: change VLAN untagged ports and PVID handling

tagging enabled, so it's not possible to set the PVID automatically like the xrx200sw_fixup_pvids() did it before and has to be specified explicitly. Signed-off-by: Martin Schiller <mschil...@tdt.de> --- .../0025-NET-MIPS-lantiq-adds-xrx200-net.patch | 76 -- 1 file chang

Re: [OpenWrt-Devel] [PATCH 4/5] lantiq/xrx200-net: add FID (filtering identifier) setting

On 02/19/2016 at 6:32 AM, John Crispin wrote: > > > On 18/02/2016 14:13, Martin Schiller wrote: > > By setting the FID of a VLAN group to a value other then the default (0) it > > is possible to switch from Shared VLAN Learning to Independant VLAN > Learning. > > &

Re: [OpenWrt-Devel] [PATCH 4/5] lantiq/xrx200-net: add FID (filtering identifier) setting

On 02/19/2016 at 11:27 AM, John Crispin wrote: > > > On 19/02/2016 08:29, Martin Schiller wrote: > > On 02/19/2016 at 6:32 AM, John Crispin wrote: > >> > >> > >> On 18/02/2016 14:13, Martin Schiller wrote: > >>> By setting the FI

Re: [OpenWrt-Devel] [PATCH 4/5] lantiq/xrx200-net: add FID (filtering identifier) setting

On 02/19/2016 at 2:22 PM, John Crispin wrote: > > > On 19/02/2016 14:08, Martin Schiller wrote: > > On 02/19/2016 at 11:27 AM, John Crispin wrote: > >> > >> > >> On 19/02/2016 08:29, Martin Schiller wrote: > >>> On 02/19/2016 at 6:32 AM, John C

Re: [OpenWrt-Devel] kmod-gpio-mcp23s08 not working/available for linux-4.14

On 2018-08-23 14:10, Martin Schiller wrote: On 2018-08-23 12:17, John Crispin wrote: On 23/08/18 11:53, Martin Schiller wrote: The mcp23s08 drivers was moved from gpio to pinctrl "subsystem" in linux-4.13. As linux-4.9 is still used for some targets, how to proceed with this mcp23

[OpenWrt-Devel] kmod-gpio-mcp23s08 not working/available for linux-4.14

The mcp23s08 drivers was moved from gpio to pinctrl "subsystem" in linux-4.13. As linux-4.9 is still used for some targets, how to proceed with this mcp23s08 driver? Create a new (second) CONFIG option (kmod-pinctrl-mcp23s08) coexisting to the kmod-gpio-mcp23s08? Or is it possible to get

Re: [OpenWrt-Devel] kmod-gpio-mcp23s08 not working/available for linux-4.14

On 2018-08-23 12:17, John Crispin wrote: On 23/08/18 11:53, Martin Schiller wrote: The mcp23s08 drivers was moved from gpio to pinctrl "subsystem" in linux-4.13. As linux-4.9 is still used for some targets, how to proceed with this mcp23s08 driver? Create a new (second) CONFIG op

Re: [OpenWrt-Devel] u-boot/lantiq: gcc7 incompatibility: resets when trying to access network

On 2018-09-24 13:38, Martin Schiller wrote: On 2018-09-24 13:14, Martin Schiller wrote: Hi, I've got some problems with the lantiq uboot in combination with the (default) gcc 7.x compiler. Setting "OPTFLAGS" in uboot's config.mk to "-O2" or the default "-Os" le

Re: [OpenWrt-Devel] u-boot/lantiq: gcc7 incompatibility: resets when trying to access network

On 2018-09-24 13:14, Martin Schiller wrote: Hi, I've got some problems with the lantiq uboot in combination with the (default) gcc 7.x compiler. Setting "OPTFLAGS" in uboot's config.mk to "-O2" or the default "-Os" leads to the following behaviour: The uboot com

[OpenWrt-Devel] u-boot/lantiq: gcc7 incompatibility: resets when trying to access network

Hi, I've got some problems with the lantiq uboot in combination with the (default) gcc 7.x compiler. Setting "OPTFLAGS" in uboot's config.mk to "-O2" or the default "-Os" leads to the following behaviour: The uboot compiles well, but when you try o access the ethernet network

[OpenWrt-Devel] [PATCH/netifd] interface: fix "if-down" hotplug event handling

ace: set interface in TEARDOWN state when checking link state") Signed-off-by: Martin Schiller --- interface.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/interface.c b/interface.c index fd7a826..7c25839 100644 --- a/interface.c +++ b/interface.c @@ -268,7 +268,7

[OpenWrt-Devel] [PATCH v2 netifd] interface: fix "if-down" hotplug event handling

ace: set interface in TEARDOWN state when checking link state") Signed-off-by: Martin Schiller --- interface.c | 1 + 1 file changed, 1 insertion(+) diff --git a/interface.c b/interface.c index fd7a826..e0652cd 100644 --- a/interface.c +++ b/interface.c @@ -269,6 +269,7 @@ mark_interfac

Re: [OpenWrt-Devel] [PATCH/netifd] interface: fix "if-down" hotplug event handling

On 2019-04-11 15:16, Hans Dedecker wrote: Hi, On Thu, Apr 11, 2019 at 3:02 PM Martin Schiller wrote: commit a97297d83e42 ("interface: set interface in TEARDOWN state when checking link state") broke the if-down hotplug event handling, as the iface->state is now IFS_TEARDOWN

[OpenWrt-Devel] [PATCH uqmi] nas: add --get-plmn

. Signed-off-by: Martin Schiller --- commands-nas.c | 31 +++ commands-nas.h | 2 ++ 2 files changed, 33 insertions(+) diff --git a/commands-nas.c b/commands-nas.c index 5874bfb..1f7445d 100644 --- a/commands-nas.c +++ b/commands-nas.c @@ -293,6 +293,37

Re: [OpenWrt-Devel] [PATCH uqmi] nas: add --get-plmn

On 2019-08-26 21:12, Sami Olmari wrote: I think the ideology behind proto handler there is to "do whatever told" despite of what the state is currently, maybe there is a reason for such behaviour (searches some stuff from network etc). There exist 2 problems in the qmi proto handler: 1.

Re: [OpenWrt-Devel] [PATCH uqmi] nas: add --get-plmn

Can somebody please take a look at this patch. It's really necessary to fix the problem in the qmi proto handler. Thanks, Martin On 2019-07-04 13:35, Martin Schiller wrote: This command is needed in the qmi proto handler to check if the plmn is already set to 'auto'. The reason

Re: [OpenWrt-Devel] Lantiq xrx200: Access to ethernet phy registers (MDIO) from userspace

On 2019-09-16 22:43, Hauke Mehrtens wrote: On 9/16/19 7:09 PM, Martin Blumenstingl wrote: Hi Martin, On Mon, Sep 16, 2019 at 12:54 PM Martin Schiller wrote: Hi! I am searching for a possibility to disable Auto Negotiation of an PEF7072 which is attached to MAC1 of the Lantiq xrx200 switch

Re: [OpenWrt-Devel] Lantiq xrx200: Access to ethernet phy registers (MDIO) from userspace

On 2019-09-17 08:51, Martin Schiller wrote: Meanwhile I found out that there is a mechanism with swconfig to configure the link attributes: https://git.openwrt.org/?p=openwrt/openwrt.git;a=commitdiff;h=6219b3deae1c8dfbf405f5a701d3f3b00ebacce1 I will try to integrate this into the "old&qu

[OpenWrt-Devel] Lantiq xrx200: Access to ethernet phy registers (MDIO) from userspace

Hi! I am searching for a possibility to disable Auto Negotiation of an PEF7072 which is attached to MAC1 of the Lantiq xrx200 switch. The xrx200-net driver does not seem to have support for that. Accessing the STD_CRTL register on the mdio bus from uboot with the mdio command works like

Re: [OpenWrt-Devel] [PATCH uqmi] nas: add --get-plmn

Ping. I still want to fix the existing problems in the qmi protohandler. Therefore, this feature needs to be integrated into uqmi. Martin On 2019-08-29 10:35, Bjørn Mork wrote: Martin Schiller writes: On 2019-08-26 21:12, Sami Olmari wrote: I think the ideology behind proto handler

Re: [OpenWrt-Devel] OpenWrt 19.07 release schedule ?

On 2019-10-12 03:28, Gordon Shawn wrote: What about skipping 19.07 and focusing on 20.03 instead? Based on the resource I think one release per year is not bad. By then Luci will be in a better shape and a newer kernel can also be used instead. Well, there are always some great changes in the

Re: [OpenWrt-Devel] Lantiq xrx200: PTM issues

d to a new one and the original skb gets freed. Otherwise the skb only gets freed after a complete round through the TX descriptor table. My suggestion would be, to always copy the skb. - Martin On 2020-01-20 13:45, Martin Schiller wrote: Update: I've found out now that the ENOB

Re: [OpenWrt-Devel] Lantiq xrx200: PTM issues

Just for reference: I've opened a pull request with a fix here: https://github.com/openwrt/openwrt/pull/2707 - Martin On 2020-01-21 06:28, Martin Schiller wrote: Ok, I think I've got it: The "sk_wmem_alloc" is decremented in sock_wfree() which is called by

[OpenWrt-Devel] [WIP] vrx518 support for AVM Fritzbox 7530

I've done some work to get the vrx518 running on the AVM Fritzbox 7530: https://github.com/3headeddevs/openwrt/commits/vrx518_support The current status is as follows: - The VRX518 TC driver is running in software datapath mode, which required some codefixes for the driver to compile at all. -

[OpenWrt-Devel] Lantiq xrx200: PTM issues

Hi! I have discovered the following problem: If you have established a PPPoE session via VDSL / PTM connection incl. VLAN tagging and send data with a relatively small send buffer (SO_SNDBUF), then an ENOBUFS always comes back. We first noticed this with stagnating data transfers over an

Re: [OpenWrt-Devel] Lantiq xrx200: PTM issues

Update: I've found out now that the ENOBUFS is set by __ip_append_data, because sk_wmem_alloc "overflows". Martin On 2020-01-20 07:09, Martin Schiller wrote: Hi! I have discovered the following problem: If you have established a PPPoE session via VDSL / PTM connection incl. VL

[OpenWrt-Devel] problems with virtual sub interfaces in firewall zones

Hi Jo, Hi all, I've encountered a problem with the change you made with commit 64bb88841fbc ("uqmi: inherit firewall zone membership to virtual sub interfaces") which was introduced to fix FS#2122. This change makes it impossible to move an interface from one zone to another without a

Re: [OpenWrt-Devel] problems with virtual sub interfaces in firewall zones

On 2020-05-07 06:47, Martin Schiller wrote: Hi Jo, Hi all, I've encountered a problem with the change you made with commit 64bb88841fbc ("uqmi: inherit firewall zone membership to virtual sub interfaces") which was introduced to fix FS#2122. This change makes it impossible to move an

Re: [OpenWrt-Devel] problems with virtual sub interfaces in firewall zones

On 2020-05-07 07:39, Martin Schiller wrote: On 2020-05-07 06:47, Martin Schiller wrote: Hi Jo, Hi all, I've encountered a problem with the change you made with commit 64bb88841fbc ("uqmi: inherit firewall zone membership to virtual sub interfaces") which was introduced to f

Re: [OpenWrt-Devel] problems with virtual sub interfaces in firewall zones

On 2020-05-07 07:39, Martin Schiller wrote: On 2020-05-07 06:47, Martin Schiller wrote: Hi Jo, Hi all, I've encountered a problem with the change you made with commit 64bb88841fbc ("uqmi: inherit firewall zone membership to virtual sub interfaces") which was introduced to f

Re: [OpenWrt-Devel] [PATCH] lantiq: add dsl line_state mapping

On 2020-06-17 12:21, Florian Eckert wrote: Hi Adrian, The line_state of the DSL connection is described in the system via a hexadecimal variable. With this change the hexadecimal is mapped to a decimal value. With this change it is now possible to store this value in a database, so that it

Re: [PATCH] base-files: sysupgrade: store status of system-services

On 2021-01-11 14:38, Stijn Segers wrote: Hi Alberto, Alberto Bursi schreef op 11 januari 2021 03:56:23 CET: On 10/01/21 22:50, Stijn Segers wrote: Hi Sven, Op zondag 10 januari 2021 om 22u28 schreef Sven Roederer : Am Samstag, 9. Januar 2021, 12:28:31 CET schrieb Stijn Segers:  > @@

Re: [PATCH v2] base-files: restore status of system-services after sysupgrade

On 2021-01-11 23:07, Sven Roederer wrote: Restore the status of the system-services after sysupgrade. Create a file with the status of all known services and keep it during upgrade. After upgrade run a uci-default script to restore every single service. Doing the restore in an uci-default

netifd: segfault on teardown when using proto static on dynamically added interface

Hi! In my work on https://github.com/openwrt/openwrt/pull/2759 (umbim / wwan: bugfixes + support for non-dhcp devices), I ran into a problem ith netifd. If you use the "static" protocol for a dynamically created interface, the netifd throws a segfault on "ifdown" of the parent interface. This

Re: [PATCH v2 0/12] add ubus support to ltq-[v|a]dsl-app

On 2021-01-14 12:55, Mathias Kresin wrote: 1/13/21 3:00 PM, Martin Schiller: On 2021-01-09 09:40, Andre Heider wrote: Hi, (cc'ed some recent commiters for lantiq) On 15/12/2020 10:35, Andre Heider wrote: v2: - drop 0002-ltq-vdsl-app-fix-Wundef-warnings.patch - use "/dev/dsl_cpe_api&quo

Re: [PATCH v2] base-files: restore status of system-services after sysupgrade

On 2021-01-12 23:03, Sven Roederer wrote: Am Dienstag, 12. Januar 2021, 19:56:54 CET schrieb Hannu Nyman: Martin Schiller kirjoitti 12.1.2021 klo 9.25: > On 2021-01-11 23:07, Sven Roederer wrote: >> Restore the status of the system-services after sysupgrade. >> Create a file

Re: [PATCH v2 0/12] add ubus support to ltq-[v|a]dsl-app

On 2021-01-09 09:40, Andre Heider wrote: Hi, (cc'ed some recent commiters for lantiq) On 15/12/2020 10:35, Andre Heider wrote: v2: - drop 0002-ltq-vdsl-app-fix-Wundef-warnings.patch - use "/dev/dsl_cpe_api" without the "0" suffix for the adsl daemon:

Re: [RFC PATCH v2 0/1] Introduce UCI support for configuring DSA VLAN filter rules

On 2021-04-28 14:39, Martin Schiller wrote: On 2021-03-26 10:30, Martin Schiller wrote: On 2021-03-26 09:55, Martin Schiller wrote: On 2021-03-26 09:42, Felix Fietkau wrote: On 2021-03-26 09:34, Martin Schiller wrote: On 2020-07-24 19:13, Felix Fietkau wrote: On 2020-07-24 18:44, Jo-Philipp

layerscape: problems with image builder

When trying to build an image for the Layerscape "NXP LS1046A-RDB SD Card Boot" target using Image Builder, you get the following error messages: ... Package list missing or not up-to-date, generating it. Building package

OpenWrt 21.02: backport lantiq xrx200 DSA switch

Hello all! Now that the Lantiq xrx200 DSA switch has finally made it into the master, I would like to ask whether we also want to pack this switch into the 21.02 release. The topic "DSA Support" is one of the key points of the 21.02 release and therefore this would fit very well. Any opinions?

Re: [RFC PATCH v2 0/1] Introduce UCI support for configuring DSA VLAN filter rules

On 2021-03-26 10:49, Martin Schiller wrote: On 2021-03-26 10:44, Felix Fietkau wrote: On 2021-03-26 09:55, Martin Schiller wrote: On 2021-03-26 09:42, Felix Fietkau wrote: On 2021-03-26 09:34, Martin Schiller wrote: On 2020-07-24 19:13, Felix Fietkau wrote: On 2020-07-24 18:44, Jo-Philipp

Re: [RFC PATCH v2 0/1] Introduce UCI support for configuring DSA VLAN filter rules

On 2021-03-26 10:30, Martin Schiller wrote: On 2021-03-26 09:55, Martin Schiller wrote: On 2021-03-26 09:42, Felix Fietkau wrote: On 2021-03-26 09:34, Martin Schiller wrote: On 2020-07-24 19:13, Felix Fietkau wrote: On 2020-07-24 18:44, Jo-Philipp Wich wrote: Hi Felix, [...] For a simple

Re: [RFC PATCH v2 0/1] Introduce UCI support for configuring DSA VLAN filter rules

On 2021-03-26 10:44, Felix Fietkau wrote: On 2021-03-26 09:55, Martin Schiller wrote: On 2021-03-26 09:42, Felix Fietkau wrote: On 2021-03-26 09:34, Martin Schiller wrote: On 2020-07-24 19:13, Felix Fietkau wrote: On 2020-07-24 18:44, Jo-Philipp Wich wrote: Hi Felix, [...] For a simple

Re: [RFC PATCH v2 0/1] Introduce UCI support for configuring DSA VLAN filter rules

On 2020-07-24 19:13, Felix Fietkau wrote: On 2020-07-24 18:44, Jo-Philipp Wich wrote: Hi Felix, [...] For a simple default config, you could have this: # network config device option type bridge # I assume this is needed as well option name switch0 Correct. config

Re: [RFC PATCH v2 0/1] Introduce UCI support for configuring DSA VLAN filter rules

On 2021-03-26 09:42, Felix Fietkau wrote: On 2021-03-26 09:34, Martin Schiller wrote: On 2020-07-24 19:13, Felix Fietkau wrote: On 2020-07-24 18:44, Jo-Philipp Wich wrote: Hi Felix, [...] For a simple default config, you could have this: # network config device option type bridge

Re: [RFC PATCH v2 0/1] Introduce UCI support for configuring DSA VLAN filter rules

On 2021-03-26 09:55, Martin Schiller wrote: On 2021-03-26 09:42, Felix Fietkau wrote: On 2021-03-26 09:34, Martin Schiller wrote: On 2020-07-24 19:13, Felix Fietkau wrote: On 2020-07-24 18:44, Jo-Philipp Wich wrote: Hi Felix, [...] For a simple default config, you could have

Re: lantiq: upstream Linux efforts

On 2021-04-12 00:24, Hauke Mehrtens wrote: Hi, On 4/11/21 7:51 PM, Martin Blumenstingl wrote: Hello everyone, you are included in this email because you have previously worked on patches for the Lantiq SoCs upstream. In the past updating the kernel version for the lantiq target in OpenWrt

Re: OpenWrt 21.02-rc1

On 2021-04-07 12:01, Hannu Nyman wrote: Hauke Mehrtens kirjoitti 7.4.2021 klo 1.29: Hi, How do we want to go forward with OpenWrt 21.02-rc1? * I think the base system is ok. * The http (original wolfssl) problem reported by jow is fixed * LuCI in the 21.02 branch still misses DSA support,

Re: Release goals for 22.XX

On 2021-10-20 04:47, Paul Spooren wrote: For now layerscape is still on 5.4 without Kernel 5.10 support. Is anyone planing to add support? Please reach out. As I had already written on 08 October, I am already working on it. Thereby I try to bring all relevant components to the state of

Re: Release goals for 22.XX

On 2021-10-08 11:13, Paul Spooren wrote: Hi, --- %< --- based on my overview[1] things are moving forward and being tested, great! What about the targets that did not see any 5.10 ambitions yet? Specifically: - arc770 - archs38 I just got an email from synopsys

RFC: layerscape: update to kernel 5.10

I have now found the cause of my boot problems with linux 5.10. (see [1] for reference) By changing the TEXT_OFFSET to 0x0 (instead of 0x8 before) in the upstream commit [2] and deactivated kernel option CONFIG_RELOCATABLE the system could not boot. Thus, we now need to set the

[PATCH ustream-ssl v2] ustream-openssl: Disable renegotiation in TLSv1.2 and earlier

This fixes CVE-2011-1473 and CVE-2011-5094 by disabling renegotiation in TLSv1.2 and earlier for server context. Signed-off-by: Martin Schiller --- v2: - also handle wolfssl implementation. --- ustream-openssl.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/ustream-openssl.c b

[PATCH ustream-ssl] ustream-openssl: Disable renegotiation in TLSv1.2 and earlier

This fixes CVE-2011-1473 and CVE-2011-5094 by disabling renegotiation in TLSv1.2 and earlier for server context. Signed-off-by: Martin Schiller --- ustream-openssl.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/ustream-openssl.c b/ustream-openssl.c index 6dae4ae..9d8d1bc 100644

kernel-headers: platform/target patches are not applied

When preparing the kernel sources to build the kernel headers, currently only the patches from the generic folder are applied, but not from the actual selected target. This is basically understandable if one assumes that one wants to use a toolchain for different targets with the same

Re: kernel-headers: platform/target patches are not applied

Hi Felix, On 2023-07-27 22:26, Felix Fietkau wrote: Hi Martin, On 27.07.23 13:23, Martin Schiller wrote: When preparing the kernel sources to build the kernel headers, currently only the patches from the generic folder are applied, but not from the actual selected target. This is basically

Re: [PATCH RESEND 06/11] Revert "x86/geode: enable X86_INTEL_LPSS to select PINCTRL"

a, I wasn't able to find very much information when I looked at this. I did find: https://lists.openwrt.org/pipermail/openwrt-devel/2018-August/019479.html This doesn't tell me what platform Martin Schiller was trying for. 17f30bfcf7 makes me suspect Martin Schiller was simply trying to do this to al