DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: dev@dpdk.org
Cc: ferruh.yigit@intel.com, Scott Branden <scott.branden@broadcom.com>
Subject: [dpdk-dev] [PATCH 1/4] introduce Broadcom Stingray
Date: Wed, 21 Mar 2018 11:06:26 -0700	[thread overview]
Message-ID: <20180321180629.58318-2-ajit.khaparde@broadcom.com> (raw)
In-Reply-To: <20180321180629.58318-1-ajit.khaparde@broadcom.com>

From: Scott Branden <scott.branden@broadcom.com>

Add Broadcom Stingray machine support based on armv8.

For product brief see:
https://www.broadcom.com/products/ethernet-connectivity/controllers/bcm58800

Signed-off-by: Scott Branden <scott.branden@broadcom.com>
Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
---
 config/defconfig_arm64-stingray-linuxapp-gcc | 16 ++++++++++++++
 mk/machine/stingray/rte.vars.mk              | 31 ++++++++++++++++++++++++++++
 2 files changed, 47 insertions(+)
 create mode 100644 config/defconfig_arm64-stingray-linuxapp-gcc
 create mode 100644 mk/machine/stingray/rte.vars.mk

diff --git a/config/defconfig_arm64-stingray-linuxapp-gcc b/config/defconfig_arm64-stingray-linuxapp-gcc
new file mode 100644
index 000000000..247e53eaa
--- /dev/null
+++ b/config/defconfig_arm64-stingray-linuxapp-gcc
@@ -0,0 +1,16 @@
+# SPDX-License-Identifier: BSD-3-Clause
+# Copyright (C) Broadcom 2017-2018. All rights reserved.
+#
+
+#include "defconfig_arm64-armv8a-linuxapp-gcc"
+
+# Broadcom - Stingray
+CONFIG_RTE_MACHINE="stingray"
+CONFIG_RTE_ARCH_ARM_TUNE="cortex-a72"
+
+# Doesn't support NUMA
+CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=n
+CONFIG_RTE_LIBRTE_VHOST_NUMA=n
+
+CONFIG_RTE_EAL_IGB_UIO=y
+CONFIG_RTE_KNI_KMOD=n
diff --git a/mk/machine/stingray/rte.vars.mk b/mk/machine/stingray/rte.vars.mk
new file mode 100644
index 000000000..bc3b7dc95
--- /dev/null
+++ b/mk/machine/stingray/rte.vars.mk
@@ -0,0 +1,31 @@
+# SPDX-License-Identifier: BSD-3-Clause
+# Copyright (C) Broadcom 2017-2018. All rights reserved.
+#
+
+#
+# machine:
+#
+#   - can define ARCH variable (overridden by cmdline value)
+#   - can define CROSS variable (overridden by cmdline value)
+#   - define MACHINE_CFLAGS variable (overridden by cmdline value)
+#   - define MACHINE_LDFLAGS variable (overridden by cmdline value)
+#   - define MACHINE_ASFLAGS variable (overridden by cmdline value)
+#   - can define CPU_CFLAGS variable (overridden by cmdline value) that
+#     overrides the one defined in arch.
+#   - can define CPU_LDFLAGS variable (overridden by cmdline value) that
+#     overrides the one defined in arch.
+#   - can define CPU_ASFLAGS variable (overridden by cmdline value) that
+#     overrides the one defined in arch.
+#   - may override any previously defined variable
+#
+
+# ARCH =
+# CROSS =
+# MACHINE_CFLAGS =
+# MACHINE_LDFLAGS =
+# MACHINE_ASFLAGS =
+# CPU_CFLAGS =
+# CPU_LDFLAGS =
+# CPU_ASFLAGS =
+
+MACHINE_CFLAGS += -march=armv8-a+crc+crypto
-- 
2.14.3 (Apple Git-98)

  reply	other threads:[~2018-03-21 18:06 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-21 18:06 [dpdk-dev] [PATCH 0/4] bnxt patchset Ajit Khaparde
2018-03-21 18:06 ` Ajit Khaparde [this message]
2018-03-30 10:34   ` [dpdk-dev] [PATCH 1/4] introduce Broadcom Stingray Ferruh Yigit
2018-03-30 18:54     ` Scott Branden
2018-03-21 18:06 ` [dpdk-dev] [PATCH 2/4] net/bnxt: add support for Stingray PF devices ids Ajit Khaparde
2018-03-30 10:35   ` Ferruh Yigit
2018-03-30 18:24     ` Scott Branden
2018-04-10  0:20     ` [dpdk-dev] [PATCH v4 0/3] bnxt patchset to support Stingray product family Ajit Khaparde
2018-04-10  0:20       ` [dpdk-dev] [PATCH v4 1/3] introduce Broadcom Stingray Ajit Khaparde
2018-04-10  0:20       ` [dpdk-dev] [PATCH v4 2/3] net/bnxt: add support for Stingray PF devices ids Ajit Khaparde
2018-04-10  0:20       ` [dpdk-dev] [PATCH v4 3/3] doc: add Broadcom Stingray SoC support to release notes Ajit Khaparde
2018-04-11 19:07         ` Ferruh Yigit
2018-04-13 21:07           ` [dpdk-dev] [PATCH v5 1/3] introduce Broadcom Stingray Ajit Khaparde
2018-04-13 21:07             ` [dpdk-dev] [PATCH v5 2/3] net/bnxt: add support for Stingray PF devices ids Ajit Khaparde
2018-04-13 21:07             ` [dpdk-dev] [PATCH v5 3/3] doc: add Broadcom Stingray SoC support to release notes Ajit Khaparde
2018-04-13 23:07             ` [dpdk-dev] [PATCH v5 1/3] introduce Broadcom Stingray Ferruh Yigit
2018-03-21 18:06 ` [dpdk-dev] [PATCH 3/4] mk: allow kernel artifacts to be located in output directory Ajit Khaparde
2018-03-30 10:35   ` Ferruh Yigit
2018-03-30 18:23     ` Scott Branden
2018-04-03 14:18       ` Ferruh Yigit
     [not found]         ` <CACZ4nhuwOp99YiaD75TzQ1igPgnjsayqHLnXyaNmmpySVZefPA@mail.gmail.com>
2018-04-06 18:10           ` Scott Branden
2018-04-06 21:31             ` Ferruh Yigit
2018-04-06 22:32               ` Scott Branden
2018-04-10 14:59                 ` Ferruh Yigit
2018-04-10 20:30                   ` Scott Branden
2018-03-21 18:06 ` [dpdk-dev] [PATCH 4/4] igb_uio: bind error if pcie bridge Ajit Khaparde
2018-03-26 17:24   ` Ferruh Yigit
2018-03-26 18:05     ` Scott Branden
2018-03-26 18:20       ` Ferruh Yigit
2018-03-26 19:13         ` Scott Branden
2018-03-26 20:43         ` [dpdk-dev] [PATCH v2] " Ajit Khaparde

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=20180321180629.58318-2-ajit.khaparde@broadcom.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=scott.branden@broadcom.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).