DPDK patches and discussions
 help / color / mirror / Atom feed
From: <lironh@marvell.com>
To: <thomas@monjalon.net>
Cc: <dev@dpdk.org>, Liron Himi <lironh@marvell.com>
Subject: [dpdk-dev] [PATCH 2/2] meson: add Marvell ARMADA architecture based on armv8-a
Date: Sat, 18 May 2019 00:27:20 +0300	[thread overview]
Message-ID: <1558128440-15776-3-git-send-email-lironh@marvell.com> (raw)
In-Reply-To: <1558128440-15776-1-git-send-email-lironh@marvell.com>

From: Liron Himi <lironh@marvell.com>

Change-Id: If210dbfeed447df3beffd53339a40e4a9069b6dc
Signed-off-by: Liron Himi <lironh@marvell.com>
Reviewed-by: Jerin Jacob Kollanukkaran <Jerin.Jacob@cavium.com>
---
 config/arm/arm64_armada_linux_gcc | 16 ++++++++++++++++
 config/arm/meson.build            |  8 +++++++-
 2 files changed, 23 insertions(+), 1 deletion(-)
 create mode 100644 config/arm/arm64_armada_linux_gcc

diff --git a/config/arm/arm64_armada_linux_gcc b/config/arm/arm64_armada_linux_gcc
new file mode 100644
index 0000000..6e6d56f
--- /dev/null
+++ b/config/arm/arm64_armada_linux_gcc
@@ -0,0 +1,16 @@
+[binaries]
+c = 'aarch64-linux-gnu-gcc'
+cpp = 'aarch64-linux-gnu-cpp'
+ar = 'aarch64-linux-gnu-ar'
+as = 'aarch64-linux-gnu-as'
+strip = 'aarch64-linux-gnu-strip'
+pcap-config = ''
+
+[host_machine]
+system = 'linux'
+cpu_family = 'aarch64'
+cpu = 'armv8-a'
+endian = 'little'
+
+[properties]
+implementor_id = '0x56'
diff --git a/config/arm/meson.build b/config/arm/meson.build
index 7fa6ed3..32decba 100644
--- a/config/arm/meson.build
+++ b/config/arm/meson.build
@@ -56,6 +56,12 @@ flags_dpaa2 = [
 	['RTE_MAX_NUMA_NODES', 1],
 	['RTE_MAX_LCORE', 16],
 	['RTE_LIBRTE_DPAA2_USE_PHYS_IOVA', false]]
+flags_armada = [
+	['RTE_MACHINE', '"armv8a"'],
+	['RTE_CACHE_LINE_SIZE', 64],
+	['RTE_MAX_NUMA_NODES', 1],
+	['RTE_MAX_LCORE', 16]]
+
 flags_default_extra = []
 flags_thunderx_extra = [
 	['RTE_MACHINE', '"thunderx"'],
@@ -104,7 +110,7 @@ impl_0x4e = ['NVIDIA', flags_generic, machine_args_generic]
 impl_0x50 = ['AppliedMicro', flags_generic, machine_args_generic]
 impl_0x51 = ['Qualcomm', flags_generic, machine_args_generic]
 impl_0x53 = ['Samsung', flags_generic, machine_args_generic]
-impl_0x56 = ['Marvell', flags_generic, machine_args_generic]
+impl_0x56 = ['Marvell ARMADA', flags_armada, machine_args_generic]
 impl_0x69 = ['Intel', flags_generic, machine_args_generic]
 impl_dpaa = ['NXP DPAA', flags_dpaa, machine_args_generic]
 impl_dpaa2 = ['NXP DPAA2', flags_dpaa2, machine_args_generic]
-- 
2.7.4


  parent reply	other threads:[~2019-05-17 19:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-17 21:27 [dpdk-dev] [PATCH 0/2] Introduces armada target lironh
2019-05-17 21:27 ` [dpdk-dev] [PATCH 1/2] mk: add Marvell ARMADA architecture based on armv8-a lironh
2019-05-22  9:11   ` Ruifeng Wang (Arm Technology China)
2019-05-22  9:12     ` Liron Himi
2019-05-23 10:11   ` Ruifeng Wang (Arm Technology China)
2019-05-23 10:51     ` Liron Himi
2019-05-24  1:10       ` Ruifeng Wang (Arm Technology China)
2019-05-24 13:06         ` Ferruh Yigit
2019-05-27  1:42           ` Ruifeng Wang (Arm Technology China)
2019-05-17 21:27 ` lironh [this message]
2019-05-17 21:34 [dpdk-dev] [PATCH 0/2] Introduces armada target lironh
2019-05-17 21:34 ` [dpdk-dev] [PATCH 2/2] meson: add Marvell ARMADA architecture based on armv8-a lironh

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=1558128440-15776-3-git-send-email-lironh@marvell.com \
    --to=lironh@marvell.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).