AW: Mark lantiq and omap as source only

2023-05-05 Thread kestrel1...@t-online.de
Hi,

why is it not feasible to add a hack/patch, actually the suggested one in this 
thread:
https://patchwork.kernel.org/project/netdevbpf/patch/20220630212703.3280485-1-martin.blumensti...@googlemail.com/

Yes, it is not accepted by the kernel maintainers and yes, it keeps the 
unwanted or undesirable behaviour of flooding that the changes in dsa should 
try to avoid. But that should not keep the xrx200 based devices from continuing 
to work with 5.15 based openwrt.

The patch in the link above worked for me, I changed the line to 1344 and 
replaced max_ports with cpu_port. Then the error messages are gone and I guess 
the flooding still appears.

If you look at the thread above, it looks like a tremendous amount of work that 
needs to be done to implement it properly. How long will that take by people 
doing it as a hobby and having other things in life, 2 years?!

Daniel.


-Original-Nachricht-
Betreff: Re: Mark lantiq and omap as source only
Datum: 2023-05-03T08:34:25+0200
Von: "Nick" 
An: "openwrt-devel@lists.openwrt.org" 

On 5/3/23 02:53, Alexander 'lynxis' Couzens wrote:

> what are the problems with lantiq 5.15?
There are some issues with the fdb entries:
> lantiq_gswip driver (e.g.: gswip 1e108000.switch: port 4 failed to add 
> vid 1 to fdb: -22)
Ansuel describes here why this is so bad:
https://github.com/openwrt/openwrt/pull/12515#issuecomment-1531686673

Bests
Nick

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: Mark lantiq and omap as source only

2023-05-04 Thread Nick


On 5/4/23 17:51, Stijn Segers wrote:

Hi,

Robert Marko  schreef op 3 mei 2023 11:21:32 CEST:

On Wed, 3 May 2023 at 11:08, Nick  wrote:

I would also love to see a release. It is now already delayed more than
a month [0] (actual branching should be happening end of march).
However, I don't have a strong opinion on this. It's sad that lantiq
targets could be dropped. I will also try to fetch me some lantiq device
from somewhere to support fixing the fdb issues and re-adding it back to
23.X or fixing it before the branch.

I would also really like a new release to branch off sooner rather than later,
there has been plenty of time for all targets to stabilize on 5.15.

I fully agree. Seems source-only is the jolt that omap and lantiq need (I know 
the latter is a popular target).

Lots of people pining for 6.1 support in main etc, so let's branch that baby so 
we can move on.

Stijn


I wanted to do some cleanup (removing 5.10 completely) so we can soon 
release:

https://github.com/openwrt/openwrt/pull/12531

However, if we still keep omap and ath25 around without bumping them to 
5.15, build will give warnings in the form of:


/home/nick/openwrt/include/kernel-version.mk:11: *** Missing kernel 
version/hash file for 5.10. Please create 
/home/nick/openwrt/include/kernel-5.10.  Stop.



___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: Mark lantiq and omap as source only

2023-05-04 Thread Stijn Segers
Hi,

Robert Marko  schreef op 3 mei 2023 11:21:32 CEST:
>On Wed, 3 May 2023 at 11:08, Nick  wrote:
>>
>> I would also love to see a release. It is now already delayed more than
>> a month [0] (actual branching should be happening end of march).
>> However, I don't have a strong opinion on this. It's sad that lantiq
>> targets could be dropped. I will also try to fetch me some lantiq device
>> from somewhere to support fixing the fdb issues and re-adding it back to
>> 23.X or fixing it before the branch.
>
>I would also really like a new release to branch off sooner rather than later,
>there has been plenty of time for all targets to stabilize on 5.15.

I fully agree. Seems source-only is the jolt that omap and lantiq need (I know 
the latter is a popular target).

Lots of people pining for 6.1 support in main etc, so let's branch that baby so 
we can move on.

Stijn

>
>Regards,
>Robert
>
>>
>> If you branch soon, you could probably also give a talk about the new
>> OpenWrt release at Battlemesh v15. ;)
>>
>> Bests
>> Nick
>>
>> [0] - https://openwrt.org/meetings/20230124
>>
>> On 5/1/23 18:01, Paul Spooren wrote:
>> > Hi all,
>> >
>> > I haven’t seen much progress happening regarding bringing the targets 
>> > lantiq or omap to Kernel 5.15. That fact is currently the last blocker for 
>> > branching another release.
>> >
>> > Instead of postponing another release I’d like to mark both targets as 
>> > source-only and do the 23.05 branch, starting with a RC0. If either of the 
>> > two targets are fixed within the RC phase, they should be re-added, as 
>> > discussed during the last meeting.
>> >
>> > I’d value your feedback.
>> >
>> > Sunshine,
>> > Paul
>> > ___
>> > openwrt-devel mailing list
>> > openwrt-devel@lists.openwrt.org
>> > https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>>
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>
>___
>openwrt-devel mailing list
>openwrt-devel@lists.openwrt.org
>https://lists.openwrt.org/mailman/listinfo/openwrt-devel

