Some xhci controllers (eg ASMedia) don't like processing a LINK TRB and
then finding that they can't process the next TRB.
Instead of flipping the cycle bit on the first data TRB, remember the
real first TRB in prepare_ring() and flip that in giveback_first_trb().
In queue_trb() ignore the cycle
Hi David,
I've been thinking about this some more, and I'd like to propose a much
simpler solution.
The TD fragment rules didn't go into the xHCI specification until the
1.0 revision. The code that follows those rules only seems to trigger
issues for 0.96 ASMedia hosts, while Intel 1.0 hosts ben
On 01/22/2014 12:56 PM, Sarah Sharp wrote:
> Walt, can you turn on xHCI debugging and look for whether the NEC host
> that worked with David's patch is a 1.0 host? You'll see a line like:
>
> // @%p = 0x%x (CAPLENGTH AND HCIVERSION)
Hi Sarah. This is from the NEC host controller, *not* the ASMe
On Wed, Jan 22, 2014 at 03:22:53PM -0800, walt wrote:
> On 01/22/2014 12:56 PM, Sarah Sharp wrote:
> > Walt, can you turn on xHCI debugging and look for whether the NEC host
> > that worked with David's patch is a 1.0 host? You'll see a line like:
> >
> > // @%p = 0x%x (CAPLENGTH AND HCIVERSION)
From: Sarah Sharp
> Hi David,
>
> I've been thinking about this some more, and I'd like to propose a much
> simpler solution.
>
> The TD fragment rules didn't go into the xHCI specification until the
> 1.0 revision. The code that follows those rules only seems to trigger
> issues for 0.96 ASMedi
On Thu, Jan 23, 2014 at 10:35:56AM +, David Laight wrote:
> From: Sarah Sharp
> > Hi David,
> >
> > I've been thinking about this some more, and I'd like to propose a much
> > simpler solution.
> >
> > The TD fragment rules didn't go into the xHCI specification until the
> > 1.0 revision. Th
From: Sarah Sharp
> On Wed, Jan 22, 2014 at 03:22:53PM -0800, walt wrote:
> > On 01/22/2014 12:56 PM, Sarah Sharp wrote:
> > > Walt, can you turn on xHCI debugging and look for whether the NEC host
> > > that worked with David's patch is a 1.0 host? You'll see a line like:
> > >
> > > // @%p = 0x%
From: Sarah Sharp
> Hi David,
>
> I've been thinking about this some more, and I'd like to propose a much
> simpler solution.
>
> The TD fragment rules didn't go into the xHCI specification until the
> 1.0 revision. The code that follows those rules only seems to trigger
> issues for 0.96 ASMed
