On Tuesday 27 February 2007 10:47 am, Alan Stern wrote: > On Mon, 26 Feb 2007, Oliver Neukum wrote:
> The main reason for deprecating power/state was that it did not have the > necessary expressive power. Different buses have different sets of power > states and requirements (sometimes individual devices do too), but > power/state only allowed for 0, 1, 2, or 3. It had a few more design botches than that, actually. > The user has the ability to enable or disable remote wakeup through the > power/wakeup attribute. Suppose for some reason the user has decided to > disable remote wakeup -- maybe because he really wants the device to > remain suspended. Or because remote wakeup really doesn't work from that device, so that autosuspend may only kick in if it's known the device is unused (vs just temporarily idle). > > > WE ALWAYS WAKE UP ON DEMAND! > > > > Why? Repeating the assertion doesn't make it any more logical. > > What's illogical about always waking up on demand? Nothing at all -- right Oliver? ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
