DPDK patches and discussions
 help / color / mirror / Atom feed
From: <lironh@marvell.com>
To: <jerinj@marvell.com>
Cc: <dev@dpdk.org>, <stable@dpdk.org>, Liron Himi <lironh@marvell.com>
Subject: [dpdk-dev] [PATCH] config: update Marvell ARMADA
Date: Fri, 29 Nov 2019 11:11:00 +0200	[thread overview]
Message-ID: <20191129091100.4252-1-lironh@marvell.com> (raw)

From: Liron Himi <lironh@marvell.com>

disable more NXP modules that conflict with MUSDK

Signed-off-by: Liron Himi <lironh@marvell.com>
---
 config/defconfig_arm64-armada-linuxapp-gcc | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/config/defconfig_arm64-armada-linuxapp-gcc b/config/defconfig_arm64-armada-linuxapp-gcc
index 059180284..c09751cf0 100644
--- a/config/defconfig_arm64-armada-linuxapp-gcc
+++ b/config/defconfig_arm64-armada-linuxapp-gcc
@@ -19,6 +19,23 @@ CONFIG_RTE_LIBRTE_PMD_MVSAM_CRYPTO=y
 
 # Disable NXP as it is conflict with MUSDK
 CONFIG_RTE_LIBRTE_DPAA_BUS=n
+CONFIG_RTE_LIBRTE_COMMON_DPAAX=n
+CONFIG_RTE_LIBRTE_FSLMC_BUS=n
+CONFIG_RTE_LIBRTE_DPAA2_MEMPOOL=n
+CONFIG_RTE_LIBRTE_DPAA2_PMD=n
+CONFIG_RTE_LIBRTE_DPAA_BUS=n
+CONFIG_RTE_LIBRTE_DPAA_MEMPOOL=n
+CONFIG_RTE_LIBRTE_DPAA_PMD=n
+CONFIG_RTE_LIBRTE_PMD_DPAA_EVENTDEV=n
+CONFIG_RTE_LIBRTE_PMD_DPAA_SEC=n
+CONFIG_RTE_LIBRTE_PMD_CAAM_JR=n
+CONFIG_RTE_LIBRTE_PMD_DPAA2_EVENTDEV=n
+CONFIG_RTE_LIBRTE_PMD_DPAA2_SEC=n
+CONFIG_RTE_LIBRTE_PMD_DPAA2_CMDIF_RAWDEV=n
+CONFIG_RTE_LIBRTE_PMD_DPAA2_QDMA_RAWDEV=n
+CONFIG_RTE_LIBRTE_PFE_PMD=n
+CONFIG_RTE_LIBRTE_ENETC_PMD=n
+
 
 # Doesn't support NUMA
 CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=n
-- 
2.23.0


             reply	other threads:[~2019-11-29  6:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29  9:11 lironh [this message]
2019-11-29 14:05 ` Jerin Jacob
2019-11-29 19:00   ` [dpdk-dev] [EXT] " Liron Himi
2019-12-02  4:11     ` Jerin Jacob
2019-12-02  6:32       ` Liron Himi
2019-12-02  7:01         ` Liron Himi
2019-12-02  7:33           ` Jerin Jacob
2020-01-23 10:01             ` Jerin Jacob
2020-02-06 14:01               ` Thomas Monjalon

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=20191129091100.4252-1-lironh@marvell.com \
    --to=lironh@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=stable@dpdk.org \
    /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).