On 22 October 2015 at 18:00, Greg KH wrote:
> On Thu, Oct 22, 2015 at 05:15:50PM +0100, John Tapsell wrote:
>> On 15 October 2015 at 15:37, Alan Stern wrote:
>> > On Thu, 15 Oct 2015, John Tapsell wrote:
>> >
>> >> I did have one wacky idea. I'm sure
On 15 October 2015 at 15:37, Alan Stern wrote:
> On Thu, 15 Oct 2015, John Tapsell wrote:
>
>> I did have one wacky idea. I'm sure it's stupid, but here it is: Is
>> it at all possible that there's a bug in the linux usb code where a
>> bInterval value of
On 15 October 2015 at 15:37, Alan Stern wrote:
> On Thu, 15 Oct 2015, John Tapsell wrote:
>
>> I did have one wacky idea. I'm sure it's stupid, but here it is: Is
>> it at all possible that there's a bug in the linux usb code where a
>> bInterval value of
On 15 October 2015 at 15:00, Greg KH wrote:
> A: No.
> Q: Should I include quotations after my reply?
>
> http://daringfireball.net/2007/07/on_top
>
> On Thu, Oct 15, 2015 at 02:56:48PM +0100, John Tapsell wrote:
>> Hi Greg,
>>
>> I'm trying to write a
like to do better if
it at all possible.
Any suggestions?
Thanks,
John
On 15 October 2015 at 14:46, Greg KH wrote:
> On Thu, Oct 15, 2015 at 12:05:52PM +0100, John Tapsell wrote:
>> Hi,
>>
>> I'm working on a linux driver for a usb to i2c chip (the MCP2221).
>> The U
flag;
}
ll_exit_clear_flag:
dev->ongoing_usb_ll_op = 0;
return rv;
}
(Please let me know what information to provide. I have oscilloscope
outputs, lsusb outputs, more information about mcp2221, etc. I just
didn't want to make this a huge dump of irrelevant information)
