From: Qingmin Liu <qingmin.liu@broadcom.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org, ajit.khaparde@broadcom.com,
Qingmin Liu <qingmin.liu@broadcom.com>
Subject: [dpdk-dev] [PATCH v1 1/1] config: add Broadcom Stingray for meson cross-compilation
Date: Mon, 6 Jan 2020 10:06:27 +0800 [thread overview]
Message-ID: <20200106020627.206262-2-qingmin.liu@broadcom.com> (raw)
In-Reply-To: <20200106020627.206262-1-qingmin.liu@broadcom.com>
Broadcom Stingray is armv8 CPU having cortex-a72. The implementor ID is
0x41 (arm) and the primary part number is 0xd08 (cortex-a72).
Signed-off-by: Qingmin Liu <qingmin.liu@broadcom.com>
---
config/arm/arm64_stingray_linux_gcc | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
create mode 100644 config/arm/arm64_stingray_linux_gcc
diff --git a/config/arm/arm64_stingray_linux_gcc b/config/arm/arm64_stingray_linux_gcc
new file mode 100644
index 000000000..86797d23c
--- /dev/null
+++ b/config/arm/arm64_stingray_linux_gcc
@@ -0,0 +1,17 @@
+[binaries]
+c = 'aarch64-linux-gnu-gcc'
+cpp = 'aarch64-linux-gnu-cpp'
+ar = 'aarch64-linux-gnu-gcc-ar'
+strip = 'aarch64-linux-gnu-strip'
+pkgconfig = 'aarch64-linux-gnu-pkg-config'
+pcap-config = ''
+
+[host_machine]
+system = 'linux'
+cpu_family = 'aarch64'
+cpu = 'armv8-a'
+endian = 'little'
+
+[properties]
+implementor_id = '0x41'
+implementor_pn = '0xd08'
--
2.21.0
next prev parent reply other threads:[~2020-01-06 2:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 2:06 [dpdk-dev] [PATCH v1 0/1] Add " Qingmin Liu
2020-01-06 2:06 ` Qingmin Liu [this message]
2020-02-06 14:04 ` [dpdk-dev] [PATCH v1 1/1] config: add " Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2020-01-06 1:19 [dpdk-dev] [PATCH v1 0/1] Add " Qingmin Liu
2020-01-06 1:19 ` [dpdk-dev] [PATCH v1 1/1] config: add " Qingmin Liu
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=20200106020627.206262-2-qingmin.liu@broadcom.com \
--to=qingmin.liu@broadcom.com \
--cc=ajit.khaparde@broadcom.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).