From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org, jerin.jacob@caviumnetworks.com,
jianbo.liu@linaro.org, santosh.shukla@caviumnetworks.com
Subject: Re: [dpdk-dev] [PATCHv3 1/2] config/armv8a: disable igb_uio
Date: Fri, 13 May 2016 14:50:48 +0200 [thread overview]
Message-ID: <2246279.hMUGCBBRbv@xps13> (raw)
In-Reply-To: <1462974479-26180-1-git-send-email-hemant.agrawal@nxp.com>
2016-05-11 19:17, Hemant Agrawal:
> IGB_UIO not supported for arm64 arch in kernel so disable.
If I understand well, a patch is needed in the kernel to make
igb_uio works? Please confirm.
In that case, yes, the default configuration should be to disable
igb_uio.
Please note it's just a default to make it work in most common cases.
And yes, the default should focus on recent kernels and future directions.
> +CONFIG_RTE_EAL_IGB_UIO=n
next prev parent reply other threads:[~2016-05-13 12:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 13:47 Hemant Agrawal
2016-05-11 13:47 ` [dpdk-dev] [PATCHv3 2/2] mk: Introduce NXP dpaa2 architecture based on armv8-a Hemant Agrawal
2016-05-11 15:22 ` [dpdk-dev] [PATCHv3 1/2] config/armv8a: disable igb_uio Stephen Hemminger
2016-05-11 16:57 ` Santosh Shukla
2016-05-11 17:02 ` Jerin Jacob
2016-05-11 18:25 ` Stephen Hemminger
2016-05-12 2:01 ` Jianbo Liu
2016-05-12 3:17 ` Santosh Shukla
2016-05-12 3:42 ` Jianbo Liu
2016-05-12 5:06 ` Santosh Shukla
2016-05-12 5:54 ` Jianbo Liu
2016-05-12 8:57 ` Santosh Shukla
2016-05-12 9:52 ` Jianbo Liu
2016-05-12 10:31 ` Santosh Shukla
2016-05-13 1:43 ` Jianbo Liu
2016-05-13 3:37 ` Hemant Agrawal
2016-05-13 7:47 ` Jerin Jacob
2016-05-13 10:09 ` Jianbo Liu
2016-05-12 3:00 ` Jerin Jacob
2016-05-13 12:50 ` Thomas Monjalon [this message]
2016-05-13 13:11 ` Santosh Shukla
2016-05-18 14:28 ` 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=2246279.hMUGCBBRbv@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=jianbo.liu@linaro.org \
--cc=santosh.shukla@caviumnetworks.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).