On Thu, Aug 02, 2007 at 11:01:08PM -0700, David Brownell wrote: > Seems to me it ought to be practical to organize a database that can > be consulted by an outcall from udev, disabling autosuspend on devices > which are known to be broken. The "modules.usbmap" syntax is an obvious > place to start (painful though it is), and I'm sure there are folk who > would prefer web-accessible/updatable databases.
It's certainly possible to do that, but it's also possible to have a userspace solution that whitelists devices. The question is whether the default kernel behaviour should be "Save power, but potentially break some of my devices" or "Don't break my devices, but use some more powre". -- Matthew Garrett | [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
