Re: [PATCH v4 2/2] ramips: add support for Wavlink WS-WN572HP3 4G

2022-12-01 Thread Arınç ÜNAL
On 30.11.2022 23:35, Jan-Niklas Burfeind wrote: Wavlink WS-WN572HP3 4G is an 802.11ac dual-band outdoor router with LTE support. Specifications; * Soc: MT7621DAT * RAM: 128MiB * Flash: NOR 16MiB GD-25Q128ESIG3 * Wi-Fi: * MT7613BEN: 5GHz * MT7603EN: 2.4GHz * Ethernet: 2x 1GbE * USB: None -

Re: [PATCH v4 2/2] ramips: add support for Wavlink WS-WN572HP3 4G

2022-12-01 Thread Jan-Niklas Burfeind
On 12/1/22 09:25, Arınç ÜNAL wrote: On 30.11.2022 23:35, Jan-Niklas Burfeind wrote: Wavlink WS-WN572HP3 4G is an 802.11ac dual-band outdoor router with LTE support. Specifications; * Soc: MT7621DAT * RAM: 128MiB * Flash: NOR 16MiB GD-25Q128ESIG3 * Wi-Fi:    * MT7613BEN: 5GHz    * MT7603EN: 2.4G

[PATCH 22.03] mvebu: cortexa9: disable devices using broken mv88e6176 switch

2022-12-01 Thread Petr Štetiar
Several users have reported, that devices using mv88e6176 switch are seriously broken, basically turning that switch into a hub. Until fixed those devices should be disabled. I've used TOH with "Switch 88E6176" filter, which provided me with the following list of likely affected devices: * Links

Re: [PATCH 22.03] mvebu: cortexa9: disable devices using broken mv88e6176 switch

2022-12-01 Thread Uwe Kleine-König
On 12/1/22 10:52, Petr Štetiar wrote: Several users have reported, that devices using mv88e6176 switch are seriously broken, basically turning that switch into a hub. Until fixed those devices should be disabled. I've used TOH with "Switch 88E6176" filter, which provided me with the following li

Re: [PATCH 22.03] mvebu: cortexa9: disable devices using broken mv88e6176 switch

2022-12-01 Thread Petr Štetiar
Uwe Kleine-König [2022-12-01 12:17:31]: Hi Uwe, > On 12/1/22 10:52, Petr Štetiar wrote: > > Several users have reported, that devices using mv88e6176 switch are > > seriously broken, basically turning that switch into a hub. Until fixed > > those devices should be disabled. > > I wonder if disa

Re: at803x SFP support regression in 22.03

2022-12-01 Thread Arınç ÜNAL
René van Dorst worked on this here: https://github.com/openwrt/openwrt/blob/master/target/linux/ramips/patches-5.10/710-at803x.patch Their mail doesn't seem to work anymore. Arınç On 30.11.2022 14:49, David Collett wrote: Hi All, I am using an SFP module in a MikroTik RouterBOARD 760iGS. It

Re: at803x SFP support regression in 22.03

2022-12-01 Thread Arınç ÜNAL
David Bauer also did some work on it. CC'ing. On 1.12.2022 15:01, Arınç ÜNAL wrote: René van Dorst worked on this here: https://github.com/openwrt/openwrt/blob/master/target/linux/ramips/patches-5.10/710-at803x.patch Their mail doesn't seem to work anymore. Arınç On 30.11.2022 14:49, David

Re: at803x SFP support regression in 22.03

2022-12-01 Thread Arınç ÜNAL
There's this reply under one of David's patches. Give this a try. Let me know if you need help with git. https://github.com/openwrt/openwrt/commit/15167671b0d7cf0c95568dd6f9620db082df5d96#commitcomment-51920086 Arınç On 1.12.2022 15:07, Arınç ÜNAL wrote: David Bauer also did some work on it.

Re: [PATCH 22.03] mvebu: cortexa9: disable devices using broken mv88e6176 switch

2022-12-01 Thread Bjørn Mork
I assume KERNEL_PATCHVER in target/linux/mvebu/Makefile will be fixed in master as well, given that 5.10 is unsupportable on this target? Bjørn ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/op

Re: [PATCH 22.03] mvebu: cortexa9: disable devices using broken mv88e6176 switch

2022-12-01 Thread Josef Schlehofer
On 01. 12. 22 14:19, Bjørn Mork wrote: I assume KERNEL_PATCHVER in target/linux/mvebu/Makefile will be fixed in master as well, given that 5.10 is unsupportable on this target? AFAIK What should be done is to put the kernel 5.15 as the default kernel for mvebu. Currently, it is only as the tes

Re: [PATCH 22.03] mvebu: cortexa9: disable devices using broken mv88e6176 switch

2022-12-01 Thread Enrico Mioso
My 2 cents here. My (very possibly wrong) impression, this seems the same way of thinking followed in commit db19efee951231b38573cffaadb15fad8f9c058d . I can understand this is a strong way to convince people to care about specific issues. Still, this seems a bit rude to me. On the other side, I

Re: [PATCH 22.03] mvebu: cortexa9: disable devices using broken mv88e6176 switch

2022-12-01 Thread Christian Marangi
On Thu, Dec 01, 2022 at 02:23:08PM +0100, Josef Schlehofer wrote: > On 01. 12. 22 14:19, Bjørn Mork wrote: > > > I assume KERNEL_PATCHVER in target/linux/mvebu/Makefile will be fixed in > > master as well, given that 5.10 is unsupportable on this target? > > > AFAIK What should be done is to put

