I did test double reads and always saw the same value both times.
Another piece of info: I tested this software on an older vortex86dx
and saw the same issue. It is plausible that a vortex86dx and
vortex86dx3 could have the same flawed EHCI. Or perhaps there's some
other systemic issue that I'm
From: Daniel Goertzen
> Sent: 24 October 2018 17:47
>
> I am developing a custom USB device that makes use of isochronous IN
> transfers. It works fine from my laptop (xHCI) however on an embedded
> target (vortex86dx3, EHCI) I am seeing mysterious EFBIG errors. After
> adding lots of debug to
On Wed, 24 Oct 2018, Steve Calfee wrote:
> On Wed, Oct 24, 2018 at 9:48 AM Daniel Goertzen
> wrote:
> >
> > I am developing a custom USB device that makes use of isochronous IN
> > transfers. It works fine from my laptop (xHCI) however on an embedded
> > target (vortex86dx3, EHCI) I am seeing
On Wed, 24 Oct 2018, Daniel Goertzen wrote:
> I am developing a custom USB device that makes use of isochronous IN
> transfers. It works fine from my laptop (xHCI) however on an embedded
> target (vortex86dx3, EHCI) I am seeing mysterious EFBIG errors. After
> adding lots of debug to ehci-sched
On Wed, Oct 24, 2018 at 9:48 AM Daniel Goertzen
wrote:
>
> I am developing a custom USB device that makes use of isochronous IN
> transfers. It works fine from my laptop (xHCI) however on an embedded
> target (vortex86dx3, EHCI) I am seeing mysterious EFBIG errors. After
> adding lots of debug
I am developing a custom USB device that makes use of isochronous IN
transfers. It works fine from my laptop (xHCI) however on an embedded
target (vortex86dx3, EHCI) I am seeing mysterious EFBIG errors. After
adding lots of debug to ehci-sched I discovered that the EHCI register
"FRINDEX" which
