From: Scott Wood <scottwood@freescale.com>
To: Rune Torgersen <runet@innovsys.com>
Cc: Mike Winter <mike.winter@vecimanetworks.com>,
linuxppc-embedded@ozlabs.org
Subject: Re: PCI DMA Problems With 82xx?
Date: Tue, 17 Jun 2008 16:52:44 -0500 [thread overview]
Message-ID: <4858322C.5030402@freescale.com> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B048F2E21@ismail.innsys.innovsys.com>
Rune Torgersen wrote:
> linuxppc-embedded-bounces+runet=innovsys.com@ozlabs.org wrote:
>> Mike Winter wrote:
>>> We are developing with an 8248-based platform, and we have a vendor
>>> telling us that the PCI hardware is unreliable on this CPU family, in
>>> particular the DMA functionality. A quick search of this list
>>> doesn't turn up any horror stories, although the processor does have
>>> some PCI errata listed. Does anybody have any practical experience
>>> using PCI on the 8248 or similar that they can share with me?
>>> Thanks.
>
> We're using all four PCI DMA's on 8265 and 8280 CPU's.
Hmm, did he mean bus-mastering from PCI devices, or the DMA block which
is documented as part of PCI on older chips, but really has nothing to
do with it that I can figure out?
-Scott
next prev parent reply other threads:[~2008-06-17 21:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 19:32 PCI DMA Problems With 82xx? Mike Winter
2008-06-17 21:29 ` Scott Wood
2008-06-17 21:49 ` Rune Torgersen
2008-06-17 21:51 ` Rune Torgersen
2008-06-17 21:52 ` Scott Wood [this message]
2008-06-18 13:32 ` Anybody have an mpc5200b mscan linux driver under 2.6.24, ARCH=powerpc or equiv? Mike Timmons
2008-06-18 13:45 ` Wolfgang Grandegger
2008-06-18 14:02 ` Mike Timmons
2008-06-18 14:18 ` Wolfgang Grandegger
2008-06-18 16:16 ` Mike Timmons
2008-06-19 10:38 ` Daniel Schnell
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=4858322C.5030402@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mike.winter@vecimanetworks.com \
--cc=runet@innovsys.com \
/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).