From: Jiri Pirko <jiri@resnulli.us>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: Ido Schimmel <idosch@mellanox.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
Jiri Pirko <jiri@mellanox.com>,
Shalom Toledo <shalomt@mellanox.com>, mlxsw <mlxsw@mellanox.com>
Subject: Re: [PATCH net-next 2/2] mlxsw: core: Add support for devlink info command
Date: Wed, 27 Mar 2019 12:08:15 +0100 [thread overview]
Message-ID: <20190327110815.GH6979@nanopsycho> (raw)
In-Reply-To: <20190326134807.39378e14@cakuba.netronome.com>
Tue, Mar 26, 2019 at 09:48:07PM CET, jakub.kicinski@netronome.com wrote:
>On Tue, 26 Mar 2019 13:46:26 +0000, Ido Schimmel wrote:
>> From: Shalom Toledo <shalomt@mellanox.com>
>>
>> Expose the following ASIC information via devlink info command:
>> - Hardware revision
>> - Firmware PSID
>> - Running firmware version
>>
>> Standard output example:
>> $ devlink dev info pci/0000:03:00.0
>> pci/0000:03:00.0:
>> versions:
>> fixed:
>> hw.revision A0
>> fw.psid MT_2750110033
>> running:
>> fw.version 13.1910.622
>>
>> Pretty JSON example:
>> $ devlink -jp dev info pci/0000:03:00.0
>> {
>> "info": {
>> "pci/0000:03:00.0": {
>> "versions": {
>> "fixed": {
>> "hw.revision": "A0",
>> "fw.psid": "MT_2750110033"
>> },
>> "running": {
>> "fw.version": "13.1910.622"
>> }
>> }
>> }
>> }
>> }
>>
>> Signed-off-by: Shalom Toledo <shalomt@mellanox.com>
>> Acked-by: Jiri Pirko <jiri@mellanox.com>
>> Signed-off-by: Ido Schimmel <idosch@mellanox.com>
>
>Looks good & glad to see it, but what's a PSID? ;)
>
>I found this after 5 seconds of googling:
>
>http://www.mellanox.com/page/firmware_HCA_FW_identification
>
>But it still just say "PSID" without explaining what the acronym stands
>for :)
It's Mellanox board/setup identification.
next prev parent reply other threads:[~2019-03-27 11:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 13:46 [PATCH net-next 0/2] mlxsw: Add support for devlink info command Ido Schimmel
2019-03-26 13:46 ` [PATCH net-next 1/2] mlxsw: reg: Add MGIR register Ido Schimmel
2019-03-26 13:46 ` [PATCH net-next 2/2] mlxsw: core: Add support for devlink info command Ido Schimmel
2019-03-26 20:48 ` Jakub Kicinski
2019-03-27 9:47 ` Petr Machata
2019-03-27 17:53 ` Jakub Kicinski
2019-03-27 19:44 ` Ido Schimmel
2019-03-27 20:36 ` Jakub Kicinski
2019-03-27 11:08 ` Jiri Pirko [this message]
2019-03-27 20:58 ` [PATCH net-next 0/2] mlxsw: " David Miller
2019-03-27 21:31 ` Ido Schimmel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190327110815.GH6979@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=idosch@mellanox.com \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@mellanox.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=shalomt@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.