X-Git-Url: http://git.droids-corp.org/?a=blobdiff_plain;f=doc%2Fguides%2Fplatform%2Fdpaa.rst;h=20a0e39329f3303e9ca04534c0611924a7f8603a;hb=c0d002aed98d6d1d38d6bb318a5bd2ed5cdc01b1;hp=39048715226189be5baf00e64c047843e1edd63e;hpb=ceccf8dc7c3d7797e380f12b45cd3ea1d7396b58;p=dpdk.git diff --git a/doc/guides/platform/dpaa.rst b/doc/guides/platform/dpaa.rst index 3904871522..20a0e39329 100644 --- a/doc/guides/platform/dpaa.rst +++ b/doc/guides/platform/dpaa.rst @@ -4,7 +4,7 @@ NXP QorIQ DPAA Board Support Package ==================================== -This doc has information about steps to setup QorIq dpaa +This doc has information about steps to setup QorIQ dpaa based layerscape platform and information about common offload hw block drivers of **NXP QorIQ DPAA** SoC family. @@ -38,7 +38,7 @@ Common Offload HW Block Drivers Steps To Setup Platform ----------------------- -There are four main pre-requisities for executing DPAA PMD on a DPAA +There are four main pre-requisites for executing DPAA PMD on a DPAA compatible board: 1. **ARM 64 Tool Chain** @@ -58,17 +58,28 @@ compatible board: 4. **FMC Tool** - Before any DPDK application can be executed, the Frame Manager Configuration - Tool (FMC) need to be executed to set the configurations of the queues. This + If one is planning to use more than 1 Recv queue and hardware capability to + parse, classify and distribute the packets, the Frame Manager Configuration + Tool (FMC) need to be executed to set the configurations of the queues before + running the DPAA based DPDK application. This setting is persistent, the + configuration will remain in the hardware till it is re-configured. This includes the queue state, RSS and other policies. This tool can be obtained from `NXP (Freescale) Public Git Repository `_. This tool needs configuration files which are available in the :ref:`DPDK Extra Scripts `, described below for DPDK usages. -As an alternative method, DPAA PMD can also be executed using images provided -as part of SDK from NXP. The SDK includes all the above prerequisites necessary -to bring up a DPAA board. + Note that DPAA PMD can also be executed using images provided + as part of SDK from NXP. The SDK includes all the above prerequisites + necessary (i.e. fmc tool) to bring up a DPAA board. + + As an alternate method, DPAA PMDs starting from DPDK 20.11 also support the + fmlib library integration. The driver will detect about any existing FMC + based config (if /tmp/fmc.bin is present). DPAA FMD will be used only if no + previous fmc config is existing. + + Note that fmlib based integratin rely on underlying fmd driver in kernel, + which is available as part of NXP kernel or NXP SDK. The following dependencies are not part of DPDK and must be installed separately: