lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0706191134160.12843@utopia.booyaka.com>
Date:	Tue, 19 Jun 2007 11:36:53 -0600 (MDT)
From:	Paul Walmsley <paul@...yaka.com>
To:	Oliver Neukum <oliver@...kum.org>
cc:	linux-usb-devel@...ts.sourceforge.net,
	Chuck Ebbert <cebbert@...hat.com>,
	"Renato S. Yamane" <renatoyamane@...dic.com.br>,
	linux-kernel@...r.kernel.org
Subject: Re: [linux-usb-devel] Error -71 on device descriptor read/all

On Tue, 19 Jun 2007, Oliver Neukum wrote:

> Am Dienstag, 19. Juni 2007 schrieb Chuck Ebbert:
>
>> Try disabling CONFIG_USB_SUSPEND
>>
>> [usb developers: what are the drawbacks of doing this?]
>
> Increased power consumption.

speaking of CONFIG_USB_SUSPEND, I've encountered at least one device -- a 
Canon EOS 5D camera -- that, after the bus suspends, must be powercycled 
in order to return the camera's interrupt endpoints to a functional state. 
How are these types of problems handled, currently?  Is this something for 
a blacklist?


- Paul
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