Ted
As a PS to the previous email the situation has I think more choices than
you portray.
Given the need for various constraints imposed by drivers for things like
RT it's entirely possible that a solution ends up being something like
Kernel proper:
Turn suspend block kernel API into an expression of constraints (or
whatever else seems to work)
Throw the user space in the bin
Google:
Use the constraints in a sledgehammer manner (hey it solves your problem
in that form so why not)
Patch in a private user space API
That makes things much much easier as we don't risk getting a horribly
broken API into the kernel that is hard to remove, while hopefully
meaning its rather easier for google to merge drivers and other code as
well as to maintain a smaller patch set.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
