From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from netronome.com (host-79-78-33-110.static.as9105.net [79.78.33.110]) by dpdk.org (Postfix) with ESMTP id B78A17CDA for ; Fri, 23 Mar 2018 18:35:36 +0100 (CET) Received: from netronome.com (localhost [127.0.0.1]) by netronome.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id w2NHZ532020250 for ; Fri, 23 Mar 2018 17:35:05 GMT Received: (from alucero@localhost) by netronome.com (8.14.4/8.14.4/Submit) id w2NHZ5Gu020249 for dev@dpdk.org; Fri, 23 Mar 2018 17:35:05 GMT From: Alejandro Lucero To: dev@dpdk.org Date: Fri, 23 Mar 2018 17:35:03 +0000 Message-Id: <1521826504-20195-4-git-send-email-alejandro.lucero@netronome.com> X-Mailer: git-send-email 1.9.1 In-Reply-To: <1521826504-20195-1-git-send-email-alejandro.lucero@netronome.com> References: <1521826504-20195-1-git-send-email-alejandro.lucero@netronome.com> Subject: [dpdk-dev] [PATCH 3/4] doc: update NFP guide X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2018 17:35:37 -0000 New CPP interface changes the way firmware upload is managed by the PMD. It also supports different firmware file names for having specific firmware aplications per card. Signed-off-by: Alejandro Lucero --- doc/guides/nics/nfp.rst | 31 ++++++++++++++++++++++++------- 1 file changed, 24 insertions(+), 7 deletions(-) diff --git a/doc/guides/nics/nfp.rst b/doc/guides/nics/nfp.rst index 99a3b76..6b1f9fc 100644 --- a/doc/guides/nics/nfp.rst +++ b/doc/guides/nics/nfp.rst @@ -99,16 +99,33 @@ have a PMD able to work with the PF and VFs at the same time and with the PF implementing VF management along with other PF-only functionalities/offloads. The PMD PF has extra work to do which will delay the DPDK app initialization -like checking if a firmware is already available in the device, uploading the -firmware if necessary, and configure the Link state properly when starting or -stopping a PF port. Note that firmware upload is not always necessary which is -the main delay for NFP PF PMD initialization. +like uploading the firmware and configure the Link state properly when starting or +stopping a PF port. Since DPDK 18.05 the firmware upload is always happening when +a PF is initialized, which was not always true with older DPDK versions. Depending on the Netronome product installed in the system, firmware files should be available under ``/lib/firmware/netronome``. DPDK PMD supporting the -PF requires a specific link, ``/lib/firmware/netronome/nic_dpdk_default.nffw``, -which should be created automatically with Netronome's Agilio products -installation. +PF looks for a firmware file in this order: + + 1) First try to find a firmware image specific for this device using the + NFP serial number: + + serial-00-15-4d-12-20-65-10-ff.nffw + + 2) Then try the PCI name: + + pci-0000:04:00.0.nffw + + 3) Finally try the card type and media: + + nic_AMDA0099-0001_2x25.nffw + +Netronome's software packages install firmware files under ``/lib/firmware/netronome`` +for supporting all the Netronome's SmartNICs and also different firmware applications. +This is usually done using file names based on SmartNIC type and media and with a +directory per firmware application. Options 1 and 2 for firmware filenames allow to +have more than one SmartNIC, same type of SmartNIC or different ones, and to upload a +different firmware to each SmartNIC. PF multiport support -------------------- -- 1.9.1