From: Kumar Gala <galak@kernel.crashing.org>
To: Liu Dave-r63238 <DaveLiu@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [QUESTION] Enable coherency for all pages on 83xx to fix PCI data corruption
Date: Tue, 29 Aug 2006 10:28:23 -0500 [thread overview]
Message-ID: <43765FEB-22D2-4435-A074-7DEF969E466B@kernel.crashing.org> (raw)
In-Reply-To: <995B09A8299C2C44B59866F6391D263511B9EA@zch01exm21.fsl.freescale.net>
On Aug 28, 2006, at 9:04 PM, Liu Dave-r63238 wrote:
>> This was to address PCI5 if I remember correctly.
>>
>> - kumar
>>
>> On Aug 28, 2006, at 2:49 AM, Liu Dave-r63238 wrote:
>>
>>> All,
>>>
>>> I want to know which PCI errata is solved by this patch and if this
>>> patch did test on real hardware.
>>>
>>> I know this patch turn on the 'M' bit -memory coherency.
>>> But I don't believe this can solved the "PCI read multi-line"
>>> errata.
>>>
>>> -DAve
> <snip>
>
> I also don't believe this patch can solve the PCI5 errata, The PCI5
> description:
>
> When external PCI devices try to read from the memory which is defined
> as
> prefetchable and where the transaction is more than one cache line,
> there
> may be data corruption.
Randy may remember but this fixed an issue related that he was seeing
with an e100 or e1000 and it was the solution provided by the
Freescale Apps team in Austin.
- kumar
next prev parent reply other threads:[~2006-08-29 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 7:49 [QUESTION] Enable coherency for all pages on 83xx to fix PCI data corruption Liu Dave-r63238
2006-08-28 13:49 ` Kumar Gala
2006-08-29 2:04 ` Liu Dave-r63238
2006-08-29 15:28 ` Kumar Gala [this message]
2006-08-30 22:15 ` Randy Vinson
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=43765FEB-22D2-4435-A074-7DEF969E466B@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=DaveLiu@freescale.com \
--cc=linuxppc-dev@ozlabs.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