public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Aidan Williams <aidan@nicta•com.au>
To: linuxppc-embedded@ozlabs•org
Subject: Virtex-4 FX12 Mini-Module support
Date: Sat, 08 Apr 2006 08:42:17 +1000	[thread overview]
Message-ID: <4436EAC9.9000904@nicta.com.au> (raw)
In-Reply-To: <4418EA57.6060308@petalogix.com>

[-- Attachment #1: Type: text/plain, Size: 828 bytes --]

Hi All,

I'm using the UQ powerpc uclinux code on the
Memec Virtex-4 FX12 Mini-Module Development Kit.

I have attached a patch with our modifications:

   - switch to set cache policy (OFF, WriteThru, WriteBack)
   - switch to enable PPC405 CPU_213 errata workaround
   - cosmetic update to cputable
   - view ccr0 register in /proc/cpu

The patch is against:
http://www.itee.uq.edu.au/~pml/uclinux_powerpc/linuxppc-2.4-20051021.tgz


The specific modules/chips we're using have a silicon bug,
See the euphemistically named "Solution 13:"
http://www.xilinx.com/xlnx/xil_ans_display.jsp?iLanguageID=1&iCountryID=1&getPagePath=20658

The board boots and runs reliably with the caches OFF.
WriteThru and WriteBack caching cause memory corruption and
this is why we implemented the cache policy switch.


regards
	aidan
____
:wq!


[-- Attachment #2: virtex-4-fx12-minimodule.txt --]
[-- Type: plain/text, Size: 23729 bytes --]

       reply	other threads:[~2006-04-07 22:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4417CEB8.40004@nicta.com.au>
     [not found] ` <4417FBA9.1030101@petalogix.com>
     [not found]   ` <4418896E.4040007@nicta.com.au>
     [not found]     ` <44189045.3010905@petalogix.com>
     [not found]       ` <4418BA71.7040208@nicta.com.au>
     [not found]         ` <4418EA57.6060308@petalogix.com>
2006-04-07 22:42           ` Aidan Williams [this message]
2007-05-28  9:26 Virtex-4 FX12 Mini-Module support Ales Gorkic

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=4436EAC9.9000904@nicta.com.au \
    --to=aidan@nicta$(echo .)com.au \
    --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