[nvmewin] WHQL limitation of class code

[Foster, Carolyn D]

Hi Suresh,
It seems likely that Microsoft doesn't allow 3rd party vendors to sign drivers that target a class code instead of a vendor and device ID.  But unfortunately I can't find any documentation that provides confirmation.   Originally the goal for the certification task was to verify that the certification tests ran successfully on the OFA NVMe driver and not to actually certify the driver.  Likely, the INF file was either modified to include a specific device and vendor ID to run certification or the standalone executables were extracted and run individually.  

Carolyn

-----Original Message-----
From: nvmewin-bounces at lists.openfabrics.org [mailto:nvmewin-bounces at lists.openfabrics.org] On Behalf Of Suresh Patil
Sent: Monday, February 22, 2016 8:36 AM
To: nvmewin at lists.openfabrics.org
Subject: [nvmewin] WHQL limitation of class code

Hi,

I ran the WHQL and found that it is failing with the error:
"DriverPackage C:\Windows\Inf\oem1.inf has a Hardware Id or a Compatible Id that begins with pci\cc_"

It seems that third party vendors cannot have a signed class driver!
How come this issue was not encountered during WHQL testing here, or am I missing something?

Regards,
Suresh
_______________________________________________
nvmewin mailing list
nvmewin at lists.openfabrics.org
http://lists.openfabrics.org/mailman/listinfo/nvmewin