Re: [PATCH 22.03] mvebu: cortexa9: disable devices using broken mv88e6176 switch

2022-12-01 Thread Robert Marko
On Thu, 1 Dec 2022 at 14:34, Christian Marangi wrote: > > On Thu, Dec 01, 2022 at 02:23:08PM +0100, Josef Schlehofer wrote: > > On 01. 12. 22 14:19, Bjørn Mork wrote: > > > > > I assume KERNEL_PATCHVER in target/linux/mvebu/Makefile will be fixed in > > > master as well, given that 5.10 is unsuppo

Re: [PATCH 22.03] mvebu: cortexa9: disable devices using broken mv88e6176 switch

2022-12-01 Thread Christian Marangi
On Thu, Dec 01, 2022 at 02:39:56PM +0100, Robert Marko wrote: > On Thu, 1 Dec 2022 at 14:34, Christian Marangi wrote: > > > > On Thu, Dec 01, 2022 at 02:23:08PM +0100, Josef Schlehofer wrote: > > > On 01. 12. 22 14:19, Bjørn Mork wrote: > > > > > > > I assume KERNEL_PATCHVER in target/linux/mvebu/

Re: [PATCH 22.03] mvebu: cortexa9: disable devices using broken mv88e6176 switch

2022-12-01 Thread Robert Marko
On Thu, 1 Dec 2022 at 14:43, Christian Marangi wrote: > > On Thu, Dec 01, 2022 at 02:39:56PM +0100, Robert Marko wrote: > > On Thu, 1 Dec 2022 at 14:34, Christian Marangi wrote: > > > > > > On Thu, Dec 01, 2022 at 02:23:08PM +0100, Josef Schlehofer wrote: > > > > On 01. 12. 22 14:19, Bjørn Mork w

Developer Meeting November 2022

2022-12-01 Thread Paul Spooren
Hi all, please find our notes from yesterdays meeting below: https://openwrt.org/meetings/20221130 Feel free to comment in this thread. Sunshine, Paul ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/lis

[PATCH v4 1/3] bcm63xx: kernel: enable the tplink image parser

2022-12-01 Thread Daniel González Cabanelas
Enable the tplink mtd firmware splitter to allow booting images with tplink headers. Since known devices with these headers are dual core, only enable this driver in the SMP subtarget. Signed-off-by: Daniel González Cabanelas --- Changes in v2: no changes Changes in v3: cosmetic Changes in v4:

[PATCH v4 2/3] bcm63xx: build tplink images

2022-12-01 Thread Daniel González Cabanelas
Add macros and a python script to build images compatible with tplink CFE bootloaders. Signed-off-by: Daniel González Cabanelas --- Changes in v2: - factory image fixed. (cfe-tplink-crcfix.py doesn't work if CFE already prepended) Changes in v3: - fixed name in temp files for prepending CFE

[PATCH v4 3/3] bcm63xx: add support for Tp-Link Archer VR400 v1

2022-12-01 Thread Daniel González Cabanelas
The Archer VR400 v1 is an EOL xDSL router with 802.11bgn/802.11ac wifi. Hardware: - SoC: Broadcom BCM63167 - CPU: dual core BMIPS4350 V8.0 @400MHz - RAM: 128 MB DDR2 - Flash: 16 MB SPI NOR - Ethernet LAN: 3x 100Mbit - Ethernet WAN: 1x GbE - Wifi 2.4 GHz: SoC integrated BCM435F 802.11b/g/n

Re: Developer Meeting November 2022

2022-12-01 Thread Nathan Lutchansky
On Thu, 1 Dec 2022, Paul Spooren wrote: Hi all, please find our notes from yesterdays meeting below: https://openwrt.org/meetings/20221130 Feel free to comment in this thread. Hi, Thank you for posting this. Regarding the various SSL/TLS libraries available as options in OpenWrt, could th

Re: Developer Meeting November 2022

2022-12-01 Thread Nicholas Smith
If a move from Github is inevitable, should we continue investing in Github, i.e. start auto-labelling tickets, making new templates, etc? For auto-closing bugs, perhaps a good policy is to auto-close bugs for any unsupported release. We could automate notifications to the reporters to let them kn

Re: [PATCH] realtek: fix dell typo

2022-12-01 Thread Sander Vanheule
On Mon, 2022-11-28 at 17:58 +0100, Jan-Niklas Burfeind wrote: > should be add/delete or abbreviated add/del > > Signed-off-by: Jan-Niklas Burfeind Merged to master. Thanks! Sander ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https:/

Re: [PATCH buildbot] docker,worker: install g++-multilib

2022-12-01 Thread Glenn Washburn
Thread OP is strangely formatted so my mail client isn't quoting the message properly and I've just inline copied the original and top posting. I've seen no response to this so I presume that nothing is being done about it and I'd like to see this fixed. Who is in charge of the build server? How c

Re: [PATCH buildbot] docker,worker: install g++-multilib

2022-12-01 Thread Website Alois 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 --- On Thursday, December 1st, 2022 at

Re: Developer Meeting November 2022

2022-12-01 Thread Shawn Shaw
Openssl is 1000KB it should be good for 16MB and above(instead of 128MB), below 16MB then mbedtls can be used. In fact openssl can probably be used on 8MB as well, there is just not much space left for extra packages. Shawn ___ openwrt-devel mailing lis