-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WDI Sample] Refactoring Platform File IO ops to use WDM calls #1142
[WDI Sample] Refactoring Platform File IO ops to use WDM calls #1142
Conversation
This PR is into main branch. That branch is closed. Please stage PR to develop branch. |
a7bb7e3
to
368b9fd
Compare
cc72c4f
to
7567118
Compare
For some reason the automated gates didn't trigger. Weird... I'll check if this is an issue with the actions themselves or something in the PR. I'll approve after checking manually that the sample builds successfully. Keep pursuing review from the Wi-Fi core team, please! |
@NeoAdonis . I also was surprised the gates did not work. I would be curious to learn why this is. |
Ok @JakobL-MSFT, @NeoAdonis , UU just approved from the Wifi Core team. We can merge now. |
Why is this change being made?
The current implementation of the WDI driver example uses calls to deprecated NDIS functions:
NdisOpenFile
,NdisMapFile
,NdisUnmapFile
,NdisCloseFile
.NDIS have deprecated the use of this functions and stick to only network-related operations which left this file operations not available for ARM64 architecture. Due to the current efforts to support ARM64, we need to refactor pieces of code within this driver to avoid the use of the deprecated NDIS calls such that we have a buildable driver for both x86_64 and ARM64.
What changed?
Refactored
PlatformReadFile
,PlatformOpenFile
,PlatformMapFile
,PlatformUnMapFile
,PlatformCloseFile
and `PlatformReadAndMapFile, to use the WDM calls for file operations and memory operations. This PR is the first step to enable the ARM64 support for this driver.