On Mon, Oct 04, 2010 at 02:33:52PM +0100, Toby Gray wrote:
> Yeah. As quite a lot of this is timing dependent I was a bit fearful
> that even though all the machines I've tested on are fine with the
> current code, there might still sometimes be a need to call
> usb_set_altinterface(). I've made
On 01/10/2010 23:25, Chris Frey wrote:
> On Fri, Oct 01, 2010 at 05:14:04PM +0100, Toby Gray wrote:
>> Yes. Sorry, I missed out that rather essential bit of information :)
>> Option #4 fixes both the time out issue on some machines (which was
>> previously fixed by SET INTERFACE) and the usb-stor
On Fri, Oct 01, 2010 at 05:14:04PM +0100, Toby Gray wrote:
> Yes. Sorry, I missed out that rather essential bit of information :)
> Option #4 fixes both the time out issue on some machines (which was
> previously fixed by SET INTERFACE) and the usb-storage issue (which is
> caused by SET INTERFA
On 01/10/2010 03:31, Chris Frey wrote:
> On Thu, Sep 30, 2010 at 02:16:32PM +0100, Toby Gray wrote:
>> 2) Change the probing code in src/probe.cc so that it tries probing the
>> end points without a call to SET INTERFACE and then, if those probes
>> fail, calls SET INTERFACE and probes again. I t
On Thu, Sep 30, 2010 at 02:16:32PM +0100, Toby Gray wrote:
> 2) Change the probing code in src/probe.cc so that it tries probing the
> end points without a call to SET INTERFACE and then, if those probes
> fail, calls SET INTERFACE and probes again. I think it's probably best
> to probe all the
On 22/09/2010 11:36, Toby Gray wrote:
>On 21/09/2010 23:01, Chris Frey wrote:
>> On Tue, Sep 21, 2010 at 12:12:57PM +0100, Toby Gray wrote:
>>> However there's clearly a reason for the call to usb_set_altinterface,
>>> so can anyone remember what devices it was necessary for?
>> It wasn't a s
On 21/09/2010 23:01, Chris Frey wrote:
> On Tue, Sep 21, 2010 at 12:12:57PM +0100, Toby Gray wrote:
>> However there's clearly a reason for the call to usb_set_altinterface,
>> so can anyone remember what devices it was necessary for?
> It wasn't a specific device, it was all devices, I believe.
On Tue, Sep 21, 2010 at 12:12:57PM +0100, Toby Gray wrote:
> However there's clearly a reason for the call to usb_set_altinterface,
> so can anyone remember what devices it was necessary for?
It wasn't a specific device, it was all devices, I believe. It was to work
around a change in the kernel
Hi,
As has been mentioned previously, I'm trying to track down why doing USB
mass storage operations while Barry is running will lead to bad things
happening such as USB port getting reset, device rebooting.
After weeks of assuming it was down to the various differences in how
the usb-stora
