All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: Dan Malek <dan@embeddededge.com>
Cc: Bruno Randolf <br1@4g-systems.de>,
	Alexander Popov <s_popov@prosyst.bg>,
	linux-mips@linux-mips.org, jsun@mvista.com
Subject: Re: Mycable XXS board
Date: Fri, 7 Mar 2003 13:39:19 -0800	[thread overview]
Message-ID: <20030307133919.P26071@mvista.com> (raw)
In-Reply-To: <3E68FD21.5050402@embeddededge.com>; from dan@embeddededge.com on Fri, Mar 07, 2003 at 03:12:17PM -0500

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

  reply	other threads:[~2003-03-07 21:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-07 12:36 Mycable XXS board Alexander Popov
2003-03-07 12:40 ` Pete Popov
2003-03-07 15:47   ` Bruno Randolf
2003-03-07 18:13     ` Jun Sun
2003-03-07 20:12       ` Dan Malek
2003-03-07 21:39         ` Jun Sun [this message]
2003-03-07 21:54           ` Dan Malek
2003-03-11 10:30             ` Bruno Randolf
2003-03-11 15:17               ` Pete Popov
2003-03-11 21:43                 ` Eric DeVolder
2003-03-11 21:57                   ` Dan Malek
2003-03-13 13:08                     ` Bruno Randolf
2003-03-13 16:03                       ` Dan Malek
2003-03-13 17:23                         ` Bruno Randolf
2003-03-13 17:50                           ` Dan Malek
2003-03-13 18:07                             ` Pete Popov
2003-03-11 15:59 ` Tiemo Krueger - mycable GmbH
  -- strict thread matches above, loose matches on Subject: below --
2003-03-10  8:27 Tiemo Krueger - mycable GmbH
2003-03-10  8:33 Tiemo Krueger - mycable GmbH
2003-03-10  9:41 ` Alexander Popov
2003-03-10  9:41   ` Alexander Popov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030307133919.P26071@mvista.com \
    --to=jsun@mvista.com \
    --cc=br1@4g-systems.de \
    --cc=dan@embeddededge.com \
    --cc=linux-mips@linux-mips.org \
    --cc=s_popov@prosyst.bg \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.