http://bugzilla.kernel.org/show_bug.cgi?id=5989
------- Additional Comments From [EMAIL PROTECTED] 2006-04-03 16:09 -------
> But, the key point is we assume Windows work, and we expect linux work too.
I just saw the documentation on acpi_os_name:
commit a1f9e65e2085e0a87f28a4d5a8ae43b32c087f24
Author: Len Brown <[EMAIL PROTECTED]>
Date: Wed Jan 25 23:47:36 2006 -0500
[ACPI] document cmdline acpi_os_name=
So I used it to simulate Windows code paths. I tested the vanilla
2.6.16-rc5 kernel with the BIOS DSDT, using
acpi_os_name="Microsoft Windows" acpi_serialize
It hung on the second sleep, as usual (and the same hang if I didn't
use acpi_serialize).
So then I wondered whether this BIOS works with Windows at all. But
it has to. What else could IBM have tested it with? So Windows must
do something smart during the suspend, like disabling the EC updates
or like the other hacks that we've been trying.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
