Hello Ferruh,

On Thursday 16 February 2017 06:09 AM, Hemant Agrawal wrote:
QBMAN, is a hardware block which interfaces with the other
accelerating hardware blocks (For e.g., WRIOP) on NXP's DPAA2
SoC for queue, buffer and packet scheduling.

This patch introduces a userspace driver for interfacing with
the QBMAN hw block.

The qbman-portal component provides APIs to do the low level
hardware bit twiddling for operations such as:
      -initializing Qman software portals
      -building and sending portal commands
      -portal interrupt configuration and processing

This same/similar code is used in kernel and compat file is used
to make it working in user space.

Signed-off-by: Geoff Thorpe <geoff.tho...@nxp.com>
Signed-off-by: Roy Pledge <roy.ple...@nxp.com>
Signed-off-by: Hemant Agrawal <hemant.agra...@nxp.com>
---

[snip]

diff --git a/drivers/common/dpaa2/qbman/rte_common_dpaa2_qbman_version.map 
b/drivers/common/dpaa2/qbman/rte_common_dpaa2_qbman_version.map
new file mode 100644
index 0000000..f653421
--- /dev/null
+++ b/drivers/common/dpaa2/qbman/rte_common_dpaa2_qbman_version.map
@@ -0,0 +1,27 @@
+DPDK_17.02 {
+       global:
+
+       qbman_check_command_complete;
+       qbman_eq_desc_clear;
+       qbman_eq_desc_set_fq;
+       qbman_eq_desc_set_no_orp;
+       qbman_eq_desc_set_qd;
+       qbman_eq_desc_set_response;
+       qbman_get_version;
+       qbman_pull_desc_clear;
+       qbman_pull_desc_set_fq;
+       qbman_pull_desc_set_numframes;
+       qbman_pull_desc_set_storage;
+       qbman_release_desc_clear;
+       qbman_release_desc_set_bpid;
+       qbman_result_DQ_fd;
+       qbman_result_DQ_flags;
+       qbman_result_has_new_result;
+       qbman_swp_acquire;
+       qbman_swp_init;
+       qbman_swp_pull;
+       qbman_swp_release;
+       qbman_swp_send_multiple;
+
+       local: *;
+};


Just wanted to highlight that we have not yet changed the exported
variable in the v7 post. I have a draft patch (based on yours and
Neil's suggestions) which I will share soon.

That involves changing source between our internal repo to dpdk -
feasibility of this is where are discussions internally stand.

Reply via email to