USB isochronous traffic with Rasberry Pi [WAS: Re: USB audio device on Raspberry Pi]

Ian Lepore ian at FreeBSD.org
Fri May 9 18:49:43 UTC 2014


On Fri, 2014-05-09 at 18:42 +0200, Hans Petter Selasky wrote:
> On 05/09/14 17:06, Ian Lepore wrote:
> > On Fri, 2014-05-09 at 16:27 +0200, Hans Petter Selasky wrote:
> >> Hi,
> >>
> >> I've tried to dig through the DWC OTG controller to make it work better
> >> in host mode. Can you test the latest code after:
> >>
> >> http://svnweb.freebsd.org/changeset/base/265777
> >>
> >> And report any errors/regression issues when using USB devices?
> >>
> >> --HPS
> >
> > After updating to r265780 and building clean, I consitantly get this
> > when the rpi boots:
> >
> > KDB: debugger backends: ddb
> > [...]
> > smsc0: warning: MII is busy
> > smsc0: at uhub1, port 1, addr 3 (disconnected)
> > smsc0: warning: Failed to read register 0x114
> > smsc0: warning: MII is busy
> > ukphy0: detached
> > miibus0: detached
> > smsc0: <vendor 0x0424 product 0xec00, rev 2.00/2.00, addr 3> on usbus0
> > smsc0: chip 0xec00, rev. 0002
> > miibus0: <MII bus> on smsc0
> > ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus0
> > ukphy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> > ue0: <USB Ethernet> on smsc0
> > ue0: Ethernet address: be:a4:34:6d:c5:2a
> > newnfs server 172.22.42.240:/rpi: not responding
> > newnfs server 172.22.42.240:/rpi: not responding
> > newnfs server 172.22.42.240:/rpi: not responding
> >
> > It's interesting that it worked well enough to mount the nfsroot
> > filesystem, then went bad after that.
> >
> > -- Ian
> 
> Can you try and upgrade again:
> 
> http://svnweb.freebsd.org/changeset/base/265783

Yep, that fixed it, thanks.

-- Ian




More information about the freebsd-arm mailing list