JDelekto
Regular
They did not include a Windows driver (signed or not) in the SDK for the PCIe card, and one was not detected and installed after I had installed the card and booted Windows.All above my paygrade, but here is the low down on WHQL:
https://www.intel.com/content/www/us/en/support/articles/000093158/graphics.html
There are two types of drivers listed on the Download Center: drivers with and without a WHQL Certification. What are the differences between the two?
Resolution
Drivers labeled as WHQL Certified have been thoroughly tested by Intel, have passed Windows Hardware Lab Kit testing on various platforms and configurations, and are signed by Microsoft as compatible with Windows* operating systems.
Drivers that do not have WHQL Certification are also thoroughly tested by Intel, are of the same functional quality as WHQL Certified drivers, and are signed by Microsoft. The key difference is that Non-WHQL drivers have not completed the full Windows Hardware Lab Kit testing prior to release. This is known as an attest-signed driver.
... but this may only apply to things available from the Intel download centre.
When I get the M.2 card, I'll try installing it on the shuttle PC and setting up a new Windows 11 SSD to see if it will detect it. To run this on Windows, I think I will need to finish porting the PCIe driver, then probably also port their C++ library to use low-level Windows APIs to communicate with the driver.
When that is done, a wrapper for their Engine can be used with other higher-level languages. While I understand the idea is to target Edge devices for Akida, I would still like to work with a more familiar development environment.
Of course, maybe they'll read this message and have someone work on it internally.