Update license comments and added SPDX license identifiers

Previously, the only information about the specific version of GPL
was present in the README and individual source files mentioned only
GPL

Update license comments and added SPDX license identifiers

Previously, the only information about the specific version of GPL
was present in the README and individual source files mentioned only
GPL alone.

Let us update all copyright comments to explicitly say "GPL v2+"
and also include the machine readable SPDX license identifier.

show more ...

VPD: When printing item IDs, escape non-ASCII characters

VPD: Cleanup

pciutils: Add decoding of vendor specific VPD fields

IBM has defined several VPD fields that are not part of the PCI
spec, but are frequently used on embedded and pluggable pcie
adapters.

Since the

pciutils: Add decoding of vendor specific VPD fields

IBM has defined several VPD fields that are not part of the PCI
spec, but are frequently used on embedded and pluggable pcie
adapters.

Since these fields are "Unknown", they are listed in hex
and less readable.

This patch adds commonly used vendor specific VPD keywords
described in "Table 160. LoPAPR VPD Fields" of the Linux on Power
Architecture Platform Reference (LoPAPR).

Signed-off-by: John Walthour <[email protected]>

show more ...

pciutils: change MN VPD keyword to F_TEXT

The PCI spec defines all keyword data fields as ASCII unless
otherwise noted. The MN keyword is not otherwise noted. To make
the MN field human readable in

pciutils: change MN VPD keyword to F_TEXT

The PCI spec defines all keyword data fields as ASCII unless
otherwise noted. The MN keyword is not otherwise noted. To make
the MN field human readable in lspci verbose outputs, this patch
changes the MN keyword definition from F_BINARY to F_TEXT.

Signed-off-by: John Walthour <[email protected]>

show more ...

Improve the VPD fix to warn the user that VPD decoding was aborted.

Stop early if the VPD is corrupt

I have several cards which report more-or-less garbage in their VPD.
It can take an extraordinarily long time to read all their VPD and none
of it is of interest. I

Stop early if the VPD is corrupt

I have several cards which report more-or-less garbage in their VPD.
It can take an extraordinarily long time to read all their VPD and none
of it is of interest. Instead, if we find an unknown resource type,
just stop trying to read any more.

Signed-off-by: Matthew Wilcox <[email protected]>

show more ...

lspci: Print vendor-/system-specific VPD item ids correctly

Vendor- and system-specific VPD items are matched only by their first
character, so we cannot read the item id from the matching structure

lspci: Print vendor-/system-specific VPD item ids correctly

Vendor- and system-specific VPD items are matched only by their first
character, so we cannot read the item id from the matching structure.
There is a similar issue with unknown VPD items, which is handled by
creating a matching structure dynamically.

We can handle both cases using the static matching structure and the
actual item id, so do that.

Signed-off-by: Ben Hutchings <[email protected]>

show more ...

Ignore NUL character at the end of VPD strings.

Broadcom Ethernet controllers have been observed to use NUL-terminated strings.

Accompany VPD items with human-readable names.

Copyright is held by Solarflare, not Ben personally

(Changed at Ben's request.)

Decode VPD fully only with -vv or higher.

This brings the behavior in line with the other capabilities.

Split lspci to multiple source files.