On Tue, Mar 04, 2014 at 08:13:32PM +0800, vichy wrote:
> hi David:
>
>
> 2014-03-04 19:40 GMT+08:00 David Laight :
> > From: vichy
> >> hi all:
> >> from xhci spec, Interrupter Target is the value between 0 and MaxIntrs-1.
> >> But why the parameter pass to TRB_INTR_TARGTRB_INTR_TARGET is always
hi David:
2014-03-04 19:40 GMT+08:00 David Laight :
> From: vichy
>> hi all:
>> from xhci spec, Interrupter Target is the value between 0 and MaxIntrs-1.
>> But why the parameter pass to TRB_INTR_TARGTRB_INTR_TARGET is always 0.
>>
>> Does that mean so far xhci host didn't support multi-interrupt
From: vichy
> hi all:
> from xhci spec, Interrupter Target is the value between 0 and MaxIntrs-1.
> But why the parameter pass to TRB_INTR_TARGTRB_INTR_TARGET is always 0.
>
> Does that mean so far xhci host didn't support multi-interrupt as
> MSI-X suggested?
AFAIK The Linux USB stack doesn't su
hi all:
from xhci spec, Interrupter Target is the value between 0 and MaxIntrs-1.
But why the parameter pass to TRB_INTR_TARGTRB_INTR_TARGET is always 0.
Does that mean so far xhci host didn't support multi-interrupt as
MSI-X suggested?
Thanks for your help in advance,
--
To unsubscribe from this