From: Jan Viktorin <viktorin@rehivetech.com>
To: dev@dpdk.org
Cc: Rasesh Mody <rasesh.mody@qlogic.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>,
Jan Viktorin <viktorin@rehivetech.com>
Subject: [dpdk-dev] [PATCH] armv7a: disable qede pmd
Date: Mon, 9 May 2016 23:34:16 +0200 [thread overview]
Message-ID: <1462829656-2135-1-git-send-email-viktorin@rehivetech.com> (raw)
The qede PMD driver is failing when building for ARMv7:
drivers/net/qede/base/ecore_dev.c: In function ‘ecore_hw_init_pf’:
drivers/net/qede/base/ecore_dev.c:1150:6:
error: variable ‘prs_reg’ set but not used [-Werror=unused-but-set-variable]
u32 prs_reg;
^
[...]
drivers/net/qede/base/ecore_dev.c:2492:13:
error: variable ‘p_phys’ set but not used [-Werror=unused-but-set-variable]
dma_addr_t p_phys = p_chain->p_phys_addr, p_phys_next = 0;
^
drivers/net/qede/base/ecore_dev.c: In function ‘ecore_chain_free_pbl’:
drivers/net/qede/base/ecore_dev.c:2532:39:
error: variable ‘pbl_size’ set but not used [-Werror=unused-but-set-variable]
u32 page_cnt = p_chain->page_cnt, i, pbl_size;
Fixes: 3eae93a9bfd5 ("qede: enable PMD build")
Signed-off-by: Jan Viktorin <viktorin@rehivetech.com>
---
config/defconfig_arm-armv7a-linuxapp-gcc | 1 +
1 file changed, 1 insertion(+)
diff --git a/config/defconfig_arm-armv7a-linuxapp-gcc b/config/defconfig_arm-armv7a-linuxapp-gcc
index e626ec1..bde6acd 100644
--- a/config/defconfig_arm-armv7a-linuxapp-gcc
+++ b/config/defconfig_arm-armv7a-linuxapp-gcc
@@ -74,3 +74,4 @@ CONFIG_RTE_LIBRTE_MPIPE_PMD=n
CONFIG_RTE_LIBRTE_VMXNET3_PMD=n
CONFIG_RTE_LIBRTE_PMD_XENVIRT=n
CONFIG_RTE_LIBRTE_PMD_BNX2X=n
+CONFIG_RTE_LIBRTE_QEDE_PMD=n
--
2.6.2
next reply other threads:[~2016-05-09 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 21:34 Jan Viktorin [this message]
2016-05-13 15: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=1462829656-2135-1-git-send-email-viktorin@rehivetech.com \
--to=viktorin@rehivetech.com \
--cc=dev@dpdk.org \
--cc=rasesh.mody@qlogic.com \
--cc=thomas.monjalon@6wind.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).