Re: [PATCH] Fix tx-queue-size on NBG6817 (allows MTU changes).
On 22/09/2020 00:06, Ansuel Smith wrote: On 19/09/2020 15:06, Paul Oranje wrote: See below, regards, Paul Op 15 sep. 2020, om 21:56 heeft jacekow...@jacekowski.org het volgende geschreven: The subject does not to comply with the rules for that, it should at least start with the target, better would be: ipq806x: fix tx-queue-size on NBG6817 I was not aware of that. From: Jacek Milewicz Fixes FS#3285 for NBG6817 only. Why is that ? Because on IPQ806x SoC it is impossible to detect correct value, therefore it has to be set for each device in device tree (which is what this patch is doing). On most IPQ806x devices correct value has to be determined manually by trying few most common values and seeing what works (4k seems to be most common). Can I ask you how you found out and how to check if a bad value is set? Is this set by default on the OEM firmware? Any test or something? OEM firmware runs older kernel that does not check for tx-fifo-depth at all (https://patchwork.kernel.org/patch/11283121/ - this patch, dated December 2019 added the check). There is only few values that the driver will accept (256,512,1k,2k,4,8k,16k), so the easiest way to check is set it to highest (16k) and then try increasingly higher MTU to check at what point does it start dropping packets or crashing (and it seems like 4k is fairly common value on this SoC). ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH] Fix tx-queue-size on NBG6817 (allows MTU changes).
On 19/09/2020 15:06, Paul Oranje wrote:
See below, regards,
Paul
Op 15 sep. 2020, om 21:56 heeft jacekow...@jacekowski.org het volgende
geschreven:
The subject does not to comply with the rules for that, it should at least
start with the target, better would be:
ipq806x: fix tx-queue-size on NBG6817
I was not aware of that.
From: Jacek Milewicz
Fixes FS#3285 for NBG6817 only.
Why is that ?
Because on IPQ806x SoC it is impossible to detect correct value,
therefore it has to be set for each device in device tree (which is what
this patch is doing).
On most IPQ806x devices correct value has to be determined manually by
trying few most common values and seeing what works (4k seems to be most
common).
Signed-off-by: Jacek Milewicz
---
.../files-4.14/arch/arm/boot/dts/qcom-ipq8065-nbg6817.dts | 2 ++
1 file changed, 2 insertions(+)
diff --git
a/target/linux/ipq806x/files-4.14/arch/arm/boot/dts/qcom-ipq8065-nbg6817.dts
b/target/linux/ipq806x/files-4.14/arch/arm/boot/dts/qcom-ipq8065-nbg6817.dts
index 7cd1c7b567..5745040d2b 100644
--- a/target/linux/ipq806x/files-4.14/arch/arm/boot/dts/qcom-ipq8065-nbg6817.dts
+++ b/target/linux/ipq806x/files-4.14/arch/arm/boot/dts/qcom-ipq8065-nbg6817.dts
@@ -289,6 +289,7 @@
qcom,emulation = <0>;
qcom,irq = <255>;
mdiobus = <>;
+ tx-fifo-depth = <4096>;
pinctrl-0 = <_pins>;
pinctrl-names = "default";
@@ -310,6 +311,7 @@
qcom,emulation = <0>;
qcom,irq = <258>;
mdiobus = <>;
+ tx-fifo-depth = <4096>;
fixed-link {
speed = <1000>;
--
2.17.1
___
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
