DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Jianbo Liu <jianbo.liu@linaro.org>, <dev@dpdk.org>
Cc: <jerin.jacob@caviumnetworks.com>
Subject: Re: [dpdk-dev] [PATCH v2] armv8/config: enable igb_uio on arm64 platform
Date: Thu, 14 Sep 2017 17:01:11 +0530	[thread overview]
Message-ID: <e1d5d841-4253-83e7-943d-a342416fe926@nxp.com> (raw)
In-Reply-To: <1505361227-29822-1-git-send-email-jianbo.liu@linaro.org>

On 9/14/2017 9:23 AM, Jianbo Liu wrote:
> The kernel patch was merged to support pci resource mapping.
> https://patchwork.kernel.org/patch/9677441/
>
> So enable igu_uio in the default arm64 configuration.
>
> v2:
>   - keep headline format
>
> Signed-off-by: Jianbo Liu <jianbo.liu@linaro.org>
> ---
>  config/common_armv8a_linuxapp | 2 --
>  1 file changed, 2 deletions(-)
>
> diff --git a/config/common_armv8a_linuxapp b/config/common_armv8a_linuxapp
> index 880313a..6732d1e 100644
> --- a/config/common_armv8a_linuxapp
> +++ b/config/common_armv8a_linuxapp
> @@ -44,8 +44,6 @@ CONFIG_RTE_FORCE_INTRINSICS=y
>  # to address minimum DMA alignment across all arm64 implementations.
>  CONFIG_RTE_CACHE_LINE_SIZE=128
>
> -CONFIG_RTE_EAL_IGB_UIO=n
> -
>  CONFIG_RTE_LIBRTE_FM10K_PMD=n
>  CONFIG_RTE_LIBRTE_SFC_EFX_PMD=n
>  CONFIG_RTE_LIBRTE_AVP_PMD=n
>
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>

  parent reply	other threads:[~2017-09-14 11:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-14  3:00 [dpdk-dev] [PATCH] config: " Jianbo Liu
2017-09-14  3:23 ` Jerin Jacob
2017-09-14  3:53 ` [dpdk-dev] [PATCH v2] armv8/config: " Jianbo Liu
2017-09-14  5:23   ` santosh
2017-09-14  9:41     ` Ferruh Yigit
2017-09-14 10:05       ` Jianbo Liu
2017-09-14 11:31   ` Hemant Agrawal [this message]
2017-10-06 21:39     ` 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=e1d5d841-4253-83e7-943d-a342416fe926@nxp.com \
    --to=hemant.agrawal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=jianbo.liu@linaro.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).