https://bugzilla.kernel.org/show_bug.cgi?id=60829
--- Comment #6 from Aaron Lu <[email protected]> --- (In reply to Peter from comment #5) > NVIDIA has stated that they do not have specific logic to check ACPI handles > and rely on the OS to provide the correct ones. Good to know this. So it basically means Windows will pick the last ACPI handle for the same _ADR ACPI handles. > > It is possibly to work around shortcomings in the ACPI layer[1], but since > Windows works fine on these devices, the issue should be solved in the Linux > implementation of ACPI. Yes, Linux ACPI can do this to follow Windows' behavior. > > Would it make sense to pick the last detected Device? (guesswork) Vendors > may provide a generic DSDT and add SSDTs for more specific configurations. I think so if Windows has this behavior. My take for this problem is: from ACPI spec's point of view, there is no way for Linux ACPI to pick a handle when multiple handles have the same _ADR, but the specific driver has(like the way you did in Bumblebee by checking handle name of PEGP). But if Windows has a rule(how can we be sure of this?), it is worth to follow it. -- You are receiving this mail because: You are watching the assignee of the bug. ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk _______________________________________________ acpi-bugzilla mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
