DPDK patches and discussions
 help / color / mirror / Atom feed
From: Fiona Trahe <fiona.trahe@intel.com>
To: dev@dpdk.org, pablo.de.lara.guarch@intel.com,
	arkadiuszx.kusztal@intel.com
Cc: deepak.k.jain@intel.com, fiona.trahe@intel.com, john.griffin@intel.com
Subject: [dpdk-dev] [PATCH v2 3/3] doc: add support for Intel QAT device D15xx
Date: Thu,  9 Mar 2017 19:20:47 +0000	[thread overview]
Message-ID: <1489087247-456-4-git-send-email-fiona.trahe@intel.com> (raw)
In-Reply-To: <1487691610-11974-1-git-send-email-fiona.trahe@intel.com>

Add instructions for D15xx device to the QAT PMD guide.

Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
---
 doc/guides/cryptodevs/qat.rst | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/doc/guides/cryptodevs/qat.rst b/doc/guides/cryptodevs/qat.rst
index 4927a00..897919e 100644
--- a/doc/guides/cryptodevs/qat.rst
+++ b/doc/guides/cryptodevs/qat.rst
@@ -36,6 +36,7 @@ hardware accelerator devices:
 * ``Intel QuickAssist Technology DH895xCC``
 * ``Intel QuickAssist Technology C62x``
 * ``Intel QuickAssist Technology C3xxx``
+* ``Intel QuickAssist Technology D15xx``
 
 
 Features
@@ -111,12 +112,15 @@ available kernel drivers and device ids are :
    DH895xCC,4.4+,qat_dh895xcc,dh895xcc,435,1,443,32
    C62x,4.5+,qat_c62x,c6xx,37c8,3,37c9,16
    C3xxx,4.5+,qat_c3xxx,c3xxx,19e2,1,19e3,16
+   D15xx,**,qat_d15xx,d15xx,6f54,1,6f55,16
 
 
 The ``driver`` column indicates either the linux kernel version in which support
 for this device was introduced or a driver available on Intel's 01.org website.
 There are both linux and 01.org kernel drivers available for some devices.
 
+    ** Release to be confirmed.
+
 
 If you are running on a kernel which includes a driver for your device, see
 `Installation using kernel.org driver`_ below. Otherwise see
@@ -308,7 +312,7 @@ the unbind command below::
         done; \
     done
 
-For **Intel(R) QuickAssist Technology C3xxx** device:
+For **Intel(R) QuickAssist Technology C3xxx or D15xx** device:
 
 The unbind command below assumes ``bdfs`` of ``01:01.00-01:02.07``,
 if your VFs are different adjust the unbind command below::
-- 
2.5.0

  parent reply	other threads:[~2017-03-09 19:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21 15:40 [dpdk-dev] [PATCH] crypto/qat: " Fiona Trahe
2017-03-09 19:20 ` [dpdk-dev] [PATCH v2 0/3] " Fiona Trahe
2017-03-09 19:20 ` [dpdk-dev] [PATCH v2 1/3] " Fiona Trahe
2017-03-30  8:30   ` Jain, Deepak K
2017-03-09 19:20 ` [dpdk-dev] [PATCH v2 2/3] doc: restructure QAT PMD guide Fiona Trahe
2017-03-22 12:29   ` Mcnamara, John
2017-03-09 19:20 ` Fiona Trahe [this message]
2017-03-22 12:35   ` [dpdk-dev] [PATCH v2 3/3] doc: add support for Intel QAT device D15xx Mcnamara, John
2017-04-03 14:13 ` [dpdk-dev] [PATCH v3 0/3] crypto/qat: " Fiona Trahe
2017-04-04  9:48   ` De Lara Guarch, Pablo
2017-04-03 14:13 ` [dpdk-dev] [PATCH v3 1/3] " Fiona Trahe
2017-04-03 15:10   ` Jain, Deepak K
2017-04-03 14:13 ` [dpdk-dev] [PATCH v3 2/3] doc: restructure QAT PMD guide Fiona Trahe
2017-04-03 15:15   ` Mcnamara, John
2017-04-03 14:13 ` [dpdk-dev] [PATCH v3 3/3] doc: add support for Intel QAT device D15xx Fiona Trahe
2017-04-03 15:15   ` Mcnamara, John

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=1489087247-456-4-git-send-email-fiona.trahe@intel.com \
    --to=fiona.trahe@intel.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=deepak.k.jain@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.griffin@intel.com \
    --cc=pablo.de.lara.guarch@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 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).