From: Ian Chang
1. Add support for Marvell CN9130 SoC
2. Add support for CP115,and create an armada-cp11x.dtsi file which will be
used to instantiate both CP110 and CP115
3. Add support for AP807/AP807-quad,AP807 is a major component of CN9130 SoC
series
4. Drop PCIe I/O ranges from CP11x f
From: Ian Chang
Hardware specification
--
* CN9130 SoC, Quad-core ARMv8 Cortex-72 @ 2200 MHz
* 4 GB DDR
* 4 GB eMMC
* mmcblk0
- mmcblk0p164M kernel_1
- mmcblk0p264M kernel_2
- mmcblk0p3 512M rootfs_1
- mmcblk0p4 512M rootfs_2
- mmcblk0p5 512M Rese
On 29.08.21 22:44, Michael Richardson wrote:
> Fabian Bläse wrote:
> > Frames between untagged ports (e.g. eth0 and eth1) are forwarded
> > correctly and frames between tagged ports (eg. eth3 and eth4) are
> > forwarded correctly.
>
> It sounds like the hardware bridge expects the host to do the
{I'm ignorant about most things DSA, and I'm asking for clarification}
Fabian Bläse wrote:
> In the above configuration, frames between Ethernet port eth0 (vlan2
> untagged) and port eth4 (vlan2 tagged) are not
> forwarded. Interestingly, the router itself is able to reach devices
I have tested this patch, and it does seem to fix the issue, as already
suspected.
I have created a backport for kernel 5.4 and submitted a pull request:
https://github.com/openwrt/openwrt/pull/4493
This should also be be considered for openwrt-21.02.
Best regards,
Fabian
OpenPGP_signature
D
On 7/1/21 10:06 AM, Martin Blumenstingl wrote:
Hi Martin,
On Thu, Jul 1, 2021 at 8:02 AM Martin Schiller wrote:
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 DSA
The default value for CONFIG_RCU_CPU_STALL_TIMEOUT was changed from 60
seconds to 21 seconds in 2012 in the upstream kernel. Some targets
already use 21 seconds.
This patch changes the default value in the generic configuration to 21
seconds and removes the target specific configuration options.
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 ---
Branch: refs/heads/master
Home
Possibly related:
-
https://github.com/torvalds/linux/commit/07c6f9805f12f1bb538ef165a092b300350384aa
- https://lore.kernel.org/netdev/20191222192235.gk25...@shell.armlinux.org.uk/
(discussion to the patch from above)
Best regards,
Fabian
___
openwrt-
Hi,
I am having issues with a bridge-in-bridge configuration on the Edgerouter X
with DSA on OpenWrt 21.02 rc4.
If a vlan-aware bridge is configured for the build-in ethernet ports, and a
vlan-interface on that bridge is then put into a different bridge (to include
wifi radios for example), th
On Aug 29, 2021, at 6:31 AM, Hannu Nyman wrote:
>
> Hauke Mehrtens wrote at Sun Aug 29 02:53:47 PDT 2021:
>
> We have now reverted back to the old "let's wait long for branching and then
> wait even longer for the actual release".
>
> The reality is the same than earlier: almost all devs and e
Hi Hauke
Op zondag 29 augustus 2021 om 11u53 schreef Hauke Mehrtens
:
Hi,
We did the 21.02-rc4, but there is still a problem with flow
offloading as this was not fixed. The other problems should be fixed
now.
On 7/17/21 5:45 PM, Hauke Mehrtens wrote:
Currently we still have these problem:
Hi Andre,
I pushed this to 21.02 now.
Hauke
On 8/24/21 12:21 AM, Andre Heider wrote:
Nice, sounds good, thanks!
On 23/08/2021 23:12, Hauke Mehrtens wrote:
Hi Andre,
I will backport this to 21.02 in the next days. I want to wait if
there are more problems showing up in master.
Hauke
On 8
On build termination I have the current error.
The error comes from the building of an initramfs with lzo compression selected
The build env is ubuntu with devel package selected.
make[5]: Entering directory
'/home/ansuel/openwrt/build_dir/target-arm_cortex-a15+neon-vfpv4_musl_eabi/linux-ipq806x_g
+1 for finally releasing. Our wireless mesh community is testing OpenWrt
21.02-snapshot now for months.
Only some trouble with ipq40xx soc, but we have workarounds for it.
On 8/29/21 12:53 PM, Adrian Schmutzler wrote:
Hi,
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-bo
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Hauke Mehrtens
> Sent: Sonntag, 29. August 2021 11:54
> To: OpenWrt Development List
> Cc: John Crispin; Jo-Philipp Wich; Kevin 'ldir' Darbyshire-Bryant
> Subject: Re: OpenWrt 21.
Am Mon, Aug 23, 2021 at 11:12:00PM +0200 schrieb Hauke Mehrtens:
> Hi Andre,
>
> I will backport this to 21.02 in the next days. I want to wait if there are
> more problems showing up in master.
>
> Hauke
Hello Hauke, all,
Were there any problems showing up? Or is this good to go into 21.02?
Kin
Hauke Mehrtens wrote at Sun Aug 29 02:53:47 PDT 2021:
> Should we just release with this as a known problem?
>
> Other than this problem I am not aware of any other critical problem.
We should.
It is annoying that 21.02 was branched more than 6 months ago, but no final
release has happened by
Hi,
We did the 21.02-rc4, but there is still a problem with flow offloading
as this was not fixed. The other problems should be fixed now.
On 7/17/21 5:45 PM, Hauke Mehrtens wrote:
Currently we still have these problem:
- IPv6 broken with flow offloading (according to reports, potentially
r
19 matches
Mail list logo
