>From: Jakub Kicinski <kuba@xxxxxxxxxx> >Sent: Thursday, April 13, 2023 5:04 PM > >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. Well, this makes sense. Although I double checked, and it seems I wasn't clear on previous explanation. Once FW update is possible with Intel's nvmupdate tools, the devlink FW update also going to update CGU firmware (part of nvm-flash region), so after all this seems a right place for this info. Thanks, Arkadiusz
