forked from acpica/acpica
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Parser: Avoid resolving in-package references
This patch changes PackageElement parsing according to the validated Windows behavior. It seems Windows always converts NameString in Package into String, so that when an OSPM driver call invokes it later, forward references can be allowed. Note, OSPMs like Linux having drivers invoking ACPICA APIs should still rely on the old ACPICA behaviors where NameString is resolved into ObjectReference for the external users. While this commit doesn't ensure such compatibility, thus functional changes in this commit is not directly enabled but is surrounded by AcpiGbl_ParseTableAsTermList so that after having done all necessary changes, it can be enabled along with the new MLC enabling. Reported by Peter Wu, Fixed by Lv Zheng. Link: https://bugs.acpica.org/show_bug.cgi?id=1333 Link: Bumblebee-Project/bbswitch#142 Reported-by: Peter Wu <peter@lekensteyn.nl> Tested-by: Peter Wu <peter@lekensteyn.nl> Tested-by: Bartosz Skrzypczak <Barteks2x@gmail.com> Signed-off-by: Lv Zheng <lv.zheng@intel.com>
- Loading branch information
Lv Zheng
committed
May 4, 2017
1 parent
49f041a
commit ce24b4d
Showing
4 changed files
with
108 additions
and
45 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters