diff options
| author | Maciej Kisielewski <maciej.kisielewski@canonical.com> | 2017-01-18 11:00:37 +0100 |
|---|---|---|
| committer | Maciej Kisielewski <maciej.kisielewski@canonical.com> | 2017-01-18 11:00:37 +0100 |
| commit | d3d14a2e7a8c4d2c849b2673b2498eab1f26aff4 (patch) | |
| tree | 9254d01c97c216862ecf0a21e711a491017d3fdc /bin/mm-test | |
| parent | a3e460b7a10f6af6b91b090c1e4a4709c035625b (diff) | |
network: use mii-tool instead of ethtool to determine max speed
On some systems, ethtool returns such output: >>> Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full <<< previous version of the `network` script parsed for any number followed by the 'baseT' string and picked the largest one found as max_speed. Which for this system is wrong. This patch makes the script parse output of mii-tool and look for 'capabilities' line. It parses modes only from that line. In case of that system it returns 100. Signed-off-by: Maciej Kisielewski <maciej.kisielewski@canonical.com>
Diffstat (limited to 'bin/mm-test')
0 files changed, 0 insertions, 0 deletions
