> Do you have the failed DSDT table dumped? Even there's recent change around > NVSA, but looks that's different.
Here is the DSDT before any of my changes: https://0paste.com/158902 > Do you see any ways to preempt this entire class of errors (Windows > unhappy with ACPI tables) within coreboot in a systematic manner? I wrote a pretty hack ASL parser so I could verify the UID. We could add some kind of DSDT sanity check build step. Though it won't catch any SSDT errors since those are generated at run time. I think the best thing is to add more checks to fwts. I submitted a bug for the _UID issue here: https://bugs.launchpad.net/fwts/+bug/1912532 We could additionally add another test to FWTS to catch error code 0x1000D. It looks like FWTS also supports processing ACPI tables: https://wiki.ubuntu.com/FirmwareTestSuite/Reference#Processing_pre-dumped_data So maybe adding FWTS to the coreboot toolchain and add a Kconfig to sanity check the DSDT isn't a bad idea? _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
