linux-mips
[Top] [All Lists]

Re: Mycable XXS board

To: Dan Malek <dan@embeddededge.com>
Subject: Re: Mycable XXS board
From: Jun Sun <jsun@mvista.com>
Date: Fri, 7 Mar 2003 13:39:19 -0800
Cc: Bruno Randolf <br1@4g-systems.de>, Alexander Popov <s_popov@prosyst.bg>, linux-mips@linux-mips.org, jsun@mvista.com
In-reply-to: <3E68FD21.5050402@embeddededge.com>; from dan@embeddededge.com on Fri, Mar 07, 2003 at 03:12:17PM -0500
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <3E689267.3070509@prosyst.bg> <1047040846.10649.10.camel@adsl.pacbell.net> <200303071647.13275.br1@4g-systems.de> <20030307101354.N26071@mvista.com> <3E68FD21.5050402@embeddededge.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.2.5i
On Fri, Mar 07, 2003 at 03:12:17PM -0500, Dan Malek wrote:
> Jun Sun wrote:
> 
> > More than likely this is due to the interrupt routing for USB controller
> > not being setup correctly.
> 
> How did you come to this conclusion?  Is this a PCI USB controller or the
> on-chip peripheral?  I have Au1xxx boards were on-chip usb is
> required and is working fine.  There aren't any options to configuring
> on-chip USB interrupts on Au1xxx.  It could just as likely be a Linux kernel
> configuration problem.  We know there is something amiss with Au1xxx USB
> in big endian mode, but all LE boards should work fine.
>

I have seen USB working under BE mode in many instances.  (Acutally
that I have two that work.).  I don't think endianess is the issue.

I have seen "number assign failures" a couple of times before, and it
is all because interrupt not routed correctedly.  That is where "more than
likely" comes from.

Of course, I have only dealt with PCI USB controllers.  On-chip ones may
have another set of additional issues that I am not aware of.

Jun

<Prev in Thread] Current Thread [Next in Thread>