netdev - Re: [PATCH net-next] cxgb4: Add support to flash firmware config image

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200731110008.598a8ea7@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date:   Fri, 31 Jul 2020 11:00:08 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Ganji Aravind <ganji.aravind@...lsio.com>
Cc:     netdev@...r.kernel.org, davem@...emloft.net, vishal@...lsio.com,
        rahul.lakkireddy@...lsio.com
Subject: Re: [PATCH net-next] cxgb4: Add support to flash firmware config
 image

On Fri, 31 Jul 2020 16:39:04 +0530 Ganji Aravind wrote:
> On Thursday, July 07/30/20, 2020 at 16:23:35 -0700, Jakub Kicinski wrote:
> > On Thu, 30 Jul 2020 20:41:38 +0530 Ganji Aravind wrote:  
> > > Update set_flash to flash firmware configuration image
> > > to flash region.  
> > 
> > And the reason why you need to flash some .ini files separately is?  
> 
> Hi Jakub,
> 
> The firmware config file contains information on how the firmware
> should distribute the hardware resources among NIC and
> Upper Layer Drivers(ULD), like iWARP, crypto, filtering, etc.
> 
> The firmware image comes with an in-built default config file that
> distributes resources among the NIC and all the ULDs. However, in
> some cases, where we don't want to run a particular ULD, or if we
> want to redistribute the resources, then we'd modify the firmware
> config file and then firmware will redistribute those resources
> according to the new configuration. So, if firmware finds this
> custom config file in flash, it reads this first. Otherwise, it'll
> continue initializing the adapter with its own in-built default
> config file.

Sounds like something devlink could be extended to do.

Firmware update interface is not for configuration.