Because using a NFP PMD requires specific BSP installed, the PMD support was not the default option before. This was just for making people aware of such dependency, since there is no need for such a BSP for just compiling DPDK with NFP PMD support.
Signed-off-by: Alejandro Lucero <alejandro.luc...@netronome.com> --- config/common_base | 2 +- doc/guides/nics/nfp.rst | 10 ++++++---- 2 files changed, 7 insertions(+), 5 deletions(-) diff --git a/config/common_base b/config/common_base index 8e9dcfa..3fd62d6 100644 --- a/config/common_base +++ b/config/common_base @@ -248,7 +248,7 @@ CONFIG_RTE_LIBRTE_ENIC_DEBUG=n # # Compile burst-oriented Netronome NFP PMD driver # -CONFIG_RTE_LIBRTE_NFP_PMD=n +CONFIG_RTE_LIBRTE_NFP_PMD=y CONFIG_RTE_LIBRTE_NFP_DEBUG=n # diff --git a/doc/guides/nics/nfp.rst b/doc/guides/nics/nfp.rst index 4ef6e02..b643e5b 100644 --- a/doc/guides/nics/nfp.rst +++ b/doc/guides/nics/nfp.rst @@ -68,10 +68,12 @@ Building the software --------------------- Netronome's PMD code is provided in the **drivers/net/nfp** directory. -Because Netronome´s BSP dependencies the driver is disabled by default -in DPDK build using **common_linuxapp configuration** file. Enabling the -driver or if you use another configuration file and want to have NFP -support, this variable is needed: +Although NFP PMD has Netronome´s BSP dependencies, it is possible to +compile it along with other DPDK PMDs even if no BSP was installed before. +Of course, a DPDK app will require such a BSP installed for using the +NFP PMD. + +Default PMD configuration is at **common_linuxapp configuration** file: - **CONFIG_RTE_LIBRTE_NFP_PMD=y** -- 1.9.1
