From: Aidan Williams <aidan@nicta•com.au>
To: Rick Moleres <rick.moleres@xilinx•com>
Cc: linuxppc-embedded@ozlabs•org, "Martin, Tim" <tim.martin@viasat•com>
Subject: Re: Linux on Virtex4
Date: Wed, 21 Jun 2006 18:46:38 +1000 [thread overview]
Message-ID: <4499076E.6000804@nicta.com.au> (raw)
In-Reply-To: <689CB232690D8D4E97DA6C76DA098E6C027E6274@XCO-EXCHVS1.xlnx.xilinx.com>
Rick Moleres wrote:
> There's also a Linux 2.4 patch provided with the ML403 PPC reference
> design on the Xilinx website
> (http://www.xilinx.com/products/boards/ml403/reference_designs.htm) that
> takes care of a Virtex-4 PPC cache issue (CCR0 register). Have you
> applied this?
>
Rick, which cache issue are you referring to?
I tried setting the CCR0 bits in accordance with:
"Solution 10: CPU_213: Incorrect data might be
flushed from the data cache"
but that didn't fix things in my case for the Avnet FX12 MiniModule.
I'm pretty sure that the FX12-MM strikes:
"Solution 13: The return of a cacheline transaction that
is not target word first (non-target word first) can
cause data corruption in the PPC405 Core data cache in
Virtex-4 FX devices."
For which the only solutions mentioned are to run without caches or get
a fixed chip.
As I understand it, the memory controller for this board must be on the
OPB because the memory is 16-bit. Is there any way to move the memory
controller to the PLB thus avoiding the cache problem (for RAM at least)?
- aidan
next prev parent reply other threads:[~2006-06-21 8:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 15:29 Linux on Virtex4 Rick Moleres
2006-06-21 8:46 ` Aidan Williams [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-13 15:46 Rick Moleres
2006-06-21 20:33 Rick Moleres
2006-06-21 18:10 Rick Moleres
2006-06-20 17:53 Martin, Tim
2006-06-19 23:24 Martin, Tim
2006-06-19 23:38 ` Grant Likely
2006-06-21 7:14 ` Filippo Capurso
2006-06-21 7:55 ` Grant Likely
2006-06-22 7:32 ` Filippo Capurso
2006-06-20 5:40 ` Aidan Williams
2006-06-20 6:56 ` Peter Korsgaard
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=4499076E.6000804@nicta.com.au \
--to=aidan@nicta$(echo .)com.au \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=rick.moleres@xilinx$(echo .)com \
--cc=tim.martin@viasat$(echo .)com \
/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