Am Montag, 15. Januar 2007 17:03 schrieb Alan Stern:
> On Mon, 15 Jan 2007, Oliver Neukum wrote:
> > Upon further thought, a module parameter won't do as the problem
> > will arise without a driver loaded. A sysfs parameter turns the whole
> > affair into a race condition. Will you set the guard parameter before the
> > autosuspend logic strikes?
> > Unfortunately this leaves only the least attractive solution.
>
> There could be a mixed approach: a builtin blacklist that is extensible
> via a procfs- or sysfs-based interface.
If you want to ask with a lot of bug reports which blacklist was loaded,
then we could.
> Note that we actually have two problems to contend with. Some devices
> must never be autosuspended at all (they disconnect when resuming), and
> others need a reset after resuming.
Do those who can be brought back with a reset need to be listed at all?
Error handling is not a bad idea.
Regards
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
