DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mk: Introduce NXP dpaa2 architecture based on armv8-a
Date: Mon, 09 May 2016 10:39:47 +0200	[thread overview]
Message-ID: <21220095.qH3WOBJJYD@xps13> (raw)
In-Reply-To: <1462801702-30918-1-git-send-email-hemant.agrawal@nxp.com>

2016-05-09 19:18, Hemant Agrawal:
> This patch introduces dpaa2 machine target to address difference
> in cpu parameter, number of core to 8 and no numa support
> w.r.t default armv8-a machine
> 
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
[...]
> --- /dev/null
> +++ b/mk/machine/dpaa2/rte.vars.mk
> +# ARCH =
> +# CROSS =
> +# MACHINE_CFLAGS =
> +# MACHINE_LDFLAGS =
> +# MACHINE_ASFLAGS =
> +# CPU_CFLAGS =
> +# CPU_LDFLAGS =
> +# CPU_ASFLAGS =
> +MACHINE_CFLAGS += -march=armv8-a
> +
> +ifdef CONFIG_RTE_ARCH_ARM_TUNE
> +MACHINE_CFLAGS += -mcpu=$(CONFIG_RTE_ARCH_ARM_TUNE)
> +endif

There is nothing specific in this file.

> --- a/mk/rte.module.mk
> +++ b/mk/rte.module.mk
> +#### Linaro toolchain usages arm64 instread of aarch64 in kernel
> +ifeq ($(ARCH), aarch64)
> +ARCH = arm64
> +endif

Could you provide more explanations please?
aarch64 shouldn't be used I think.

  parent reply	other threads:[~2016-05-09  8:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09 13:48 Hemant Agrawal
2016-05-09  8:20 ` Santosh Shukla
2016-05-09  8:39 ` Thomas Monjalon [this message]
2016-05-09  9:09   ` Hemant Agrawal
2016-05-09  9:06 ` Jerin Jacob
2016-05-09  9:13   ` Santosh Shukla
2016-05-09  9:16     ` Hemant Agrawal
2016-05-09 11:02   ` Jianbo Liu
2016-05-09 12:11     ` Jerin Jacob
2016-05-09 15:22       ` Jianbo Liu
2016-05-09 16:17         ` Jerin Jacob
2016-05-10  2:10           ` Jianbo Liu
2016-05-10  5:26             ` Jerin Jacob

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=21220095.qH3WOBJJYD@xps13 \
    --to=thomas.monjalon@6wind.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 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).