The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
I have an opportunity to write both an audio driver and several APO's, and would like to get some sage, seasoned advice. The vast majority of my drivers are written in KMDF ... for a variety of reasons, it's been my go-to springboard for drivers and I'd like for this audio driver to be no exception.
The driver is supposed to be getting audio data off a hardware tap from a digital microphone, and there is hardware to support this which then exposes a USB interface. I've reviewed the SYSVAD sample (written in WDM) in the WDK and have searched here and on StackOverflow for others who might be writing audio drivers ... everyone writing audio drivers seem to be using the SYSVAD sample as a starting point and moving from there, staying in WDM. The APO's appear to be pretty straightforward and there are good examples I've found of those.
The architecture is reasonably straightforward ... the bottom edge is communicating with a USB chipset for getting the audio data from a microphone, the top edge is exposing some pins and attributes ... is there an architectural reason why KMDF would be an unsuitable framework for an audio driver?
|Upcoming OSR Seminars|
|OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!|
|Writing WDF Drivers||7 Dec 2020||LIVE ONLINE|
|Internals & Software Drivers||25 Jan 2021||LIVE ONLINE|
|Developing Minifilters||8 March 2021||LIVE ONLINE|