From: Ganji Aravind <ganji.aravind@chelsio.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, vishal@chelsio.com,
rahul.lakkireddy@chelsio.com
Subject: Re: [PATCH net-next] cxgb4: Add support to flash firmware config image
Date: Fri, 31 Jul 2020 16:39:04 +0530 [thread overview]
Message-ID: <20200731110904.GA1571@chelsio.com> (raw)
In-Reply-To: <20200730162335.6a6aa4cf@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
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.
Thanks
-Ganji Aravind.
next prev parent reply other threads:[~2020-07-31 11:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 15:11 [PATCH net-next] cxgb4: Add support to flash firmware config image Ganji Aravind
2020-07-30 23:23 ` Jakub Kicinski
2020-07-31 11:09 ` Ganji Aravind [this message]
2020-07-31 18:00 ` Jakub Kicinski
2020-07-31 21:17 ` Rahul Lakkireddy
2020-08-02 4:22 ` Jakub Kicinski
2020-08-02 17:12 ` Rahul Lakkireddy
2020-08-03 21:13 ` Jakub Kicinski
2020-08-04 9:43 ` Rahul Lakkireddy
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=20200731110904.GA1571@chelsio.com \
--to=ganji.aravind@chelsio.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rahul.lakkireddy@chelsio.com \
--cc=vishal@chelsio.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.