[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200708031808.11903.oliver@neukum.org>
Date: Fri, 3 Aug 2007 18:08:11 +0200
From: Oliver Neukum <oliver@...kum.org>
To: Matthew Garrett <mjg59@...f.ucam.org>
Cc: David Brownell <david-b@...bell.net>,
linux-usb-devel@...ts.sourceforge.net, Greg KH <gregkh@...e.de>,
Rogan Dawes <lists@...es.za.net>, linux-kernel@...r.kernel.org,
Alan Stern <stern@...land.harvard.edu>
Subject: Re: [linux-usb-devel] [PATCH] USB: Only enable autosuspend by default on certain device classes
Am Freitag 03 August 2007 schrieb Matthew Garrett:
> > Which is why I didn't suggest doing that, of course. The only
> > one making that kind of straw man argument seems to be you.
>
> But however you phrase it, that's effectively what it is. "Does your
> device work?" just makes users wonder why the damn computer doesn't know
> already. "This option may prevent your device from working. Click here
> to switch it off" results in them wondering why it was switched on in
> the first place. Many of our users aren't technical - they don't care
> about saving 200mW, they just care about their printer working when they
> plug it in.
Devices rarely simply crash. Although Windows doesn't do runtime power
management, it certainly will suspend all devices when the system goes
into suspension. Buggy devices typically disconnect and reconnect when
resumed. This is testable for in software without user intervention.
Regards
Oliver
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists