[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<DM6PR11MB42363E9DC481B09277369B5A83632@DM6PR11MB4236.namprd11.prod.outlook.com>
Date: Thu, 19 Sep 2024 10:44:11 +0000
From: <Mohan.Prasad@...rochip.com>
To: <andrew@...n.ch>
CC: <netdev@...r.kernel.org>, <davem@...emloft.net>, <kuba@...nel.org>,
<edumazet@...gle.com>, <pabeni@...hat.com>, <shuah@...nel.org>,
<linux-kernel@...r.kernel.org>, <linux-kselftest@...r.kernel.org>,
<horms@...nel.org>, <brett.creeley@....com>, <rosenp@...il.com>,
<UNGLinuxDriver@...rochip.com>, <willemb@...gle.com>
Subject: RE: [PATCH net-next v2 1/3] selftests: nic_basic_tests: Add selftest
file for basic tests of NIC
Hello Andrew,
Thank you for the suggestion.
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
> > > Since you have batteries included python:
> > >
> > > ethtool --json enp2s0
> > > [sudo] password for andrew:
> > > [ {
> > > "ifname": "enp2s0",
> > > "supported-ports": [ "TP","MII" ],
> > > "supported-link-modes": [
> > > "10baseT/Half","10baseT/Full","100baseT/Half","100baseT/Full","1000b
> > > aseT/
> > > Full" ],
> > > "supported-pause-frame-use": "Symmetric Receive-only",
> > > "supports-auto-negotiation": true,
> > > "supported-fec-modes": [ ],
> > > "advertised-link-modes": [
> > > "10baseT/Half","10baseT/Full","100baseT/Half","100baseT/Full","1000b
> > > aseT/
> > > Full" ],
> > > "advertised-pause-frame-use": "Symmetric Receive-only",
> > > "advertised-auto-negotiation": true,
> > > "advertised-fec-modes": [ ],
> > > "auto-negotiation": false,
> > > "master-slave-cfg": "preferred slave",
> > > "master-slave-status": "unknown",
> > > "port": "Twisted Pair",
> > > "phyad": 0,
> > > "transceiver": "external",
> > > "supports-wake-on": "pumbg",
> > > "wake-on": "d",
> > > "link-detected": false
> > > } ]
> > >
> > > You can use a json library to do all the parsing for you.
> >
> > I tried running the --json option with the ethtool ("ethtool --json enp9s0"),
> however I am not getting the above output.
> > Instead it always throws "ethtool: bad command line argument(s)"
> > I am figuring out what might be missing (or any suggestions would be
> helpful).
>
> Are you using real ethtool, or busybox? What version of ethtool? I'm using
> 6.10, but it looks like JSON support was added somewhere around 5.10.
I have been using ethtool 6.7, updating to ethtool 6.10 solved the problem.
Powered by blists - more mailing lists