-- 
Verstuurd vanaf mijn Android apparaat met K-9 Mail. Excuseer mijn beknoptheid.

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: Mark lantiq and omap as source only

2023-05-03 Thread Aleksander Bajkowski


W dniu 03.05.2023 o 20:30, Nick pisze:


On 5/3/23 19:23, Aleksander Bajkowski wrote:


W dniu 03.05.2023 o 19:11, Nick pisze:

On 5/3/23 11:07, Nick wrote:

I will also try to fetch me some lantiq device from somewhere to 
support fixing the fdb issues and re-adding it back to 23.X or 
fixing it before the branch. 
I organized myself now a **FRITZ!Box 7320** and **TP Link 
TD-W8970**. So if anyone wants me to test anything just write me. 
Meanwhile I will also have a look at this issue.



This issue only affects the xrx200 target (gswip driver). AVM 7320 is 
supported by the xway subtarget and has built-in tantos switch.

The TP Link TD-W8970 is a xrx200 target. :)
So we just could have disabled the xrx200 target instead of setting 
the whole target to source only?




Yes, I think it's a good idea.


I made a mistake, I have a 7330. However, I have also some network 
issues with this device (no connectity to device but a link).




This is a known limitation on the AVM 7320/7330. The DSA driver for this 
switch is missing. Only the first ethernet port works only if the cable 
is connected at boot. Some time ago I acquired an AVM 7330 and started 
writing a driver to replace the patch carried downstream.




Bests
Nick

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: Mark lantiq and omap as source only

2023-05-03 Thread Felix Baumann
Am 3. Mai 2023 20:30:11 MESZ schrieb Nick :
>
>On 5/3/23 19:23, Aleksander Bajkowski wrote:
>> 
>> W dniu 03.05.2023 o 19:11, Nick pisze:
>>> On 5/3/23 11:07, Nick wrote:
>>> 
 I will also try to fetch me some lantiq device from somewhere to support 
 fixing the fdb issues and re-adding it back to 23.X or fixing it before 
 the branch. 
>>> I organized myself now a **FRITZ!Box 7320** and **TP Link TD-W8970**. So if 
>>> anyone wants me to test anything just write me. Meanwhile I will also have 
>>> a look at this issue.
>> 
>> 
>> This issue only affects the xrx200 target (gswip driver). AVM 7320 is 
>> supported by the xway subtarget and has built-in tantos switch.
>The TP Link TD-W8970 is a xrx200 target. :)
>So we just could have disabled the xrx200 target instead of setting the whole 
>target to source only?
>
>I made a mistake, I have a 7330. However, I have also some network issues with 
>this device (no connectity to device but a link).
>
>Bests
>Nick
>
>___
>openwrt-devel mailing list
>openwrt-devel@lists.openwrt.org
>https://lists.openwrt.org/mailman/listinfo/openwrt-devel

The Fritz!Box 7330 has always had broken ethernet.
https://github.com/freifunk-gluon/gluon/issues/1943
https://github.com/openwrt/openwrt/issues/7125

I suppose you could fix that as well, but maybe you should focus on 5.15 on the 
TD-W8970.


Regards
Felix Baumann

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: Mark lantiq and omap as source only

2023-05-03 Thread Nick


On 5/3/23 19:23, Aleksander Bajkowski wrote:


W dniu 03.05.2023 o 19:11, Nick pisze:

On 5/3/23 11:07, Nick wrote:

I will also try to fetch me some lantiq device from somewhere to 
support fixing the fdb issues and re-adding it back to 23.X or 
fixing it before the branch. 
I organized myself now a **FRITZ!Box 7320** and **TP Link TD-W8970**. 
So if anyone wants me to test anything just write me. Meanwhile I 
will also have a look at this issue.



This issue only affects the xrx200 target (gswip driver). AVM 7320 is 
supported by the xway subtarget and has built-in tantos switch.

The TP Link TD-W8970 is a xrx200 target. :)
So we just could have disabled the xrx200 target instead of setting the 
whole target to source only?


I made a mistake, I have a 7330. However, I have also some network 
issues with this device (no connectity to device but a link).


Bests
Nick

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: Mark lantiq and omap as source only

2023-05-03 Thread Aleksander Bajkowski


W dniu 03.05.2023 o 19:11, Nick pisze:

On 5/3/23 11:07, Nick wrote:

I will also try to fetch me some lantiq device from somewhere to 
support fixing the fdb issues and re-adding it back to 23.X or fixing 
it before the branch. 
I organized myself now a **FRITZ!Box 7320** and **TP Link TD-W8970**. 
So if anyone wants me to test anything just write me. Meanwhile I will 
also have a look at this issue.



This issue only affects the xrx200 target (gswip driver). AVM 7320 is 
supported by the xway subtarget and has built-in tantos switch.





