Hi!
> Well, partially; but it's not used consistently. Could you
> (or someone) explain what the plan is? I see:
>
> - Three separate x86 PM "initiators": APM, ACPI, swsusp.
> (Plus ones for ARM and MIPS.)
>
> - Two driver registration infrastructures, the driver model
> stuff and the older pm_*() stuff.
>
> The pm_*() is how a handful of sound drivers and other random
> stuff register themselves -- and how PCI does it.
>
> I'd sure have expected PCI to only use the driver model stuff,
> and I'll hope all those users will all be phased out by the
> time that 2.6 gets near the end of its test cycle.
>
>
> The "initiators" all talk to _both_ infrastructures, but they
> don't talk to the driver model stuff in the same way. For
> example, on suspend:
>
> - ACPI issues a NOTIFY, which can veto the suspend;
> then SAVE_STATE, ditto; finally POWER_DOWN.
>
> - APM uses the pm_*() calls for a vetoable check,
> never issues SAVE_STATE, then goes POWER_DOWN.
>
> - While swsusp is more like ACPI except that it doesn't
> support vetoing from either NOTIFY or SAVE_STATE.
Where does acpi call pm_*()? It seems like it does not and it seems
like a bug to me.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
