From: Timothy McDaniel <timothy.mcdaniel@intel.com>
Cc: dev@dpdk.org, jerinj@marvell.com, harry.van.haaren@intel.com,
mdr@ashroe.eu, nhorman@tuxdriver.com, nikhil.rao@intel.com,
erik.g.carrillo@intel.com, abhinandan.gujjar@intel.com,
pbhagavatula@marvell.com, hemant.agrawal@nxp.com,
mattias.ronnblom@ericsson.com, peter.mccarthy@intel.com
Subject: [dpdk-dev] [PATCH] usertools/devbind: add dlb
Date: Wed, 21 Apr 2021 15:04:01 -0500 [thread overview]
Message-ID: <1619035442-4504-1-git-send-email-timothy.mcdaniel@intel.com> (raw)
Add dlb to usertools/dpdk-devbind.py so that it shows up
as an eventdev, and is identified as Intel dlb.
Signed-off-by: Timothy McDaniel <timothy.mcdaniel@intel.com>
---
usertools/dpdk-devbind.py | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/usertools/dpdk-devbind.py b/usertools/dpdk-devbind.py
index 98bd1b7..f36d294 100755
--- a/usertools/dpdk-devbind.py
+++ b/usertools/dpdk-devbind.py
@@ -59,11 +59,13 @@
'SVendor': None, 'SDevice': None}
intel_ntb_icx = {'Class': '06', 'Vendor': '8086', 'Device': '347e',
'SVendor': None, 'SDevice': None}
+intel_dlb = {'Class': '0b', 'Vendor': '8086', 'Device': '270b,2710,2714',
+ 'SVendor': None, 'SDevice': None}
network_devices = [network_class, cavium_pkx, avp_vnic, ifpga_class]
baseband_devices = [acceleration_class]
crypto_devices = [encryption_class, intel_processor_class]
-eventdev_devices = [cavium_sso, cavium_tim, octeontx2_sso]
+eventdev_devices = [cavium_sso, cavium_tim, octeontx2_sso, intel_dlb]
mempool_devices = [cavium_fpa, octeontx2_npa]
compress_devices = [cavium_zip]
regex_devices = [octeontx2_ree]
--
1.7.10
next reply other threads:[~2021-04-21 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 20:04 Timothy McDaniel [this message]
2021-04-25 15:53 ` [dpdk-dev] [PATCH] usertools/devbind: add dlb Thomas Monjalon
2021-04-26 13:00 ` McDaniel, Timothy
2021-04-26 15:34 ` [dpdk-dev] [PATCH v2 1/1] " Timothy McDaniel
2021-05-19 9:47 ` Thomas Monjalon
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=1619035442-4504-1-git-send-email-timothy.mcdaniel@intel.com \
--to=timothy.mcdaniel@intel.com \
--cc=abhinandan.gujjar@intel.com \
--cc=dev@dpdk.org \
--cc=erik.g.carrillo@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=mdr@ashroe.eu \
--cc=nhorman@tuxdriver.com \
--cc=nikhil.rao@intel.com \
--cc=pbhagavatula@marvell.com \
--cc=peter.mccarthy@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.