From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 395A7C77B61 for ; Thu, 13 Apr 2023 15:04:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230403AbjDMPEJ (ORCPT ); Thu, 13 Apr 2023 11:04:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55562 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229660AbjDMPEJ (ORCPT ); Thu, 13 Apr 2023 11:04:09 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5631783E2; Thu, 13 Apr 2023 08:04:08 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id E73A263BBE; Thu, 13 Apr 2023 15:04:07 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id CC5A7C433EF; Thu, 13 Apr 2023 15:04:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1681398247; bh=JdbgbeQTK4oXXpvwy/OkbrBX79V7CMl8I2rByssnbK8=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=YPGDH/bbVb36/Vi0t11lP6f2sRR4SOLUf7fIxJRUtI28miO5mrqAWIL/3j1+kYij5 Znu5MBMUAZ+ABRUL93fKTMB8SrOPqtCDWAWceK9xh6JuqFmfUN0jdOLKeXXtxaZjlk Mji3Ymgy4JBemOYnGu9wR+RTKyZ/BPk926GVY3BLbrJozJPXSyT4kwpnvRSM1BGqMQ lDdzkfb6wkR/K9+ZE7ddssGuJ4sacrzsSzrfTlCIV7dOuOB08yFa6iiLh6ZIpQyFy4 pQXosljbJNj3i7pKtYMvmQu2Iu5JzdM+4DG/oqhlS/RRYM3agdlvngB1MvkVuACpU7 GLBtV7XMPP1Sw== Date: Thu, 13 Apr 2023 08:04:05 -0700 From: Jakub Kicinski To: "Kubalewski, Arkadiusz" Cc: "jiri@resnulli.us" , "davem@davemloft.net" , "edumazet@google.com" , "pabeni@redhat.com" , "corbet@lwn.net" , "Brandeburg, Jesse" , "Nguyen, Anthony L" , "richardcochran@gmail.com" , "netdev@vger.kernel.org" , "linux-doc@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "intel-wired-lan@lists.osuosl.org" Subject: Re: [RFC PATCH v1] ice: add CGU info to devlink info callback Message-ID: <20230413080405.30bbe3bd@kernel.org> In-Reply-To: References: <20230412133811.2518336-1-arkadiusz.kubalewski@intel.com> <20230412203500.36fb7c36@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org 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.