From: Stefan Roese <sr@denx•de>
To: linuxppc-embedded@ozlabs•org
Subject: Re: Yosemite/440EP PLB4 vs PLB3 DMA to PCI issue
Date: Mon, 6 Feb 2006 19:31:24 +0100 [thread overview]
Message-ID: <200602061931.25370.sr@denx.de> (raw)
In-Reply-To: <43E68E85.3080100@ovro.caltech.edu>
Hi David,
I never used DMA on 440EP/GP till now so I just noticed the two different
PLB's and their DMA controllers. Never seen this on any 4xx PPC so far. I
suspect that the PLB4 is integrated mainly because of the USB interface.
On Monday 06 February 2006 00:47, David Hawkins wrote:
> I took a look at the 440EP user manual, and I haven't been
> able to explain the PLB4 DMA controller observations.
>
> Here's what I've got so far;
>
> p595: PLB-to-PCI transaction handling
> Shows the two situations where the PCI bridge will
> generate memory-read-line (MRL) and memory-read-multiple (MRM)
What version of the user manual are you referring to? Could you please give
the pages for the current manual (Revision 1.18).
<snip>
> (I hope you had a nice vacation Stefan!)
Thanks. Very nice. One week of sunshine in the snow. :-)
Ciao,
Stefan
next prev parent reply other threads:[~2006-02-06 18:31 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 9:35 Yosemite/440EP why are readl()/ioread32() setup to readlittle-endian? Jenkins, Clive
2006-02-02 9:46 ` Eugene Surovegin
2006-02-02 14:37 ` Matt Porter
2006-02-02 17:45 ` Eugene Surovegin
2006-02-02 18:16 ` Matt Porter
2006-02-05 4:41 ` Yosemite/440EP PLB4 vs PLB3 DMA to PCI issue David Hawkins
2006-02-05 10:39 ` Wolfgang Denk
2006-02-05 23:47 ` David Hawkins
2006-02-06 18:31 ` Stefan Roese [this message]
2006-02-06 19:09 ` David Hawkins
2006-02-08 15:38 ` Stefan Roese
2006-02-08 18:43 ` David Hawkins
2006-02-09 0:34 ` Wolfgang Denk
2006-02-09 13:25 ` Mark Chambers
2006-02-09 23:58 ` Yosemite/440EP 'issues' as a PCI target David Hawkins
2006-02-10 7:47 ` Stefan Roese
2006-02-10 17:05 ` David Hawkins
2006-02-10 17:20 ` Andrew Armitage
2006-02-10 17:26 ` David Hawkins
2006-02-10 17:31 ` Wolfgang Denk
2006-02-10 17:38 ` David Hawkins
2006-02-10 17:58 ` David Hawkins
2006-02-11 6:03 ` David Hawkins
2006-02-11 8:21 ` Stefan Roese
2006-02-11 18:15 ` David Hawkins
2006-02-11 13:03 ` Wolfgang Denk
2006-02-10 17:59 ` Stefan Roese
2006-02-10 18:11 ` David Hawkins
2006-02-11 8:06 ` Stefan Roese
2006-02-11 18:06 ` David Hawkins
2006-02-11 19:00 ` David Hawkins
[not found] ` <001701c62e6c$09c48ea0$6401a8c0@CHUCK2>
2006-02-10 18:19 ` David Hawkins
2006-02-11 6:06 ` David Hawkins
[not found] ` <43ECCCA2.1070007@sandburst.com>
[not found] ` <43ECCE7A.4090507@ovro.caltech.edu>
[not found] ` <43ECD19E.8010604@sandburst.com>
2006-02-10 19:13 ` David Hawkins
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=200602061931.25370.sr@denx.de \
--to=sr@denx$(echo .)de \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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