hi all:
when I trace linux ehci driver source code.
I have some questions
1. in itd_slot_ok, why we have to
uframe %= period;
and use this uframe to calculate the bandwidth?
suppose start passed to itd_slot_ok is 537, period, usb->interval, is 8.
that mean we want to know whether bandwi
On 31 July 2013 15:14, Philipp Dreimann wrote:
> On Tue, Jul 30, 2013 at 9:28 PM, Alan Stern wrote:
>> On Tue, 30 Jul 2013, Sarah Sharp wrote:
>>
>>> On Tue, Jul 30, 2013 at 12:52:40PM -0400, Alan Stern wrote:
>>> > Sarah, the usbmon trace shows that after doing a successful port reset
>>> > and
On Sat, 7 Sep 2013, vichy wrote:
> hi all:
> when I trace linux ehci driver source code.
> I have some questions
> 1. in itd_slot_ok, why we have to
> uframe %= period;
> and use this uframe to calculate the bandwidth?
>
> suppose start passed to itd_slot_ok is 537, period, usb->interv
On Sat, 7 Sep 2013, joe M wrote:
> Hello Sarah, Alan,
>
> Just wanted to check if you have any suggestions on how to go about
> debugging this issue.
Nothing that I haven't mentioned previously.
> I get these messages "usb 6-1: device not accepting address 5, error
> -62" when I connect my FS d
I've posted a number of requests for aid on this and have gotten very
little responses and none that were helpful. I have spent at least 24
hours of research time on this and just a little direction from somebody
who knows this subsystem can help me immensely as the IRQ subsystem is
new to me.
On 09/07/2013 05:19 PM, Daniel Santos wrote:
I've posted a number of requests for aid on this and have gotten very little
responses and none that were helpful. I have spent at least 24 hours of
research time on this and just a little direction from somebody who knows this
subsystem can help me
It is Private
I am George Daniels, a Banker and credit system programmer (HSBC bank).
I saw your email address while browsing through the bank D.T.C Screen in
my office yesterday so I decided to use this very chance to know you. I
believe we should use every opportunity to know each other better.
Hello Alan,
>> Just wanted to check if you have any suggestions on how to go about
>> debugging this issue.
>
> Nothing that I haven't mentioned previously.
Thank you for your thoughts. I could not get a logic analyzer to
figure out the signals on the lines. But, I could log the usb
interrupts fr
On Sat, 7 Sep 2013, joe M wrote:
> Hello Alan,
>
> >> Just wanted to check if you have any suggestions on how to go about
> >> debugging this issue.
> >
> > Nothing that I haven't mentioned previously.
>
> Thank you for your thoughts. I could not get a logic analyzer to
> figure out the signals
