PCI: Migrate from BSF to BDF convention #220
Comments
jaypipes
added a commit
that referenced
this issue
May 20, 2021
As noted by @pearsonk in #220, the PCIAddress.Slot field was a bit of a misnomer, since the more common representation of a PCIAddress is Bus:Device.Function, not Bus:Slot.Function. Actual PCI slot information may be retrieved from DMI, but what we were referring to was not the actual PCI slot information but rather the PCI address device component. Fixes Issue #220
jaypipes
added a commit
that referenced
this issue
May 25, 2021
As noted by @pearsonk in #220, the PCIAddress.Slot field was a bit of a misnomer, since the more common representation of a PCIAddress is Bus:Device.Function, not Bus:Slot.Function. Actual PCI slot information may be retrieved from DMI, but what we were referring to was not the actual PCI slot information but rather the PCI address device component. Fixes Issue #220
|
fixed by #252 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Slot designation is a bit of a misnomer when referring to the addressing field, which is conventionally called Device in Domain:Bus:Device.Function notations.
Further, as it seems relevant, actual slot information can be pulled from DMI (type 9) with a lookup of the Designation for a matching Bus Address for the first Function of the device. Absence of a DMI entry would signify an internal PCI device not connected to an expansion slot.
The text was updated successfully, but these errors were encountered: