From: David Miller <davem@davemloft.net>
To: jakub.kicinski@netronome.com
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com
Subject: Re: [PATCH net-next 0/3] nfp: extend firmware request logic
Date: Thu, 27 Jul 2017 17:26:43 -0700 (PDT) [thread overview]
Message-ID: <20170727.172643.2063365377965177727.davem@davemloft.net> (raw)
In-Reply-To: <20170726180948.3220-1-jakub.kicinski@netronome.com>
From: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Wed, 26 Jul 2017 11:09:45 -0700
> We have been pondering for some time how to support loading different
> application firmwares onto NFP. We want to support both users selecting
> one of the firmware images provided by Netronome (which are optimized
> for different use cases each) as well as firmware images created by
> users themselves or other companies.
>
> In the end we decided to go with the simplest solution - depending on
> the right firmware image being placed in /lib/firmware. This vastly
> simplifies driver logic and also doesn't require any new API.
>
> Different NICs on one system may want to run different applications
> therefore we first try to load firmware specific to the device (by
> serial number of PCI slot) and if not present try the device model
> based name we have been using so far.
Series applied, thanks Jakub.
prev parent reply other threads:[~2017-07-28 0:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 18:09 [PATCH net-next 0/3] nfp: extend firmware request logic Jakub Kicinski
2017-07-26 18:09 ` [PATCH net-next 1/3] nfp: remove the probe deferral when FW not present Jakub Kicinski
2017-07-26 18:09 ` [PATCH net-next 2/3] nfp: look for firmware image by device serial number and PCI name Jakub Kicinski
2017-07-27 8:20 ` David Laight
2017-07-27 9:25 ` Jakub Kicinski
2017-07-27 10:15 ` David Laight
2017-07-26 18:09 ` [PATCH net-next 3/3] nfp: only use direct firmware requests Jakub Kicinski
2017-07-27 8:09 ` [oss-drivers] [PATCH net-next 0/3] nfp: extend firmware request logic Simon Horman
2017-07-28 0:26 ` David Miller [this message]
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=20170727.172643.2063365377965177727.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).