| |||||||||||||
Wakelocks and the embedded problemWakelocks and the embedded problemPosted Feb 11, 2009 15:53 UTC (Wed) by knan (subscriber, #3940)In reply to: Wakelocks and the embedded problem by Kluge Parent article: Wakelocks and the embedded problem
"In use by some other piece of code" is the usual criteria. I.e. a driver using your added shared infrastructure, a userspace program talking to the interface added, etc.
The actual hardware being more than dreams in a simulator also helps, of course.
(Log in to post comments)
Wakelocks and the embedded problem Posted Feb 14, 2009 0:34 UTC (Sat) by giraffedata (subscriber, #1954) [Link] I can remember various LWN articles about some proposed feature where kernel developers argued that it needed to be used out of tree and shipped with distributions for a while to prove its worthiness before joining the kernel.org major league. I believe these were major functions, though.
|
|||||||||||||