archive mirror
 help / color / mirror / Atom feed
From: Sean V Kelley <>
Cc:, Sean V Kelley <>
Subject: [PATCH v2 0/1] pciutils: Add available DVSEC Details
Date: Thu,  9 Apr 2020 14:30:18 -0700	[thread overview]
Message-ID: <> (raw)

Changes since v1 [1]:

- Use consistent syntax to match other lspci capability output.
(Bjorn Helgaas)


Add separate Designated Vendor-Specific Capability (DVSEC) defines
and cap function so as to align with PCIe r5.0, sec terms and
provide available details.  First step in later adding support for CXL.


Sean V Kelley (1):
  lspci: Add available DVSEC details

 lib/header.h    |   4 +
 ls-ecaps.c      |  25 +++-
 tests/cap-dvsec | 340 ++++++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 368 insertions(+), 1 deletion(-)
 create mode 100644 tests/cap-dvsec


             reply	other threads:[~2020-04-09 21:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09 21:30 Sean V Kelley [this message]
2020-04-09 21:30 ` [PATCH v2 1/1] lspci: Add available DVSEC details Sean V Kelley

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).