From: David Brownell <david-b@pacbell.net>
To: linux-usb-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] pegasus + MediaGX: Oops in khubd, the continuing story?
Date: Fri, 04 May 2001 16:23:49 -0700 [thread overview]
Message-ID: <0ba601c0d4f1$46c07a00$6800000a@brownell.org> (raw)
In-Reply-To: <E14vnVb-00085n-00@the-village.bc.nu>
> I suspect the ohci driver currently. I've been reviewing it a little and it
> is full of code written by someone who does not know about pci write posting.
I think there's a lot of that going around ... I don't think any of what you
mentioned was in the Documentation/pci.txt writeup, or any other source
of kernel documentation I found when I started to look at at that code!
That diagnosis works as well with the known facts as any other; maybe
better, considering some of the info I've collected offline. And it could
also explain some other intermittent failures.
> You have to do
>
> writel(STOP, reg->dmactrl);
> [posted]
> readl(reg->dmactrl)
> [read forces write, read reply will follow any DMA
> pending the other way]
Good to know. That'd apply for any register read, not just the
one that was written to, yes?
- Dave
prev parent reply other threads:[~2001-05-04 23:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-04 20:16 pegasus + MediaGX: Oops in khubd, the continuing story? Frank de Lange
2001-05-04 21:53 ` [linux-usb-devel] " Alan Cox
2001-05-04 23:23 ` David Brownell [this message]
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='0ba601c0d4f1$46c07a00$6800000a@brownell.org' \
--to=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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