On Mon, Aug 11, 2008 at 03:02:20PM +0800, Zhao Yakui wrote: > On Mon, 2008-08-11 at 08:45 +0200, Andi Kleen wrote: > > On Mon, Aug 11, 2008 at 02:55:05PM +0800, Zhao Yakui wrote: > > > Subject:ACPI: Get the device power state in the course of scanning device > > > From: Zhao Yakui <yakui.zhao@xxxxxxxxx> > > > > > > Get the device power state in the course of scanning device if the device > > > power flag is power_managable. i.e. The device has the _PSx/_PRx object. > > > > > > At the same time before the drivers/acpi/power module is loaded, there is no > > > relation between acpi_power_resource and acpi device. So the first parameter > > > of acpi_power_get_state is changed to acpi_handle. > > > > > > http://bugzilla.kernel.org/show_bug.cgi?id=8049 > > > http://bugzilla.kernel.org/show_bug.cgi?id=11000 > > > > Seems to be an pretty old bug. I assume it's not critical > > enough to require pushing into .27? > Yes. It is not critical. > But in fact windows can work well on such broken BIOS. In order to make Any guess how do they do that? Do they have a blacklist for this case? > Linux be compatible with this broken BIOS, it will be OK to merge them. The option is fine since it is off by default, but I'm a little scaried about the init sequence ordering for .27. That might break something. -Andi -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
