On Fri, Aug 03, 2007 at 07:01:11AM -0700, David Brownell wrote: > Which is, as I pointed out, the wrong response. Desktoppy > people should be making their tools do more intelligent things > with new USB devices they see ... like updating databases of > broken devices, and configuring *this* system to know that of > the devices it regularly deals with, this handful is broken.
Popping up a box saying "Is your device broken?" isn't good UI. > > But while this is still a likely probability, the chances are no > > distribution is going to ship with CONFIG_USB_SUSPEND enabled. > > So you're saying all the distros want to make PM problems worse? No. But given a choice between working hardware or marginally better runtime PM, they're going to choose working hardware. > And that with all the other desktoppy stuff they're doing, not one > of them is willing to help make things better? This patch is exactly that - a way of getting most of the benefits of autosuspend without any real probability of breaking hardware. If you mean "Are the distributions willing to pop up dialogs asking users to start caring about obscure aspects of the USB spec", then I don't think that's actually making things better. > Pardon me if I want to hear distro vendors agree with you before I > believe that. I'm speaking as part of the Ubuntu kernel team, and I've been discussing this with Fedora people. > > > Breaking > > people's hardware (even if, at a fundamental level, it's the hardware > > that's broken) generally irritates users - and I suspect that the users > > it'll irritate the most are the ones who won't report it to LKML. > > Having a laptop drain its battery an hour before it needs to is > also irritating. (As are the extortionate prices for each model's > unique batteries, but that's a different issue.) You commonly run a laptop off battery while having a printer plugged in? -- Matthew Garrett | [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
