On Thu February 14 2008, Victor Lowther wrote: > Right, I do not see where in the HAL source code that is determined. I > can see the quirks in > > hal-info/fdi/information/10freedesktop/20-video-quirk-pm-dell.fdi > > and follow the invocation chain back to hal/tools/hal-system-power-suspend > but I cannot see where that tool is invoked from or (more critically) > how the HAL_PROP_POWER_MANAGEMENT_QUIRK family of environment variables > are created from the descriptions in the hal-info quirks files. > > Am I missing something obvious in the hal source code?
Hal is pretty generic about how to generate the environment variables, e.g. every property is translated into HAL_PROP_ variables[1] and the possible method calls are also configured via fdi files, e.g. fdi/policy/10osvendor/10-power-mgmt-policy.fdi seems to contain the mapping from dbus methods to the scripts for power management, e.g. here it is defined that hal-system-power-suspend should be called for the respective dbus method. And in this special case, the quirks are properties in the power_management namespace which can be set with conditionally with match tags that are described here: http://people.freedesktop.org/~david/hal-spec/hal-spec.html#fdi-matching I hope this helps you already, I do not know where in the source code all the fdi files are evaluated, my knowledge comes basically from browsing through the hal-spec and grepping around in the source code. Regards, Till [1] http://people.freedesktop.org/~david/hal-spec/hal-spec.html#device-properties-info-method-calls
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Pm-utils mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/pm-utils
