DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: Ruifeng Wang <Ruifeng.Wang@arm.com>
Cc: "Juraj Linkeš" <juraj.linkes@pantheon.tech>,
	"Dharmik Jayesh Thakkar" <DharmikJayesh.Thakkar@arm.com>,
	"Honnappa Nagarahalli" <Honnappa.Nagarahalli@arm.com>,
	"ci@dpdk.org" <ci@dpdk.org>, nd <nd@arm.com>
Subject: Re: Intel QAT 8970 accel card on ARM Ampere Server
Date: Mon, 9 Oct 2023 22:28:51 -0400	[thread overview]
Message-ID: <CAJvnSUCdX5F0_XRZ-N16rf-WRLjaWnAiV+bjMqZ0hZcVn4n8fQ@mail.gmail.com> (raw)
In-Reply-To: <CAJvnSUD+g--7c79q-OHHY4-XBzqTqdtzKmGH7jjvYwhrD5DnZg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 465 bytes --]

Also I am just now thinking I probably should have provided dpdk-devbind.py
output:

probb@arm-ampere-dut:/tmp/dpdk/usertools$ dpdk-devbind.py --status
Crypto devices using kernel driver
==================================
0000:03:00.0 'C62x Chipset QuickAssist Technology 37c8' drv=c6xx
unused=vfio-pci
0000:04:00.0 'C62x Chipset QuickAssist Technology 37c8' drv=c6xx
unused=vfio-pci
0000:05:00.0 'C62x Chipset QuickAssist Technology 37c8' drv=c6xx
unused=vfio-pci

[-- Attachment #2: Type: text/html, Size: 551 bytes --]

  reply	other threads:[~2023-10-10  2:29 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31 17:13 Patrick Robb
2023-08-04  9:48 ` Ruifeng Wang
2023-08-08  7:07   ` Juraj Linkeš
2023-08-08  7:11     ` Ruifeng Wang
2023-08-11 21:18       ` Patrick Robb
2023-08-21  8:45         ` Juraj Linkeš
2023-08-30  0:05           ` Patrick Robb
2023-09-01 21:30           ` Patrick Robb
2023-09-11  8:13             ` Juraj Linkeš
2023-09-20 18:28               ` Patrick Robb
2023-09-25 15:19                 ` Ruifeng Wang
2023-10-09 16:34                   ` Patrick Robb
2023-10-10  2:28                     ` Patrick Robb [this message]
2023-10-10  3:55                       ` Dharmik Jayesh Thakkar
2023-10-10  7:25                         ` David Marchand
2023-10-10 15:03                           ` Dharmik Jayesh Thakkar
2023-10-10 15:12                             ` David Marchand
2023-10-10 15:59                         ` Patrick Robb
2023-10-10 21:50                           ` Dharmik Jayesh Thakkar
2023-10-11  8:14                           ` Juraj Linkeš
2023-10-11 20:13                             ` Patrick Robb
2023-11-02 22:00                               ` Patrick Robb
2023-11-14  7:34                                 ` Ruifeng Wang
2023-11-14 14:36                                   ` Patrick Robb
2024-02-27  6:58                                   ` Patrick Robb
2024-02-27 13:50                                     ` Honnappa Nagarahalli
2024-02-28 20:00                                       ` Patrick Robb
2024-02-28 20:40                                         ` Honnappa Nagarahalli
2024-03-07  5:27                                           ` Patrick Robb
2024-03-07  7:56                                             ` David Marchand
2023-10-11 11:51                           ` David Marchand

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=CAJvnSUCdX5F0_XRZ-N16rf-WRLjaWnAiV+bjMqZ0hZcVn4n8fQ@mail.gmail.com \
    --to=probb@iol.unh.edu \
    --cc=DharmikJayesh.Thakkar@arm.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=Ruifeng.Wang@arm.com \
    --cc=ci@dpdk.org \
    --cc=juraj.linkes@pantheon.tech \
    --cc=nd@arm.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).