https://bugzilla.kernel.org/show_bug.cgi?id=204251
Zhang Rui (rui.zh...@intel.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rui.zh...@intel.com
--- Comment #24 from Zhang Rui (rui.zh...@intel.com) ---
acpiexec dsdt.dat:
- find BRT6
\_SB.PCI0.GFX0.BRT6 Method 0x55e9480d0200 001 Args 2 Len
001A Aml 0x7f26bbc23cd9
\_SB.PCI0.PEG0.PEGP.BRT6 Method 0x55e9480d2640 001 Args 2 Len
0022 Aml 0x7f26bbc2401b
- find LCD
\_SB.PCI0.GFX0.LCD Device 0x55e9480cdf50 001
so we have two BRT6 method, they share similar code.
it is okay for \_SB.PCI0.GFX0.BRT6 to use relative path LCD, but it is not okay
for
\_SB.PCI0.PEG0.PEGP.BRT6 to do so.
Method (BRT6, 2, NotSerialized)
{
If ((EVD5 == One))
{
If ((Arg0 == One))
{
Notify (LCD, 0x86) // Device-Specific
}
If ((Arg0 & 0x02))
{
Notify (LCD, 0x87) // Device-Specific
}
}
}
I guess the ACPI errors will go away if we replace LCD with \_SB.PCI0.GFX0.LCD.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
