linux-kernel - [PATCH 0/2] fpga: dfl: optional VSEC for start of dfl

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 16 Nov 2020 17:25:50 -0800
From:   matthew.gerlach@...ux.intel.com
To:     linux-fpga@...r.kernel.org, linux-kernel@...r.kernel.org,
        mdf@...nel.org, hao.wu@...el.com, trix@...hat.com,
        linux-doc@...r.kernel.org, corbet@....net
Cc:     Matthew Gerlach <matthew.gerlach@...ux.intel.com>
Subject: [PATCH 0/2] fpga: dfl: optional VSEC for start of dfl

From: Matthew Gerlach <matthew.gerlach@...ux.intel.com>

The start of a Device Feature List (DFL) is currently assumed to be at
Bar0/Offset 0 on the PCIe bus by drivers/fpga/dfl-pci.c.  This patchset
adds support for the start of one or more DFLs to be specified in a
Vendor-Specific Capability (VSEC) structure in PCIe config space.  If no
such VSEC structure exists, then the start of the DFL is assumed to be 
Bar0/Offset 0 for backward compatibility.

Matthew Gerlach (2):
  fpga: dfl: refactor cci_enumerate_feature_devs()
  fpga: dfl: look for vendor specific capability

 Documentation/fpga/dfl.rst |  10 +++
 drivers/fpga/dfl-pci.c     | 168 +++++++++++++++++++++++++++++--------
 2 files changed, 143 insertions(+), 35 deletions(-)

-- 
2.25.2