Closed forderud closed 3 months ago
Hi! Sorry for the late reply.
Thanks for letting us know. We've been working in fixing this issue for all samples on the develop
branch. After the latest kit is released, the changes will be migrated to main
. You can use the develop
branch version of the drivers if you want to get rid of this warning. However, many of the samples require the usage of the preview version of the WDK to build properly, so be aware of that.
Thanks a lot for taking polishing the sample drivers @NeoAdonis so that external developers like me gets a cleaner starting point for driver developments.
By the way, what's the contribution policy for this repo? I've over the past year tried to submit some PR's for addressing various issues with the sample drivers. However, there doesn't seem to be anyone from Microsoft responding. Is there something I can do from my end to get review feedback to my suggestions?
simple just write in the ,inf file
[Version] Signature="$WINDOWS NT$" Class=YOUR_CLASS_NAME ClassGuid=YOUR_CLASS_GUID Provider=%ProviderName% CatalogFile=YOUR_CATALOG_FILE_NAME DriverVer=YOUR_DRIVER_VERSION PnpLockdown=1 <<----------- THIS
Thanks for fixing this. I hereby confirm that the reported PnpLockdown
warning appear to have been fixed by f20a01318ddb570731de91f62e94b37550139b28.
I'm experiencing the following warning when building the
simbatt
sample:Maybe the INF files can be updated accordingly to resolve the warning?