Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Bruno Randolf <br1@4g-systems.de>
To: Dan Malek <dan@embeddededge.com>, Jun Sun <jsun@mvista.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Mycable XXS board
Date: Tue, 11 Mar 2003 11:30:57 +0100	[thread overview]
Message-ID: <200303111130.57387.br1@4g-systems.de> (raw)
In-Reply-To: <3E691514.7000907@embeddededge.com>

On Friday 07 March 2003 22:54, Dan Malek wrote:

> That's what I wanted to clarify.  Are we discussing one of the on-chip
> peripheral USB controllers of the Au1xxx, or is it a PCI USB controller
> that was plugged into the Au1500.  In the case of the on-chip controller,
> there aren't any interrupt routing problems, it's identical (and the same
> code) on all Au1xxx boards.

we are discussing the on-chip USB controller for the mycable board. and its 
little endian...

any ideas where the assignment errors could come from in this case?

thanks,
bruno

  reply	other threads:[~2003-03-11 10:31 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
2003-03-07 21:54           ` Dan Malek
2003-03-11 10:30             ` Bruno Randolf [this message]
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=200303111130.57387.br1@4g-systems.de \
    --to=br1@4g-systems.de \
    --cc=dan@embeddededge.com \
    --cc=jsun@mvista.com \
    --cc=linux-mips@linux-mips.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox