Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Kunihiko IMAI <kimai@iodata.jp>
To: linux-mips@linux-mips.org
Subject: Re: USB on MIPS
Date: Fri, 19 Dec 2003 13:14:31 +0900	[thread overview]
Message-ID: <m3zndpsau0.wl@iodata.jp> (raw)
In-Reply-To: <20031218094321.A4146@mvista.com>

Hi,

At Thu, 18 Dec 2003 09:43:21 -0800,
Jun Sun wrote:
> 
> On Thu, Dec 18, 2003 at 07:58:36PM +0530, samavarthy c wrote:
> > Hi,
(snip)
> 
> Another possiblity (which is probably more likely) is the IRQ
> number is not seupt correctly.  

And another possibilities are:

	DMA cache coherency
		NEC VR4xxxs have no bus-snoop function. So
		cache-coherency must be maintaind by software.
		(or use KSEG1 access)

		But I remember linux-2.4.18 of usb-ohci.c doesn't have
		this problem.

	Read/write cycle order
		Read/write cycle order of CPU instruction level is
		guaranteed at bus level?
		( Or at assembler level, the sequent instruction is
		re-ordered ? )

		Newer version of usb-ohci.c has some wmb() funtions.
		It synchronizes read/write order.

I got similar errors on VR4181A with 2.4.18 kernel.  VR4181A has
built-in USB OHCI 1.1 host connected internal PCI bus.

To fix this problem, I compared newer usb-ohci.c and put wmb()
corresponded place. It is expaneded as subsequent NOPs. (VR4xxx has
real SYNC instruction.)

Thanks.
_._. __._  _ . ... _  .___ ._. _____ _... ._ _._ _.._. .____  _ . ... _

                                                          Kunihiko IMAI

  reply	other threads:[~2003-12-19  4:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-18 14:28 USB on MIPS samavarthy c
2003-12-18 16:51 ` Pete Popov
2003-12-18 17:43 ` Jun Sun
2003-12-19  4:14   ` Kunihiko IMAI [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-20  7:22 samavarthy c
2003-12-20  8:58 ` Dimitri Torfs

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=m3zndpsau0.wl@iodata.jp \
    --to=kimai@iodata.jp \
    --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