Claiming a PCI device by class code

NTDEV
1

Hi,

In the INF for my driver I am claiming a PCI device by class code. It works fine but WHQL throws the error:
?DriverPackage C:\Windows\Inf\oem1.inf has a Hardware Id or a Compatible Id that begins with pci\cc_?

Does this mean that third party vendors cannot claim a PCI device by class code and they need to claim it only using VID/DID?

Regards,
Suresh

2

Correct.

Sent from my Windows 10 phone

From: xxxxx@yahoo.commailto:xxxxx
Sent: Monday, February 22, 2016 3:07 AM
To: Windows System Software Devs Interest Listmailto:xxxxx
Subject: [ntdev] Claiming a PCI device by class code

Hi,

In the INF for my driver I am claiming a PCI device by class code. It works fine but WHQL throws the error:
?DriverPackage C:\Windows\Inf\oem1.inf has a Hardware Id or a Compatible Id that begins with pci\cc_?

Does this mean that third party vendors cannot claim a PCI device by class code and they need to claim it only using VID/DID?

Regards,
Suresh

—
NTDEV is sponsored by OSR

Visit the list online at: https:

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at https:

To unsubscribe, visit the List Server section of OSR Online at https:</https:></https:></https:></mailto:xxxxx></mailto:xxxxx>

3

Thanks Doron. I am sure this must be documented somewhere too, but I can’t find it. Could you please provide a link to such limitation documented?

I am actually toying around with NVMe driver developed by OFA (http://www.nvmexpress.org/blog/open-fabrics-alliance-nvm-express-window-driver-1-4-released-december-8-2014/)
Surprisingly the driver is supposed to be WHQL compliant where the INF file claims it by class code only. I am not sure where the disconnect is.

Regards,
Suresh

4

Signed Class drivers are limited to first party, I don?t know where that is documented

Sent from my Windows 10 phone

From: xxxxx@yahoo.commailto:xxxxx
Sent: Monday, February 22, 2016 6:33 AM
To: Windows System Software Devs Interest Listmailto:xxxxx
Subject: RE:[ntdev] Claiming a PCI device by class code

Thanks Doron. I am sure this must be documented somewhere too, but I can’t find it. Could you please provide a link to such limitation documented?

I am actually toying around with NVMe driver developed by OFA (https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.nvmexpress.org%2Fblog%2Fopen-fabrics-alliance-nvm-express-window-driver-1-4-released-december-8-2014%2F&amp;data=01|01|Doron.Holan%40microsoft.com|aab47ed2180a4cec35cf08d33b952af7|72f988bf86f141af91ab2d7cd011db47|1&amp;sdata=%2BmuQ0UCRyVn5Tkz9FhOihorKdcg4jY0b%2BKWJgRvy0ZM%3D)
Surprisingly the driver is supposed to be WHQL compliant where the INF file claims it by class code only. I am not sure where the disconnect is.

Regards,
Suresh

—
NTDEV is sponsored by OSR

Visit the list online at: https:

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at https:

To unsubscribe, visit the List Server section of OSR Online at https:</https:></https:></https:></mailto:xxxxx></mailto:xxxxx>

5

Found this link:
“INF Requirements for PCI Devices”
https://msdn.microsoft.com/en-us/library/windows/hardware/dn653567(v=vs.85).aspx

According to it either VID/DID or VID/DID/SID/SVID is allowed to be used for PCI devices. Using only VID/DID seems to be more restrictive and latter is more recommended.
I guess you were referring to same requirement. This however appears to be quite dated.

Thanks,
Suresh

6

The doc is dated because the policy has been in place for a long time. It still applies

Sent from my Windows 10 phone

From: xxxxx@yahoo.commailto:xxxxx
Sent: Monday, February 22, 2016 6:31 PM
To: Windows System Software Devs Interest Listmailto:xxxxx
Subject: RE:[ntdev] Claiming a PCI device by class code

Found this link:
“INF Requirements for PCI Devices”
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmsdn.microsoft.com%2Fen-us%2Flibrary%2Fwindows%2Fhardware%2Fdn653567(v%3Dvs.85).aspx&amp;data=01|01|Doron.Holan%40microsoft.com|dad6c2b620044c79c24108d33bf97f41|72f988bf86f141af91ab2d7cd011db47|1&amp;sdata=YVkZ6j8SIISrDumgnXXf9rLGb16U6EE%2BJPjbsh6JxWc%3D

According to it either VID/DID or VID/DID/SID/SVID is allowed to be used for PCI devices. Using only VID/DID seems to be more restrictive and latter is more recommended.
I guess you were referring to same requirement. This however appears to be quite dated.

Thanks,
Suresh

—
NTDEV is sponsored by OSR

Visit the list online at: https:

MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at https:

To unsubscribe, visit the List Server section of OSR Online at https:</https:></https:></https:></mailto:xxxxx></mailto:xxxxx>