|
Should IDPF be registered as new Programming Interface under PCI SIG
As we are learning our ways to make things as generic interfaces, the proposal on the table is to register a new PCI SIG Programming interface under
PCIE class : Network Controller (02h)
subclass : Ethernet Controller (00h)
Programming Interface : Ethernet Controller with IDPF
compliant Interface (01h) ----> NEW
This is similar to NVMe which is a Storage-Programming Interface. What this will allow us is to have the driver be loaded just based on Programming Interface identification, and we wouldn't need a generic Vendor ID for this device that Every vendor needs to put in their HW. An Emulated IDPF device will still have a Vendor ID such as "Redhat"
If a Vendor chooses to add a Vendor ID + Device ID identification tuple in the IDPF driver, they can still do that for reasons such as Quirks or any other reason.
|
