armada 370 (88f6710) mainline uboot support
Posted by wacke
|
Re: armada 370 (88f6710) mainline uboot support December 05, 2018 05:11PM |
Admin Registered: 14 years ago Posts: 19,910 |
Hi wacke,
Not really. Have been too busy to do research. That Armada 370 box is arriving, though. This issue is highest on my priority list to do :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Not really. Have been too busy to do research. That Armada 370 box is arriving, though. This issue is highest on my priority list to do :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support December 26, 2018 12:12PM |
Registered: 7 years ago Posts: 264 |
Looks like the issue with the temperature sensor was due to a bug that was introduced when they made the binding changes rather than the changes themselves.
a patch was recently accepted into the mainline kernel to fix it:
https://github.com/torvalds/linux/commit/70bb27b79adf63ea39e37371d09c823c7a8f93ce
Edited 1 time(s). Last edit at 12/27/2018 08:22AM by 1000001101000.
a patch was recently accepted into the mainline kernel to fix it:
https://github.com/torvalds/linux/commit/70bb27b79adf63ea39e37371d09c823c7a8f93ce
Edited 1 time(s). Last edit at 12/27/2018 08:22AM by 1000001101000.
|
Re: armada 370 (88f6710) mainline uboot support December 26, 2018 04:09PM |
Admin Registered: 14 years ago Posts: 19,910 |
1000001101000,
> Looks like the issue with the temperature sensor
> was due to a bug that was introduced when they
> made the binding changes rather than the changes
> themselves.
Thanks for the patch :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Looks like the issue with the temperature sensor
> was due to a bug that was introduced when they
> made the binding changes rather than the changes
> themselves.
Thanks for the patch :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support January 05, 2019 02:14AM |
Registered: 10 years ago Posts: 166 |
|
Re: armada 370 (88f6710) mainline uboot support January 05, 2019 02:35AM |
Admin Registered: 14 years ago Posts: 19,910 |
Hi wacke,
I've receivd my 370 board, but it was too close to the start of my trip. I will be back the end of this month.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
I've receivd my 370 board, but it was too close to the start of my trip. I will be back the end of this month.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support February 09, 2019 07:30AM |
Registered: 10 years ago Posts: 166 |
|
Re: armada 370 (88f6710) mainline uboot support February 09, 2019 12:51PM |
Admin Registered: 14 years ago Posts: 19,910 |
wacke,
I'm back. Have not booted up my a370 board yet! it will take a while to acclimate to my normal time zone :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
I'm back. Have not booted up my a370 board yet! it will take a while to acclimate to my normal time zone :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support February 28, 2019 07:01PM |
Registered: 10 years ago Posts: 166 |
|
Re: armada 370 (88f6710) mainline uboot support February 28, 2019 09:07PM |
Admin Registered: 14 years ago Posts: 19,910 |
wacke Wrote:
-------------------------------------------------------
> Hi bodhi,
> Did you boot up your a370 board?
Not yet!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> Hi bodhi,
> Did you boot up your a370 board?
Not yet!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support March 01, 2019 05:44AM |
Admin Registered: 14 years ago Posts: 19,910 |
But I do hope to spend a few hours to get this box running this weekend :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support March 03, 2019 10:51PM |
Admin Registered: 14 years ago Posts: 19,910 |
wacke,
Booted up my Armada 370 board. And having problem right away :) it was previously own and root credential seems to have been changed (not root/nosoup4u anymore).
And also some problem booting the latest Debian rootfs (might be a remnant of previous botched attempt of hacking).
I can kwboot, so not a problem to restoring original stock FW. Might have to look for it, though.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Booted up my Armada 370 board. And having problem right away :) it was previously own and root credential seems to have been changed (not root/nosoup4u anymore).
And also some problem booting the latest Debian rootfs (might be a remnant of previous botched attempt of hacking).
I can kwboot, so not a problem to restoring original stock FW. Might have to look for it, though.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support March 04, 2019 01:25AM |
Registered: 10 years ago Posts: 166 |
bodhi Wrote:
-------------------------------------------------------
> wacke,
>
> Booted up my Armada 370 board. And having problem
> right away :) it was previously own and root
> credential seems to have been changed (not
> root/nosoup4u anymore).
>
Hi bodhi,
Great news! And the uboot for armada 370 will be the next step?
-------------------------------------------------------
> wacke,
>
> Booted up my Armada 370 board. And having problem
> right away :) it was previously own and root
> credential seems to have been changed (not
> root/nosoup4u anymore).
>
Hi bodhi,
Great news! And the uboot for armada 370 will be the next step?
|
Re: armada 370 (88f6710) mainline uboot support March 04, 2019 02:21AM |
Admin Registered: 14 years ago Posts: 19,910 |
wacke,
> Great news! And the uboot for armada 370 will be
> the next step?
I hope to get this booting Debian first.
Indeed, the next fun thing for me to work on is to build a new u-boot for at least one of Armada 370/380 series. This 370 box is quite convenient in that I know I can kwboot a recovery uboot at will :) The Thecus N2350 is also good, but not as convenient with the serial console inside that needs soldering (I just wire a temp serial console on the Thecus when needed).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Great news! And the uboot for armada 370 will be
> the next step?
I hope to get this booting Debian first.
Indeed, the next fun thing for me to work on is to build a new u-boot for at least one of Armada 370/380 series. This 370 box is quite convenient in that I know I can kwboot a recovery uboot at will :) The Thecus N2350 is also good, but not as convenient with the serial console inside that needs soldering (I just wire a temp serial console on the Thecus when needed).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support March 14, 2019 08:57PM |
Registered: 10 years ago Posts: 166 |
|
Re: armada 370 (88f6710) mainline uboot support March 14, 2019 09:32PM |
Admin Registered: 14 years ago Posts: 19,910 |
wacke,
https://forum.doozan.com/read.php?2,41809,80659#msg-80659
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
https://forum.doozan.com/read.php?2,41809,80659#msg-80659
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support March 14, 2019 10:00PM |
Registered: 10 years ago Posts: 166 |
|
Re: armada 370 (88f6710) mainline uboot support March 14, 2019 10:11PM |
Admin Registered: 14 years ago Posts: 19,910 |
wacke,
> Hi bodhi,
> So my box also can use this kernel?
Not sure. You need to try. If you have serial console, post serial console boot log.
I need to see what uboot version you have, and the DTS (if you are booting FDT kernel currently).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Hi bodhi,
> So my box also can use this kernel?
Not sure. You need to try. If you have serial console, post serial console boot log.
I need to see what uboot version you have, and the DTS (if you are booting FDT kernel currently).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support March 14, 2019 10:17PM |
Registered: 10 years ago Posts: 166 |
|
Re: armada 370 (88f6710) mainline uboot support March 15, 2019 12:09AM |
Admin Registered: 14 years ago Posts: 19,910 |
wacke,
I've looked at your previous posts. No, your board is using newer boot loader, the address indicated that.
So you should continue using the 4.16.7-mvebu-tld-1 or which ever you are on, or upgrade to the newer kernel 4.20.6-mvebu-tld-1 .
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/15/2019 12:15AM by bodhi.
I've looked at your previous posts. No, your board is using newer boot loader, the address indicated that.
soc {
ranges = <MBUS_ID(0xf0, 0x01) 0 0xf1000000 0x100000
MBUS_ID(0x01, 0xe0) 0 0xfff00000 0x100000
MBUS_ID(0x09, 0x01) 0 0xf1100000 0x10000>;
So you should continue using the 4.16.7-mvebu-tld-1 or which ever you are on, or upgrade to the newer kernel 4.20.6-mvebu-tld-1 .
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/15/2019 12:15AM by bodhi.
|
Re: armada 370 (88f6710) mainline uboot support March 15, 2019 12:26AM |
Registered: 10 years ago Posts: 166 |
bodhi Wrote:
-------------------------------------------------------
> wacke,
>
> So you should continue using the
> 4.16.7-mvebu-tld-1 or which ever you are on, or
> upgrade to the newer kernel 4.20.6-mvebu-tld-1 .
OK. Does the kernel 4.20.6-mvebu-tld-1 include the HW I/O patch for armada 370?
-------------------------------------------------------
> wacke,
>
> So you should continue using the
> 4.16.7-mvebu-tld-1 or which ever you are on, or
> upgrade to the newer kernel 4.20.6-mvebu-tld-1 .
OK. Does the kernel 4.20.6-mvebu-tld-1 include the HW I/O patch for armada 370?
|
Re: armada 370 (88f6710) mainline uboot support March 15, 2019 01:22AM |
Admin Registered: 14 years ago Posts: 19,910 |
wacke Wrote:
-------------------------------------------------------
> bodhi Wrote:
> -------------------------------------------------------
> > wacke,
> >
> > So you should continue using the
> > 4.16.7-mvebu-tld-1 or which ever you are on, or
> > upgrade to the newer kernel 4.20.6-mvebu-tld-1
> .
>
> OK. Does the kernel 4.20.6-mvebu-tld-1 include the
> HW I/O patch for armada 370?
No, it does not. That is something we still need to work on in the future.
Could you post the test where you measured the IO performance?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/15/2019 01:23AM by bodhi.
-------------------------------------------------------
> bodhi Wrote:
> -------------------------------------------------------
> > wacke,
> >
> > So you should continue using the
> > 4.16.7-mvebu-tld-1 or which ever you are on, or
> > upgrade to the newer kernel 4.20.6-mvebu-tld-1
> .
>
> OK. Does the kernel 4.20.6-mvebu-tld-1 include the
> HW I/O patch for armada 370?
No, it does not. That is something we still need to work on in the future.
Could you post the test where you measured the IO performance?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/15/2019 01:23AM by bodhi.
|
Re: armada 370 (88f6710) mainline uboot support March 15, 2019 05:48AM |
Registered: 10 years ago Posts: 166 |
Hi bodhi,
I used the iperf3 to test the IO performance.My box ip is 192.168.1.238.
My box to router (armada 385,Turris Omnia)
PC connected to my box:
Another PC to my box:
PC to PC through my box:
The test result seems that PC to my box get the low performance. But the switch was working properly.
I used the iperf3 to test the IO performance.My box ip is 192.168.1.238.
My box to router (armada 385,Turris Omnia)
root@debian:~# iperf3 -c 192.168.1.1 Connecting to host 192.168.1.1, port 5201 [ 4] local 192.168.1.238 port 50948 connected to 192.168.1.1 port 5201 [ ID] Interval Transfer Bandwidth Retr Cwnd [ 4] 0.00-1.02 sec 45.0 MBytes 370 Mbits/sec 1 139 KBytes [ 4] 1.02-2.01 sec 52.5 MBytes 446 Mbits/sec 0 171 KBytes [ 4] 2.01-3.01 sec 52.5 MBytes 440 Mbits/sec 0 199 KBytes [ 4] 3.01-4.02 sec 53.8 MBytes 448 Mbits/sec 0 199 KBytes [ 4] 4.02-5.01 sec 52.5 MBytes 445 Mbits/sec 0 202 KBytes [ 4] 5.01-6.01 sec 51.4 MBytes 430 Mbits/sec 0 205 KBytes [ 4] 6.01-7.00 sec 51.2 MBytes 433 Mbits/sec 0 208 KBytes [ 4] 7.00-8.00 sec 65.0 MBytes 546 Mbits/sec 10 287 KBytes [ 4] 8.00-9.02 sec 55.3 MBytes 455 Mbits/sec 0 297 KBytes [ 4] 9.02-10.01 sec 50.0 MBytes 423 Mbits/sec 0 297 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.01 sec 529 MBytes 443 Mbits/sec 11 sender [ 4] 0.00-10.01 sec 529 MBytes 443 Mbits/sec receiver iperf Done.
PC connected to my box:
root@debian:~# iperf3 -s ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- Accepted connection from 192.168.1.80, port 2165 [ 5] local 192.168.1.238 port 5201 connected to 192.168.1.80 port 2166 [ ID] Interval Transfer Bandwidth [ 5] 0.00-1.00 sec 14.5 MBytes 122 Mbits/sec [ 5] 1.00-2.01 sec 21.7 MBytes 181 Mbits/sec [ 5] 2.01-3.01 sec 24.2 MBytes 203 Mbits/sec [ 5] 3.01-4.01 sec 22.2 MBytes 186 Mbits/sec [ 5] 4.01-5.01 sec 23.8 MBytes 200 Mbits/sec [ 5] 5.01-6.01 sec 26.3 MBytes 220 Mbits/sec [ 5] 6.01-7.00 sec 26.6 MBytes 224 Mbits/sec [ 5] 7.00-8.01 sec 27.6 MBytes 232 Mbits/sec [ 5] 8.01-9.01 sec 27.9 MBytes 234 Mbits/sec [ 5] 9.01-10.00 sec 27.4 MBytes 231 Mbits/sec [ 5] 10.00-10.19 sec 5.21 MBytes 229 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 5] 0.00-10.19 sec 0.00 Bytes 0.00 bits/sec sender [ 5] 0.00-10.19 sec 248 MBytes 204 Mbits/sec receiver
Another PC to my box:
Wacke@HOME-Server:~> iperf3 -c 192.168.1.238 Connecting to host 192.168.1.238, port 5201 [ 5] local 192.168.1.2 port 48660 connected to 192.168.1.238 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 25.7 MBytes 216 Mbits/sec 131 221 KBytes [ 5] 1.00-2.00 sec 24.0 MBytes 201 Mbits/sec 0 296 KBytes [ 5] 2.00-3.00 sec 26.6 MBytes 223 Mbits/sec 108 243 KBytes [ 5] 3.00-4.00 sec 25.3 MBytes 212 Mbits/sec 83 205 KBytes [ 5] 4.00-5.00 sec 25.2 MBytes 212 Mbits/sec 100 154 KBytes [ 5] 5.00-6.00 sec 25.0 MBytes 210 Mbits/sec 0 250 KBytes [ 5] 6.00-7.00 sec 19.8 MBytes 166 Mbits/sec 214 184 KBytes [ 5] 7.00-8.00 sec 26.5 MBytes 222 Mbits/sec 150 93.3 KBytes [ 5] 8.00-9.00 sec 23.1 MBytes 194 Mbits/sec 0 209 KBytes [ 5] 9.00-10.00 sec 24.1 MBytes 202 Mbits/sec 91 171 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 245 MBytes 206 Mbits/sec 877 sender [ 5] 0.00-10.00 sec 244 MBytes 205 Mbits/sec receiver iperf Done.
PC to PC through my box:
Wacke@HOME-Server:~> iperf3 -c 192.168.1.80 Connecting to host 192.168.1.80, port 5201 [ 5] local 192.168.1.2 port 38344 connected to 192.168.1.80 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 111 MBytes 933 Mbits/sec 14 221 KBytes [ 5] 1.00-2.00 sec 110 MBytes 924 Mbits/sec 1 221 KBytes [ 5] 2.00-3.00 sec 111 MBytes 928 Mbits/sec 1 221 KBytes [ 5] 3.00-4.00 sec 111 MBytes 928 Mbits/sec 0 221 KBytes [ 5] 4.00-5.00 sec 110 MBytes 926 Mbits/sec 0 221 KBytes [ 5] 5.00-6.00 sec 111 MBytes 930 Mbits/sec 0 221 KBytes [ 5] 6.00-7.00 sec 110 MBytes 927 Mbits/sec 0 221 KBytes [ 5] 7.00-8.00 sec 111 MBytes 927 Mbits/sec 0 221 KBytes [ 5] 8.00-9.00 sec 110 MBytes 926 Mbits/sec 1 221 KBytes [ 5] 9.00-10.00 sec 110 MBytes 924 Mbits/sec 0 221 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 1.08 GBytes 927 Mbits/sec 17 sender [ 5] 0.00-10.00 sec 1.08 GBytes 927 Mbits/sec receiver iperf Done.
The test result seems that PC to my box get the low performance. But the switch was working properly.
|
Re: armada 370 (88f6710) mainline uboot support March 15, 2019 10:17AM |
Admin Registered: 14 years ago Posts: 19,910 |
wacke,
Good tests!
But I would test from PC direct to router, too, to make it complete.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Good tests!
But I would test from PC direct to router, too, to make it complete.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support March 16, 2019 06:03AM |
Registered: 10 years ago Posts: 166 |
Hi bodhi,
Test of PC direct to router (armada 385, turris omnia):
Test of PC direct to router (armada 385, turris omnia):
Wacke@HOME-Server:~> iperf3 -c 192.168.1.1 Connecting to host 192.168.1.1, port 5201 [ 5] local 192.168.1.2 port 45628 connected to 192.168.1.1 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 113 MBytes 946 Mbits/sec 0 474 KBytes [ 5] 1.00-2.00 sec 110 MBytes 924 Mbits/sec 21 386 KBytes [ 5] 2.00-3.00 sec 108 MBytes 904 Mbits/sec 27 345 KBytes [ 5] 3.00-4.00 sec 110 MBytes 924 Mbits/sec 0 385 KBytes [ 5] 4.00-5.00 sec 111 MBytes 933 Mbits/sec 0 403 KBytes [ 5] 5.00-6.00 sec 110 MBytes 927 Mbits/sec 0 416 KBytes [ 5] 6.00-7.00 sec 110 MBytes 920 Mbits/sec 0 428 KBytes [ 5] 7.00-8.00 sec 111 MBytes 927 Mbits/sec 0 430 KBytes [ 5] 8.00-9.00 sec 110 MBytes 923 Mbits/sec 0 437 KBytes [ 5] 9.00-10.00 sec 110 MBytes 927 Mbits/sec 0 440 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 1.08 GBytes 925 Mbits/sec 48 sender [ 5] 0.00-10.07 sec 1.08 GBytes 918 Mbits/sec receiver iperf Done.
|
Re: armada 370 (88f6710) mainline uboot support March 16, 2019 03:39PM |
Admin Registered: 14 years ago Posts: 19,910 |
wacke,
Did you try to turn off flow control (if it is on)?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/16/2019 03:49PM by bodhi.
Did you try to turn off flow control (if it is on)?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/16/2019 03:49PM by bodhi.
|
Re: armada 370 (88f6710) mainline uboot support March 16, 2019 06:34PM |
Admin Registered: 14 years ago Posts: 19,910 |
wacke,
Your box to router (armada 385,Turris Omnia) is 500 Mbits/sec.I think flow control might be the reason for this speed. So that would account for it.
I think your box DSA switch migh have slowed it down.
I would run this test to see the speed going from the router to this box.
Actually all tests should be bidirectional, especially when different Ethernet chip is on each side.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Your box to router (armada 385,Turris Omnia) is 500 Mbits/sec.I think flow control might be the reason for this speed. So that would account for it.
I think your box DSA switch migh have slowed it down.
I would run this test to see the speed going from the router to this box.
iperf3 -c 192.168.1.1 -r
Actually all tests should be bidirectional, especially when different Ethernet chip is on each side.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: armada 370 (88f6710) mainline uboot support March 17, 2019 07:29AM |
Registered: 10 years ago Posts: 166 |
Hi bodhi,
The iperf3 was not support bidirectional mode, so I just retested with bidirectional manually.
My box to my router:
And the flow control was enabled on my router,how to disable it?
My router to my box:
PC to my box
My box to PC
May be it's DSA driver problem?
The iperf3 was not support bidirectional mode, so I just retested with bidirectional manually.
My box to my router:
root@debian:~# iperf3 -c 192.168.1.1 Connecting to host 192.168.1.1, port 5201 [ 4] local 192.168.1.238 port 40430 connected to 192.168.1.1 port 5201 [ ID] Interval Transfer Bandwidth Retr Cwnd [ 4] 0.00-1.01 sec 43.8 MBytes 363 Mbits/sec 17 139 KBytes [ 4] 1.01-2.02 sec 52.5 MBytes 437 Mbits/sec 0 154 KBytes [ 4] 2.02-3.01 sec 52.2 MBytes 442 Mbits/sec 0 195 KBytes [ 4] 3.01-4.02 sec 55.0 MBytes 455 Mbits/sec 0 198 KBytes [ 4] 4.02-5.00 sec 50.0 MBytes 428 Mbits/sec 0 198 KBytes [ 4] 5.00-6.01 sec 55.0 MBytes 458 Mbits/sec 0 198 KBytes [ 4] 6.01-7.01 sec 52.7 MBytes 443 Mbits/sec 0 204 KBytes [ 4] 7.01-8.03 sec 53.8 MBytes 442 Mbits/sec 0 204 KBytes [ 4] 8.03-9.02 sec 51.2 MBytes 431 Mbits/sec 0 204 KBytes [ 4] 9.02-10.00 sec 52.5 MBytes 450 Mbits/sec 4 167 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 519 MBytes 435 Mbits/sec 21 sender [ 4] 0.00-10.00 sec 519 MBytes 435 Mbits/sec receiver iperf Done.
And the flow control was enabled on my router,how to disable it?
[622477.055712] mv88e6085 f1072004.mdio-mii:10 lan1: Link is Up - 1Gbps/Full - flow control rx/tx
My router to my box:
root@debian:~# iperf3 -s ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- Accepted connection from 192.168.1.1, port 60814 [ 5] local 192.168.1.238 port 5201 connected to 192.168.1.1 port 60816 [ ID] Interval Transfer Bandwidth [ 5] 0.00-1.01 sec 21.3 MBytes 177 Mbits/sec [ 5] 1.01-2.00 sec 22.8 MBytes 191 Mbits/sec [ 5] 2.00-3.00 sec 21.8 MBytes 182 Mbits/sec [ 5] 3.00-4.01 sec 23.8 MBytes 197 Mbits/sec [ 5] 4.01-5.00 sec 20.8 MBytes 176 Mbits/sec [ 5] 5.00-6.01 sec 24.9 MBytes 207 Mbits/sec [ 5] 6.01-7.01 sec 22.6 MBytes 190 Mbits/sec [ 5] 7.01-8.00 sec 23.1 MBytes 195 Mbits/sec [ 5] 8.00-9.01 sec 24.5 MBytes 205 Mbits/sec [ 5] 9.01-10.01 sec 22.1 MBytes 185 Mbits/sec [ 5] 10.01-10.03 sec 640 KBytes 231 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 5] 0.00-10.03 sec 0.00 Bytes 0.00 bits/sec sender [ 5] 0.00-10.03 sec 228 MBytes 191 Mbits/sec receiver
PC to my box
root@debian:~# iperf3 -s ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- Accepted connection from 192.168.1.2, port 52744 [ 5] local 192.168.1.238 port 5201 connected to 192.168.1.2 port 52746 [ ID] Interval Transfer Bandwidth [ 5] 0.00-1.00 sec 21.8 MBytes 182 Mbits/sec [ 5] 1.00-2.00 sec 24.2 MBytes 204 Mbits/sec [ 5] 2.00-3.01 sec 24.8 MBytes 207 Mbits/sec [ 5] 3.01-4.01 sec 20.9 MBytes 176 Mbits/sec [ 5] 4.01-5.01 sec 26.1 MBytes 217 Mbits/sec [ 5] 5.01-6.01 sec 21.5 MBytes 181 Mbits/sec [ 5] 6.01-7.01 sec 24.5 MBytes 205 Mbits/sec [ 5] 7.01-8.01 sec 23.9 MBytes 201 Mbits/sec [ 5] 8.01-9.01 sec 22.6 MBytes 190 Mbits/sec [ 5] 9.01-10.01 sec 25.9 MBytes 215 Mbits/sec [ 5] 10.01-10.03 sec 512 KBytes 279 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 5] 0.00-10.03 sec 0.00 Bytes 0.00 bits/sec sender [ 5] 0.00-10.03 sec 237 MBytes 198 Mbits/sec receiver iperf3: the client has unexpectedly closed the connection
My box to PC
root@debian:~# iperf3 -c 192.168.1.2 Connecting to host 192.168.1.2, port 5201 [ 4] local 192.168.1.238 port 33060 connected to 192.168.1.2 port 5201 [ ID] Interval Transfer Bandwidth Retr Cwnd [ 4] 0.00-1.02 sec 56.2 MBytes 463 Mbits/sec 0 199 KBytes [ 4] 1.02-2.01 sec 55.0 MBytes 467 Mbits/sec 0 199 KBytes [ 4] 2.01-3.02 sec 53.8 MBytes 443 Mbits/sec 0 199 KBytes [ 4] 3.02-4.01 sec 51.2 MBytes 437 Mbits/sec 0 199 KBytes [ 4] 4.01-5.00 sec 56.2 MBytes 473 Mbits/sec 0 209 KBytes [ 4] 5.00-6.02 sec 57.5 MBytes 476 Mbits/sec 0 209 KBytes [ 4] 6.02-7.01 sec 52.5 MBytes 444 Mbits/sec 0 209 KBytes [ 4] 7.01-8.02 sec 55.0 MBytes 457 Mbits/sec 0 209 KBytes [ 4] 8.02-9.01 sec 51.2 MBytes 435 Mbits/sec 0 209 KBytes [ 4] 9.01-10.00 sec 51.2 MBytes 431 Mbits/sec 0 209 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 540 MBytes 453 Mbits/sec 0 sender [ 4] 0.00-10.00 sec 540 MBytes 453 Mbits/sec receiver iperf Done.
May be it's DSA driver problem?
|
Re: armada 370 (88f6710) mainline uboot support March 17, 2019 03:46PM |
Admin Registered: 14 years ago Posts: 19,910 |
wacke,
Yes, I think perhaps the DSA switch.
Here is the tests I did yesterday, using a cheap Gbits switch to connect these 3 boxes (that I think I need to retest at my better switch). And flow control must have slowed it down.
NAS326 (Armada 380, flow control enabled) — Mirabox (Armada 370, flow control enabled)
Dockstar (Kirkwood 6281, flow control disabled) — Mirabox (Armada 370, flow control enabled)
The following test is done using good quality switch.
NSA325 (Kirkwood 6282, flow control disabled) -- GoFlex Net (Kirkwood 8281, flow control disabled)
Based on the MIrabox test, I think your network chip/driver is causing the slow down, not HW IO Cohenrency.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/17/2019 03:50PM by bodhi.
Yes, I think perhaps the DSA switch.
Here is the tests I did yesterday, using a cheap Gbits switch to connect these 3 boxes (that I think I need to retest at my better switch). And flow control must have slowed it down.
NAS326 (Armada 380, flow control enabled) — Mirabox (Armada 370, flow control enabled)
root@Nas326:~# iperf -s -i 3 ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 128 KByte (default) ------------------------------------------------------------ [ 4] local 192.168.0.236 port 5001 connected with 192.168.0.252 port 44960 [ ID] Interval Transfer Bandwidth [ 4] 0.0- 3.0 sec 189 MBytes 527 Mbits/sec [ 4] 3.0- 6.0 sec 191 MBytes 533 Mbits/sec [ 4] 6.0- 9.0 sec 189 MBytes 529 Mbits/sec [ 4] 0.0-10.0 sec 632 MBytes 530 Mbits/sec ------------------------------------------------------------ Client connecting to 192.168.0.252, TCP port 5001 TCP window size: 105 KByte (default) ------------------------------------------------------------ [ 4] local 192.168.0.236 port 43606 connected with 192.168.0.252 port 5001 [ 4] 0.0- 3.0 sec 171 MBytes 478 Mbits/sec [ 4] 3.0- 6.0 sec 171 MBytes 478 Mbits/sec [ 4] 6.0- 9.0 sec 168 MBytes 471 Mbits/sec [ 4] 0.0-10.0 sec 566 MBytes 474 Mbits/sec
Dockstar (Kirkwood 6281, flow control disabled) — Mirabox (Armada 370, flow control enabled)
root@Mirabox:~# iperf -s -i 3 ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 128 KByte (default) ------------------------------------------------------------ [ 4] local 192.168.0.252 port 5001 connected with 192.168.0.220 port 57566 [ ID] Interval Transfer Bandwidth [ 4] 0.0- 3.0 sec 168 MBytes 470 Mbits/sec [ 4] 3.0- 6.0 sec 171 MBytes 479 Mbits/sec [ 4] 6.0- 9.0 sec 172 MBytes 482 Mbits/sec [ 4] 0.0-10.0 sec 570 MBytes 477 Mbits/sec ------------------------------------------------------------ Client connecting to 192.168.0.220, TCP port 5001 TCP window size: 127 KByte (default) ------------------------------------------------------------ [ 4] local 192.168.0.252 port 33800 connected with 192.168.0.220 port 5001 [ 4] 0.0- 3.0 sec 211 MBytes 590 Mbits/sec [ 4] 3.0- 6.0 sec 212 MBytes 591 Mbits/sec [ 4] 6.0- 9.0 sec 211 MBytes 591 Mbits/sec [ 4] 0.0-10.0 sec 704 MBytes 591 Mbits/sec
The following test is done using good quality switch.
NSA325 (Kirkwood 6282, flow control disabled) -- GoFlex Net (Kirkwood 8281, flow control disabled)
iperf -n2000M -i 3 -c Homembp.local ------------------------------------------------------------ Client connecting to Homembp.local, TCP port 5001 TCP window size: 43.8 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.0.224 port 49350 connected with 192.168.0.234 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0- 3.0 sec 286 MBytes 800 Mbits/sec [ 3] 3.0- 6.0 sec 287 MBytes 803 Mbits/sec [ 3] 6.0- 9.0 sec 287 MBytes 803 Mbits/sec [ 3] 9.0-12.0 sec 286 MBytes 800 Mbits/sec [ 3] 12.0-15.0 sec 286 MBytes 800 Mbits/sec [ 3] 15.0-18.0 sec 286 MBytes 799 Mbits/sec
Based on the MIrabox test, I think your network chip/driver is causing the slow down, not HW IO Cohenrency.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/17/2019 03:50PM by bodhi.
|
Re: armada 370 (88f6710) mainline uboot support March 17, 2019 08:14PM |
Registered: 10 years ago Posts: 166 |
Hi bodhi,
So need rewrite the DTS? My box used the 88e6171r switch, and tested that base address <0x10> doesn't work.
So need rewrite the DTS? My box used the 88e6171r switch, and tested that base address <0x10> doesn't work.
/*
* Device Tree file for Marvell Armada 370 Reference Design board
* (RD-88F6710-A1)
*
* Copied from arch/arm/boot/dts/armada-370-db.dts
*
* Copyright (C) 2013 Florian Fainelli <florian@openwrt.org>
*
* This file is dual-licensed: you can use it either under the terms
* of the GPL or the X11 license, at your option. Note that this dual
* licensing only applies to this file, and not this project as a
* whole.
*
* a) This file is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License as
* published by the Free Software Foundation; either version 2 of the
* License, or (at your option) any later version.
*
* This file is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* Or, alternatively,
*
* b) Permission is hereby granted, free of charge, to any person
* obtaining a copy of this software and associated documentation
* files (the "Software"), to deal in the Software without
* restriction, including without limitation the rights to use,
* copy, modify, merge, publish, distribute, sublicense, and/or
* sell copies of the Software, and to permit persons to whom the
* Software is furnished to do so, subject to the following
* conditions:
*
* The above copyright notice and this permission notice shall be
* included in all copies or substantial portions of the Software.
*
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
* EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
* OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
* NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
* HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
* WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
* FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
* OTHER DEALINGS IN THE SOFTWARE.
*
* Note: this Device Tree assumes that the bootloader has remapped the
* internal registers to 0xf1000000 (instead of the default
* 0xd0000000). The 0xf1000000 is the default used by the recent,
* DT-capable, U-Boot bootloaders provided by Marvell. Some earlier
* boards were delivered with an older version of the bootloader that
* left internal registers mapped at 0xd0000000. If you are in this
* situation, you should either update your bootloader (preferred
* solution) or the below Device Tree should be adjusted.
*/
/dts-v1/;
#include <dt-bindings/input/input.h>
#include <dt-bindings/gpio/gpio.h>
#include "armada-370.dtsi"
/ {
model = "RTNAS V3";
compatible = "marvell,armada-370-rtnasv3","marvell,a370-rd", "marvell,armada370", "marvell,armada-370-xp";
chosen {
stdout-path = "serial0:115200n8";
};
memory@0 {
device_type = "memory";
reg = <0x00000000 0x40000000>; /* 1024 MB */
};
soc {
ranges = <MBUS_ID(0xf0, 0x01) 0 0xf1000000 0x100000
MBUS_ID(0x01, 0xe0) 0 0xfff00000 0x100000
MBUS_ID(0x09, 0x01) 0 0xf1100000 0x10000>;
internal-regs {
serial@12000 {
status = "okay";
};
sata@a0000 {
nr-ports = <2>;
status = "okay";
};
ethernet@70000 {
status = "disabled";
phy = <&phy0>;
phy-mode = "sgmii";
};
ethernet@74000 {
pinctrl-0 = <&ge1_rgmii_pins>;
pinctrl-names = "default";
status = "okay";
phy-mode = "rgmii-id";
fixed-link {
speed = <1000>;
full-duplex;
};
};
mvsdio@d4000 {
pinctrl-0 = <&sdio_pins1>;
pinctrl-names = "default";
status = "disabled";
/* No CD or WP GPIOs */
broken-cd;
};
usb@50000 {
status = "okay";
};
usb@51000 {
status = "okay";
};
nand@d0000 {
status = "okay";
num-cs = <2>;
marvell,nand-keep-config;
marvell,nand-enable-arbiter;
nand-on-flash-bbt;
nand-ecc-strength = <0x4>;
nand-ecc-step-size = <0x200>;
partition@0 {
label = "u-boot";
reg = <0x0 0x400000>;
};
partition@400000 {
label = "uboot_env";
reg = <0x400000 0x400000>;
};
partition@800000 {
label = "vendor";
reg = <0x800000 0x400000>;
};
partition@c00000 {
label = "unused";
reg = <0xc00000 0xc00000>;
};
partition@1800000 {
label = "kernel";
reg = <0x1800000 0x400000>;
};
partition@1c00000 {
label = "ubi";
reg = <0x1c00000 0x3e400000>;
};
partition@40000000 {
label = "syscfg";
reg = <0x40000000 0xbbc00000>;
};
};
};
};
gpio-keys {
compatible = "gpio-keys";
pinctrl-0 = <&reset_button_pin &pwr_button_pin>;
pinctrl-names = "default";
reset_button {
label = "Reset Button";
linux,code = <KEY_RESTART>;
gpios = <&gpio1 30 GPIO_ACTIVE_LOW>;
};
wps_button {
label = "Software Button";
linux,code = <KEY_POWER>;
gpios = <&gpio1 20 GPIO_ACTIVE_LOW>;
};
};
gpio-leds {
compatible = "gpio-leds";
pinctrl-names = "default";
pinctrl-0 = <&pwr_led_pin &wps_led_pins>;
blue_pwr_led {
label = "rtnasv3:blue:pwr";
gpios = <&gpio0 6 GPIO_ACTIVE_HIGH>;
default-state = "keep";
};
blue_wps_led {
label = "rtnasv3:blue:wps";
gpios = <&gpio1 18 GPIO_ACTIVE_HIGH>;
default-state = "off";
};
};
dsa {
status = "disabled";
compatible = "marvell,dsa";
#address-cells = <2>;
#size-cells = <0>;
dsa,ethernet = <ð1>;
dsa,mii-bus = <&mdio>;
switch@0 {
#address-cells = <1>;
#size-cells = <0>;
reg = <0x10 0>; /* MDIO address 16, switch 0 in tree */
port@0 {
reg = <0>;
label = "lan0";
};
port@1 {
reg = <1>;
label = "lan1";
};
port@2 {
reg = <2>;
label = "lan2";
};
port@3 {
reg = <3>;
label = "lan3";
};
port@4 {
reg = <4>;
label = "wan";
};
port@5 {
reg = <5>;
label = "cpu";
};
};
};
};
&mdio {
pinctrl-0 = <&mdio_pins>;
pinctrl-names = "default";
switch0@0 {
compatible = "marvell,mv88e6085";
#address-cells = <1>;
#size-cells = <0>;
reg = <0x0>;
ports {
#address-cells = <1>;
#size-cells = <0>;
port@0 {
reg = <0>;
label = "lan0";
};
port@1 {
reg = <1>;
label = "lan1";
};
port@2 {
reg = <2>;
label = "lan2";
};
port@3 {
reg = <3>;
label = "lan3";
};
port@4 {
reg = <4>;
label = "wan";
};
port@5 {
reg = <5>;
label = "cpu";
ethernet = <ð1>;
fixed-link {
speed = <1000>;
full-duplex;
};
};
};
};
};
&pciec {
status = "okay";
/* Internal mini-PCIe connector */
pcie@1,0 {
/* Port 0, Lane 0 */
status = "okay";
};
/* Internal mini-PCIe connector */
pcie@2,0 {
/* Port 1, Lane 0 */
status = "okay";
};
};
&pinctrl {
compatible = "marvell,mv88f6710-pinctrl";
pwr_button_pin: pwr-button-pin {
marvell,pins = "mpp52";
marvell,function = "gpio";
};
reset_button_pin: reset-button-pin {
marvell,pins = "mpp62";
marvell,function = "gpio";
};
pwr_led_pin: pwr-led-pin {
marvell,pins = "mpp6";
marvell,function = "gpio";
};
wps_led_pins: wps-led-pins {
marvell,pins = "mpp50";
marvell,function = "gpio";
};
};
|
Re: armada 370 (88f6710) mainline uboot support March 18, 2019 12:08AM |
Admin Registered: 14 years ago Posts: 19,910 |
wacke,
I didn't see any thing strange in your DTS.
This compatible field is OK. This is actually the switch familly mv88e6085.
But, why is the DSA status disabled? I know the EA4500 DTS also has this status set to disabled. Perhaps the mdio "switch" node seems to be all we need to activate it.
I will see if I can find the REF manual for this 6171R switch.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
I didn't see any thing strange in your DTS.
This compatible field is OK. This is actually the switch familly mv88e6085.
compatible = "marvell,mv88e6085";
But, why is the DSA status disabled? I know the EA4500 DTS also has this status set to disabled. Perhaps the mdio "switch" node seems to be all we need to activate it.
dsa {
status = "disabled";
Have you tried to set it to OK to see if anything changes:
status = "okay";
I will see if I can find the REF manual for this 6171R switch.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
