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:
> @@ -228
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 scrip
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 wit
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:
package/kernel/lantiq/ltq-adsl/patches/1
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_ap
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 i
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 bridg
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
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 this
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
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, this
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 was
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 se
On 02/16/2016 at 8:32 AM, Martin Blumenstingl wrote:
> On Tue, Feb 16, 2016 at 8:06 AM, Martin Schiller wrote:
> > 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
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 wrote:
> > > Hi!
> > >
> > > I need to set up the xrx200 switch with one LAN switch part (p
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
---
.../linux/lantiq/patches-4.4/0025-NET-MIPS-lantiq-adds-xrx200-net.patc
Remove unnecessary MPMAP (PCE_MAP1) initialization and make DMCPMAP (PCE_MAP2)
and UUCMAP (PCE_MAP3) configurable from user space.
Signed-off-by: Martin Schiller
---
.../0025-NET-MIPS-lantiq-adds-xrx200-net.patch | 42 ++
1 file changed, 28 insertions(+), 14 deletions
The correct possible VID range is 0-4095.
Signed-off-by: Martin Schiller
---
.../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-lantiq-adds-xrx200-net.patch
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
---
.../0025-NET-MIPS-lantiq-adds-xrx200-net.patch | 39 +-
1 file changed, 38
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
---
.../0025-NET-MIPS-lantiq-adds-xrx200-net.patch | 76 --
1 file changed, 26 insertions(+
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.
> >
>
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 FID of a VLAN
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
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: Martin Sch
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
---
target/l
-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 splits
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
--
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
---
target/linux
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
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 CONTROL
> SUBSYSTEM)
> linux-g..
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] pinctrl/lantiq: fix up pinmux
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
---
.../patches-3.18/0150-lantiq-pinctrl-xway.patch| 1118 +++-
.../pa
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
---
target/linux
On 11/17/2015 at 4:10 PM, John Crispin wrote:
>
>
> On 17/11/2015 16:06, Daniel Schwierzeck wrote:
> > 2015-11-17 13:48 GMT+01:00 Martin Schiller :
> >> This patch introduces new dedicated "pinctrl-ase", "pinctrl-danube",
> >> "
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: John C
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
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
---
.../0025-NET-MIPS-lantiq-adds-xrx200
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
---
Changes in v2:
- use devicetree aliases instead of
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
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 adds devic
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
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
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
he qmi proto handler.
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
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 rea
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. Settin
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 thi
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
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
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
(ping/tftboot
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
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 "-O
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 expe
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
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
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 m
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 there
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 OpenVP
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 inc
copied 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 t
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
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
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 i
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
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?
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 and
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
LSDK-21
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 KERNEL_LOA
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
--- a
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
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
b
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.
-
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 reconn
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 mo
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 fix
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 fix
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 ca
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 architec
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
o idea, 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
Hi!
I've got some issues bringing up copper SFPs in a BananaPi BPI-R4 runnig
the latest OpenWrt master. Using the original Firmware pre-installed on
the BPI-R4 makes the modules work as expected:
I've tested with a HPE J8177C 1GBASE-T module as well as with a FS
SFP-10G-T module.
Any ideas what
On 2024-08-01 10:22, Daniel Golle wrote:
On 1 August 2024 07:26:35 UTC, Martin Schiller wrote:
Hi!
I've got some issues bringing up copper SFPs in a BananaPi BPI-R4
runnig
the latest OpenWrt master. Using the original Firmware pre-installed
on
the BPI-R4 makes the modules work as exp
Hi Daniel,
I have discovered a problem with the M.2 Key B slot of the BPI-R4. The
32 kHz CLKOUT signal of the RTC is (according to the specs) connected to
PIN 68.
However, on all the m.2 WWAN modules I have tested, this PIN is either
not connected or is even used for a different function. For ex
On 2025-01-12 15:09, Sergey Ryazanov wrote:
atm_qos struct should be the same both for user and kernel spaces. Via
the __SO_ENCODE() macro it is used to define the SO_ATMQOS socket IOC.
During the VRX518 support introduction, the atm_trafprm sturct nested
into the atm_qos stucture was update wit
On 2025-01-13 23:27, Sergey Ryazanov wrote:
Hi Andre, Martin,
On 13.01.2025 14:17, Andre Heider wrote:
On 13/01/2025 9:17 am, Martin Schiller wrote:
On 2025-01-12 15:09, Sergey Ryazanov wrote:
atm_qos struct should be the same both for user and kernel spaces.
Via
the __SO_ENCODE() macro it
On 2025-03-05 14:48, Robert Marko wrote:
On Wed, 5 Mar 2025 at 14:43, Martin Schiller wrote:
CONFIG_MITIGATE_SPECTRE_BRANCH_HISTORY was disabled with commit
6b007d2512ad (treewide: disable spectre mitigation on unaffected Arm64
targets) for all targets in target/linux/mediatek/filogic folder
On 2025-03-05 14:33, Daniel Golle wrote:
On Wed, Mar 05, 2025 at 02:13:04PM +0100, Martin Schiller wrote:
CONFIG_MITIGATE_SPECTRE_BRANCH_HISTORY was disabled with commit
6b007d2512ad (treewide: disable spectre mitigation on unaffected Arm64
targets) for all targets in target/linux/mediatek
CONFIG_MITIGATE_SPECTRE_BRANCH_HISTORY was disabled with commit
6b007d2512ad (treewide: disable spectre mitigation on unaffected Arm64
targets) for all targets in target/linux/mediatek/filogic folder, but
the Arm Cortex-A73 in the Filogic 880 are affected [0].
So should we enable CONFIG_MITIGATE_
88 matches
Mail list logo
