From: Marc Leeman <marc.leeman@barco.com>
To: Jos Beck <jos_beck@euronet.nl>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: PCI on MPC8250VR
Date: Tue, 30 Mar 2004 08:49:42 +0200 [thread overview]
Message-ID: <20040330064942.GA32569@smtp.barco.com> (raw)
In-Reply-To: <40684302.2040701@euronet.nl>
> In this list I only read about trouble with the 8250 PCI :)
In our case, we are using PCI quite successfully for simple data pushing
to another device (8245 writes) and DMA is only limited by a (known)
silicon bug in the DSP revision.
Master-Read operations from the PPC memory over PCI have currently a
problem, but we are not able to pinpoint it to either the PPC or the
DSP.
I don't think PCI on the PPC side is a problem though :-/
marc.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-30 6:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 15:38 PCI on MPC8250VR Jos Beck
2004-03-30 6:49 ` Marc Leeman [this message]
2004-03-30 8:07 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2004-03-30 16:24 Rune Torgersen
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=20040330064942.GA32569@smtp.barco.com \
--to=marc.leeman@barco.com \
--cc=jos_beck@euronet.nl \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).