All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com
Subject: Re: [PATCH v2 08/10] config: add dpaaX build support in common linuxapp
Date: Fri, 09 Mar 2018 18:11:33 +0100	[thread overview]
Message-ID: <1614156.TSxC4NnS1j@xps> (raw)
In-Reply-To: <1519889597-5805-9-git-send-email-hemant.agrawal@nxp.com>

Hi,

As you know the config options should be declared in common_base
and overwritten in common_linuxapp.

That's why there is no need to add comments in common_linuxapp.
And some of the options should be only in common_base, like
	CONFIG_RTE_LIBRTE_DPAA_HWDEBUG=n

Please try to move all the options in common_base with their comments,
and only overwrite what is needed for Linux compilation.

Thanks


01/03/2018 08:33, Hemant Agrawal:
> --- a/config/common_linuxapp
> +++ b/config/common_linuxapp
> @@ -23,3 +23,40 @@ CONFIG_RTE_LIBRTE_NFP_PMD=y
>  CONFIG_RTE_LIBRTE_POWER=y
>  CONFIG_RTE_VIRTIO_USER=y
>  CONFIG_RTE_PROC_INFO=y
> +#
> +# ARMv8 Specific driver compilation flags
> +#
> +
> +# Compile NXP DPAA Bus
> +CONFIG_RTE_LIBRTE_DPAA_BUS=y
> +CONFIG_RTE_LIBRTE_DPAA_HWDEBUG=n
> +
> +# Compile NXP DPAA Mempool
> +CONFIG_RTE_LIBRTE_DPAA_MEMPOOL=y
> +
> +# Compile bust-oriented NXP DPAA PMD
> +CONFIG_RTE_LIBRTE_DPAA_PMD=y
> +
> +# Compile schedule-oriented NXP DPAA Event Dev PMD
> +CONFIG_RTE_LIBRTE_PMD_DPAA_EVENTDEV=y
> +
> +# Compile NXP DPAA caam - crypto driver
> +CONFIG_RTE_LIBRTE_PMD_DPAA_SEC=y
> +CONFIG_RTE_LIBRTE_DPAA_MAX_CRYPTODEV=4
> +CONFIG_RTE_DPAA_SEC_PMD_MAX_NB_SESSIONS=2048
> +
> +# Compile NXP DPAA2 FSL-MC Bus
> +CONFIG_RTE_LIBRTE_FSLMC_BUS=y
> +
> +# Compile NXP DPAA2 Mempool
> +CONFIG_RTE_LIBRTE_DPAA2_MEMPOOL=y
> +
> +# Compile burst-oriented NXP DPAA2 PMD driver
> +CONFIG_RTE_LIBRTE_DPAA2_PMD=y
> +
> +# Compile schedule-oriented NXP DPAA2 EVENTDEV driver
> +CONFIG_RTE_LIBRTE_PMD_DPAA2_EVENTDEV=y
> +
> +# Compile NXP DPAA2 crypto sec driver for CAAM HW
> +CONFIG_RTE_LIBRTE_PMD_DPAA2_SEC=y
> +CONFIG_RTE_DPAA2_SEC_PMD_MAX_NB_SESSIONS=2048

  reply	other threads:[~2018-03-09 17:11 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27 17:25 [PATCH 0/7] meson build support for dpaaX Hemant Agrawal
2018-02-27 17:25 ` [PATCH 1/7] event/dpaa: fix include header Hemant Agrawal
2018-02-27 17:25 ` [PATCH 2/7] dpaa: prepare for 32 bit compilation Hemant Agrawal
2018-02-27 17:25 ` [PATCH 3/7] dpaa2: " Hemant Agrawal
2018-02-27 17:25 ` [PATCH 4/7] bus/fslmc: add 32 bit functional support for ARM Hemant Agrawal
2018-02-27 17:25 ` [PATCH 5/7] bus/dpaa: enabling dpaa compilation for other platforms Hemant Agrawal
2018-02-27 17:25 ` [PATCH 6/7] bus/fslmc: enabling dpaa2 " Hemant Agrawal
2018-02-28 14:45   ` Bruce Richardson
2018-02-28 16:02     ` Hemant Agrawal
2018-02-28 16:33       ` Richardson, Bruce
2018-02-27 17:25 ` [PATCH 7/7] build: add meson support for dpaaX platforms Hemant Agrawal
2018-02-28 14:44   ` Bruce Richardson
2018-03-01  6:10     ` Hemant Agrawal
2018-03-01 14:15       ` Thomas Monjalon
2018-03-09 16:49         ` Thomas Monjalon
2018-03-09 17:42           ` Hemant Agrawal
2018-03-01  7:33 ` [PATCH v2 00/10] meson build support for dpaaX Hemant Agrawal
2018-03-01  7:33   ` [PATCH v2 01/10] event/dpaa: fix include header Hemant Agrawal
2018-03-01  7:33   ` [PATCH v2 02/10] bus/dpaa: fix the BE compilation issue Hemant Agrawal
2018-03-01 12:22     ` Shreyansh Jain
2018-03-01  7:33   ` [PATCH v2 03/10] dpaa: prepare for 32 bit compilation Hemant Agrawal
2018-03-01  7:33   ` [PATCH v2 04/10] dpaa2: " Hemant Agrawal
2018-03-01  7:33   ` [PATCH v2 05/10] bus/fslmc: add 32 bit functional support for ARM Hemant Agrawal
2018-03-01  7:33   ` [PATCH v2 06/10] bus/dpaa: enabling dpaa compilation for other platforms Hemant Agrawal
2018-03-01  7:33   ` [PATCH v2 07/10] bus/fslmc: enabling dpaa2 " Hemant Agrawal
2018-03-01  7:33   ` [PATCH v2 08/10] config: add dpaaX build support in common linuxapp Hemant Agrawal
2018-03-09 17:11     ` Thomas Monjalon [this message]
2018-03-09 17:22       ` Hemant Agrawal
2018-03-01  7:33   ` [PATCH v2 09/10] build: add meson support for dpaaX platforms Hemant Agrawal
2018-03-01  7:33   ` [PATCH v2 10/10] build: add meson cross compile config for dpaaX Hemant Agrawal
2018-03-14  7:55   ` [PATCH v3 00/10] meson build support " Hemant Agrawal
2018-03-14  7:55     ` [PATCH v3 01/10] event/dpaa: fix include header Hemant Agrawal
2018-03-14  7:55     ` [PATCH v3 02/10] bus/dpaa: fix the BE compilation issue Hemant Agrawal
2018-03-14  7:55     ` [PATCH v3 03/10] dpaa: prepare for 32 bit compilation Hemant Agrawal
2018-03-14  7:56     ` [PATCH v3 04/10] dpaa2: " Hemant Agrawal
2018-03-14  7:56     ` [PATCH v3 05/10] bus/fslmc: add 32 bit functional support for ARM Hemant Agrawal
2018-03-14  7:56     ` [PATCH v3 06/10] bus/dpaa: enabling dpaa compilation for other platforms Hemant Agrawal
2018-03-14  7:56     ` [PATCH v3 07/10] bus/fslmc: enabling dpaa2 " Hemant Agrawal
2018-03-14  7:56     ` [PATCH v3 08/10] config: add dpaaX build support in common linuxapp Hemant Agrawal
2018-03-14  7:56     ` [PATCH v3 09/10] build: add meson support for dpaaX platforms Hemant Agrawal
2018-03-14  7:56     ` [PATCH v3 10/10] build: add meson cross compile config for dpaaX Hemant Agrawal
2018-03-14  9:08     ` [PATCH v3 00/10] meson build support " Bruce Richardson
2018-03-14  9:12       ` Hemant Agrawal
2018-03-15 17:10     ` Bruce Richardson

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=1614156.TSxC4NnS1j@xps \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.