On Mon, Jul 22, 2002 at 11:51:24AM -0700, David Brownell wrote: > >>So what else can go into driverfs ? > > I'd rather know what _should_ go into it ... :)
Device specific information. Driver specific information. Basically all the crap in /proc that doesn't deal with processes :) > Well, it wouldn't be visible through driverfs but the power > management hooks need to start happening. Individual USB > device drivers need some sort of suspend/resume callback, > and if they don't provide one (or if the hub driver notices > its subtree can't properly suspend), it should morph into > a disconnect()... power management is on the list, but it's _very_ doubtful it will make it into 2.5 due to the long list of things that has to happen first. 2.7 is a good goal for it :) > I suspect that device and config descriptors shouldn't appear, > although there might be an argument for them (useful, and we > already have a text format). I could see exporting this information if people found it useful. Personally I like the way /proc/bus/usb/devices looks, but I'm used to it... thanks, greg k-h ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
