Windows-driver-samples

Linux: lsusb -tv Windows: There's an example in the WDK here: https://github.com/Microsoft/Windows-driver-samples/tree/mai...

Some parts have already been open-sourced. For example, the console host component has been open sourced here: https://github.com/microsoft/terminal And the FAT filesystem driver: https://github.com/microsoft/Windows-driver-samples/tree/mai... And also PowerShell: https://github.com/PowerShell/PowerShell And most of .NET: https://github.com/dotnet Maybe they could consider an Apple-style approach: open source the core of the kernel and text-mode user space but leave the GUI closed. Of course, open sourcing everything would be even better, but that might too big of a step for them. Open sourcing the non-GUI core could be a good initial step, whether or not it ends up going further.

https://learn.microsoft.com/en-us/windows-hardware/drivers/d... https://learn.microsoft.com/en-us/windows-hardware/drivers/o... https://github.com/microsoft/Windows-driver-samples

The state machine example is definitely a very fitting use of goto, but it reminds me of another thing that seems to have become a rare skill but is very useful: flowcharting. Besides making people comfortable with goto in general, it also helps visualise control flow in ways that a lot of programmers these days don't realise, and it's unfortunate that a lot of courses seem to have omitted its teaching. Also worth reading is "GOTO Considered Harmful Considered Harmful": https://news.ycombinator.com/item?id=11056434 And here Microsoft provides us with lovely example of such ridiculous nesting. That's a very memorable example, but ultimately the true cause of that monstrosity is a clearly stupid API design; this is the API for a file picker, the recommended replacement for an existing one that they wanted to deprecate. In the existing one,

> Is this something you have to sign an NDA with Microsoft to get access to the headers and docs for it? Or will I find the headers hidden away in the WDK somewhere? Turns out the header file is included in the Windows 10 SDK, as km/nthalext.h Not the very latest version, but someone posted it on GitHub here: https://github.com/tpn/winsdk-10/blob/master/Include/10.0.16... (You can download the multi-gigabyte Windows 10/11/2022 SDKs to get a more recent one, although not sure if anything has changed.) Still doesn't seem to be any public documentation. The header includes very detailed comments, but (as you'd expect for header file comments) they concentrate on the nitty-gritty and omit the big picture. Searching "nthalext.h" on GitHub finds source code for a handful of HAL extensions, so at least there is some sample code to look at. Micro

Well yes. But Linus is right on that one. I wouldn't say Windows drivers were C++, more like "C with Classes" (and maybe a little bit C++) Also, Windows drivers are usually much more convoluted than Linux drivers https://github.com/microsoft/Windows-driver-samples

Linux is the kernel, so really the equivalent on Windows is the Windows kernel API, not the Win32 (user) API. However, the kernel API seems to be somewhat similar to the Win32 version presented in the talk and not nearly as gnarly as the Linux equivalent: https://github.com/microsoft/Windows-driver-samples/blob/mas... https://docs.microsoft.com/en-us/windows-hardware/drivers/dd... That said I'm just an application programmer so I've only ever used the Win32 API.

That loop is totally fine. I wrote it many times in C#, C and C++, and I saw it many more times in other people’s code. Microsoft DDK sample: https://github.com/Microsoft/Windows-driver-samples/blob/mas... Microsoft MediaFoundation sample: https://github.com/Microsoft/Windows-classic-samples/blob/ma... OpenSSL: https://github.com/openssl/openssl/blob/master/crypto/sha/sh... And many others. Just because code looks unfamiliar doesn’t mean it’s something wrong with the code.

I meant it's written in C++[0]. The interface is exported through standard C functions, but the header files also have the declarations guarded with "extern "C"". Microsoft do have some sample drivers that are written in C++, e.g. https://github.com/Microsoft/Windows-driver-samples/tree/mas... [0]: https://github.com/Microsoft/Windows-Driver-Frameworks/tree/...

I too have been finding it hard to find a single reliable and up-to-date source for learning windows drivers. There's a plethora of info online, but lots is out of date and/or scattered and redundant. Even decent paid training is hard to find, at least in my part of the world. There's a book, but it's old [1] There's samples, which are fresh [2] There's a multi part series on Code Project, but it's old (yet much of it still applies conceptually; samples not so much) Part 1 of 6: [3] If anybody has a good one-stop-shop and updated source of learning I'd very much appreciate it (I'd love a nicely written book on the matter that's not older than, say, 3 years old) [1]: http://www.amazon.com/Developing-Drivers-Foundation-Develope... [2]: https://github.com/Microsoft/Windows-driver-samples [3]: http://www.codeproject.com/Articles/9504/Driver-D