From: Jakub Kicinski <kuba@kernel.org>
To: "Kubalewski, Arkadiusz" <arkadiusz.kubalewski@intel.com>
Cc: "jiri@resnulli.us" <jiri@resnulli.us>,
"corbet@lwn.net" <corbet@lwn.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"richardcochran@gmail.com" <richardcochran@gmail.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"edumazet@google.com" <edumazet@google.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [Intel-wired-lan] [RFC PATCH v1] ice: add CGU info to devlink info callback
Date: Thu, 13 Apr 2023 08:04:05 -0700 [thread overview]
Message-ID: <20230413080405.30bbe3bd@kernel.org> (raw)
In-Reply-To: <DM6PR11MB46577E14FE17ADA6D1E74E789B989@DM6PR11MB4657.namprd11.prod.outlook.com>
On Thu, 13 Apr 2023 13:43:52 +0000 Kubalewski, Arkadiusz wrote:
> >Is it flashed together with the rest of the FW components of the NIC?
> >Or the update method is different?
>
> Right now there is no mechanics for CGU firmware update at all, this is why I
> mention that this is for now mostly for debugging purposes.
> There are already some works ongoing to have CGU FW update possible, first with
> Intel's nvmupdate packages and tools. But, for Linux we probably also gonna
> need to support update through devlink, at least this seems right thing to do,
> as there is already possibility to update NIC firmware with devlink.
Only FW versions which are updated with a single flashing operation /
are part of a single FW image should be reported under the device
instance. If the flash is separate you need to create a separate
devlink (sub)instance or something along those lines.
Differently put - the components in the API are components of the FW
image, not components of a board.
We had a similar discussion about "line cards" before.
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: "Kubalewski, Arkadiusz" <arkadiusz.kubalewski@intel.com>
Cc: "jiri@resnulli.us" <jiri@resnulli.us>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"richardcochran@gmail.com" <richardcochran@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Subject: Re: [RFC PATCH v1] ice: add CGU info to devlink info callback
Date: Thu, 13 Apr 2023 08:04:05 -0700 [thread overview]
Message-ID: <20230413080405.30bbe3bd@kernel.org> (raw)
In-Reply-To: <DM6PR11MB46577E14FE17ADA6D1E74E789B989@DM6PR11MB4657.namprd11.prod.outlook.com>
On Thu, 13 Apr 2023 13:43:52 +0000 Kubalewski, Arkadiusz wrote:
> >Is it flashed together with the rest of the FW components of the NIC?
> >Or the update method is different?
>
> Right now there is no mechanics for CGU firmware update at all, this is why I
> mention that this is for now mostly for debugging purposes.
> There are already some works ongoing to have CGU FW update possible, first with
> Intel's nvmupdate packages and tools. But, for Linux we probably also gonna
> need to support update through devlink, at least this seems right thing to do,
> as there is already possibility to update NIC firmware with devlink.
Only FW versions which are updated with a single flashing operation /
are part of a single FW image should be reported under the device
instance. If the flash is separate you need to create a separate
devlink (sub)instance or something along those lines.
Differently put - the components in the API are components of the FW
image, not components of a board.
We had a similar discussion about "line cards" before.
next prev parent reply other threads:[~2023-04-13 15:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 13:38 [Intel-wired-lan] [RFC PATCH v1] ice: add CGU info to devlink info callback Arkadiusz Kubalewski
2023-04-12 13:38 ` Arkadiusz Kubalewski
2023-04-12 21:33 ` [Intel-wired-lan] " Jacob Keller
2023-04-13 13:36 ` Kubalewski, Arkadiusz
2023-04-13 16:42 ` Jacob Keller
2023-04-14 12:34 ` Kubalewski, Arkadiusz
2023-04-13 3:35 ` Jakub Kicinski
2023-04-13 3:35 ` Jakub Kicinski
2023-04-13 13:43 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-04-13 13:43 ` Kubalewski, Arkadiusz
2023-04-13 15:04 ` Jakub Kicinski [this message]
2023-04-13 15:04 ` Jakub Kicinski
2023-04-14 10:04 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-04-14 10:04 ` Kubalewski, Arkadiusz
2023-04-14 14:46 ` [Intel-wired-lan] " Jakub Kicinski
2023-04-14 14:46 ` Jakub Kicinski
2023-04-13 13:17 ` [Intel-wired-lan] " Leon Romanovsky
2023-04-13 13:17 ` Leon Romanovsky
2023-04-13 14:04 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-04-13 14:04 ` Kubalewski, Arkadiusz
2023-04-13 17:17 ` [Intel-wired-lan] " Leon Romanovsky
2023-04-13 17:17 ` Leon Romanovsky
2023-04-14 10:06 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-04-14 10:06 ` Kubalewski, Arkadiusz
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=20230413080405.30bbe3bd@kernel.org \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.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.