> On Sep 3, 2015, at 10:59 AM, Bill Paul <[email protected]> wrote: > >> I've worked through some firmware issues on older MS releases, but never >> Windows 8 or 10. So this advice may be out of date. Do you know if >> Windows got through the boot loader and is starting the kernel? If so, >> you can turn on extra debug messages to show the drivers as they are >> loading. That can give you some good clues. If that's not enough, you >> can enable remote debugging and use MS's debuggers (eg. WinDbg) and >> symbol tables to get an idea of the call chain which is failing. It's >> been a long time since I've done this, so I'm rusty on the specifics... >> searching on msdn.microsoft.com <http://msdn.microsoft.com/> should get you >> going. >> >> Historically, Windows has been extremely picky about ACPI tables, much >> more so than Linux. > > No: historically hardware vendors have been insufficiently picky about > creating their ACPI tables, leading to what I have not-so-affectionately > named > the "If It Works With Windows, It Must Be Okay" syndrome.
This issue even finds its way into hardware. I’ve seen USB device that violate the USB spec, but they work with the Windows driver, so ship it. Thanks, Andrew Fish _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
