As Arjan suggested, trying to load the default modules right after the
initial rootfs mount could be an acceptable compromise and it would be
really nice (for both code sanity and avoiding future problems) to be
able to declare module loading nested inside async unspported.
we can even try twi
But no, it's not just some trivial one-liner. Especially the question
about "when to try to load the module that is given on the kernel
command line" is not trivial. Do we require that the module is in the
initrd and loadable basically immediate at boot? Do we try again after
switching the root
For now, I'm gonna implement simple "I'm not gonna wait for myself"
self-deadlock avoidance. If this needs any more sophistication, I
think we better reimplement it so that we can explicitly match up and
track who's gonna wait for what instead of throwing everything into a
single cookie space a
On 9/24/2012 12:13 AM, Alan Stern wrote:
> Therefore all we need is an API for individual devices, not for
> domains. Of course, userspace may want to know which devices all
> belong to the same power domain.
agreed on both.
I'd like PowerTOP to be able to report at least who keeps power alive a
On 9/23/2012 8:33 PM, Rafael J. Wysocki wrote:
> On Sunday, September 23, 2012, Peter Stuge wrote:
>> Rafael J. Wysocki wrote:
>>> Well, we actually need to handle power domains appropriately.
>> ..
>>> Some work in that direction has been done in the ARM space, where we have
>>> much more direct a