Bests
Nick

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: Mark lantiq and omap as source only

2023-05-03 Thread Nick

On 5/3/23 11:07, Nick wrote:

I will also try to fetch me some lantiq device from somewhere to 
support fixing the fdb issues and re-adding it back to 23.X or fixing 
it before the branch. 
I organized myself now a **FRITZ!Box 7320** and **TP Link TD-W8970**. So 
if anyone wants me to test anything just write me. Meanwhile I will also 
have a look at this issue.


Bests
Nick

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: Mark lantiq and omap as source only

2023-05-03 Thread Robert Marko
On Wed, 3 May 2023 at 11:08, Nick  wrote:
>
> I would also love to see a release. It is now already delayed more than
> a month [0] (actual branching should be happening end of march).
> However, I don't have a strong opinion on this. It's sad that lantiq
> targets could be dropped. I will also try to fetch me some lantiq device
> from somewhere to support fixing the fdb issues and re-adding it back to
> 23.X or fixing it before the branch.

I would also really like a new release to branch off sooner rather than later,
there has been plenty of time for all targets to stabilize on 5.15.

Regards,
Robert

>
> If you branch soon, you could probably also give a talk about the new
> OpenWrt release at Battlemesh v15. ;)
>
> Bests
> Nick
>
> [0] - https://openwrt.org/meetings/20230124
>
> On 5/1/23 18:01, Paul Spooren wrote:
> > Hi all,
> >
> > I haven’t seen much progress happening regarding bringing the targets 
> > lantiq or omap to Kernel 5.15. That fact is currently the last blocker for 
> > branching another release.
> >
> > Instead of postponing another release I’d like to mark both targets as 
> > source-only and do the 23.05 branch, starting with a RC0. If either of the 
> > two targets are fixed within the RC phase, they should be re-added, as 
> > discussed during the last meeting.
> >
> > I’d value your feedback.
> >
> > Sunshine,
> > Paul
> > ___
> > openwrt-devel mailing list
> > openwrt-devel@lists.openwrt.org
> > https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: Mark lantiq and omap as source only

2023-05-03 Thread Nick
I would also love to see a release. It is now already delayed more than 
a month [0] (actual branching should be happening end of march). 
However, I don't have a strong opinion on this. It's sad that lantiq 
targets could be dropped. I will also try to fetch me some lantiq device 
from somewhere to support fixing the fdb issues and re-adding it back to 
23.X or fixing it before the branch.


If you branch soon, you could probably also give a talk about the new 
OpenWrt release at Battlemesh v15. ;)


Bests
Nick

[0] - https://openwrt.org/meetings/20230124

On 5/1/23 18:01, Paul Spooren wrote:

Hi all,

I haven’t seen much progress happening regarding bringing the targets lantiq or 
omap to Kernel 5.15. That fact is currently the last blocker for branching 
another release.

Instead of postponing another release I’d like to mark both targets as 
source-only and do the 23.05 branch, starting with a RC0. If either of the two 
targets are fixed within the RC phase, they should be re-added, as discussed 
during the last meeting.

I’d value your feedback.

Sunshine,
Paul
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: Mark lantiq and omap as source only

2023-05-02 Thread Nick

On 5/3/23 02:53, Alexander 'lynxis' Couzens wrote:


what are the problems with lantiq 5.15?

There are some issues with the fdb entries:
lantiq_gswip driver (e.g.: gswip 1e108000.switch: port 4 failed to add 
vid 1 to fdb: -22)

Ansuel describes here why this is so bad:
https://github.com/openwrt/openwrt/pull/12515#issuecomment-1531686673

Bests
Nick

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: Mark lantiq and omap as source only

2023-05-02 Thread Alexander 'lynxis' Couzens
Hi Paul,

> I haven’t seen much progress happening regarding bringing the targets lantiq 
> or omap to Kernel 5.15. That fact is currently the last blocker for branching 
> another release.

> Instead of postponing another release I’d like to mark both targets as 
> source-only and do the 23.05 branch, starting with a RC0. If either of the 
> two targets are fixed within the RC phase, they should be re-added, as 
> discussed during the last meeting.

what are the problems with lantiq 5.15?

For omap:
- The upstream kernel changed the ethernet default and the driver will use 2 
static vlan ids (configurable via dts) to tag the traffic
of port 1 and port 2.

ACK for OMAP. I'll try to fix it before the release.

Best,
lynxis

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Mark lantiq and omap as source only

2023-05-01 Thread Paul Spooren
Hi all,

I haven’t seen much progress happening regarding bringing the targets lantiq or 
omap to Kernel 5.15. That fact is currently the last blocker for branching 
another release.

Instead of postponing another release I’d like to mark both targets as 
source-only and do the 23.05 branch, starting with a RC0. If either of the two 
targets are fixed within the RC phase, they should be re-added, as discussed 
during the last meeting.

I’d value your feedback.

Sunshine,
Paul
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel