From: Wojciech Kromer <krom@dgt-lab.com.pl>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: linux-2.4.18 & copy-back cache mode
Date: Fri, 08 Mar 2002 15:41:54 +0100 [thread overview]
Message-ID: <3C88CDB2.7070905@dgt-lab.com.pl> (raw)
In-Reply-To: D3A72C5007329A4F991C0DD87202259F096A96@sekhmet.ad.newisys.com
>
>
>I am sorry. I meant 64Mhz , not 66Mhz.
>
>
>
>
>I am running my MPC855T at 66Mhz 1:1 CPU/bus clock mode without any problems. I used an app. note from Motorola to do this and according to the app.note, we just need to satisfy some timing constraints on the processor (latency of data reaching the MPC pins from SDRAM). The app. note suggests using specific Micron SDRAM which satisfy all these requirements.
>
>Subject: Re: linux-2.4.18 & copy-back cache mode
>
Maybe it's teh same problem.
I have some problems while strong memory usage, for example copying a lot of files.
It stops on bus errors.
Anyone could send me UPM table for CAS_LATENCY==3. I'm not sure if burst is realy needed. Now its disabled, because I do not have correct UPM table for this.
==================================
I have CPU: XPC860xxZPnnD4 at 80 MHz: 4 kB I-Cache 4 kB D-Cache FEC present
And SDRAM:
DIMM size 0x08000000 (128 MB)
[00] 80 number of bytes written/used
[01] 08 total number of bytes in serial PD device
[02] 04 fundamental memory type (SDRAM)
[03] 0c number of rows
[04] 09 number of columns
[05] 02 number of banks
[06] 40 data width (lo)
[07] 00 data width (hi)
[08] 01 interface levels
[09] 75 RAS access
[0A] 54 CAS access
[0B] 00 configuration type (non-parity/parity/ECC)
[0C] 80 refresh rate/type
[0D] 08 primary DRAM organization
[0E] 00 secondary DRAM organization (parity/ECC-checkbits)
[0F] 01
[12] 04 supported CAS latencies: 3
[1F] 10 bank size (64 MB)
other:
0 1 2 3 4 5 6 7 8 9 a b c d e f
[1x] 8f 04 04 01 01 00 0e a0 60 00 00 14 0f 14 2c 10
[2x] 15 08 15 08 00 00 00 00 00 00 00 00 00 00 00 00
[3x] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 12 9c
[4x] 2c ff ff ff ff ff ff ff 01 00 00 00 00 00 00 00
[5x] 00 00 00 00 00 00 00 00 00 00 00 01 00 ff ff ff
[6x] ff ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00
[7x] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 64 fd
setup MEM like this
UPM 00804000
MPTPR 00001000
SDRAM 2 32MB BR fff00110=0x000000C1 OR fff00114=0xFE000F00
SDRAM 3 32MB BR fff00118=0x020000C1 OR fff0011c=0xFE000F00
SDRAM 5 32MB BR fff00128=0x040000C1 OR fff0012c=0xFE000F00
SDRAM 6 32MB BR fff00130=0x060000C1 OR fff00134=0xFE000F00
MBMR 4e944112 MAR 000000c8 MCR 80804234 80806234 8080a234 8080c234
--
* * * * * * * * * * * *
* per pedes ad astra! *
* * * * * * * * * * * * mailto:krom@dgt-lab.com.pl
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-03-08 14:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-07 22:18 linux-2.4.18 & copy-back cache mode Navin Boppuri
2002-03-08 14:41 ` Wojciech Kromer [this message]
2002-03-08 15:22 ` Wolfgang Denk
2002-03-12 7:08 ` Wojciech Kromer
2002-03-12 9:38 ` Wolfgang Denk
2002-03-09 1:19 ` Conn Clark
-- strict thread matches above, loose matches on Subject: below --
2002-03-12 15:58 Navin Boppuri
2002-03-06 9:14 Laurent Pinchart
2002-03-06 14:52 ` Dan Malek
2002-03-06 15:37 ` Laurent Pinchart
2002-03-06 16:28 ` Dan Malek
2002-03-06 17:09 ` Wolfgang Denk
2002-03-06 19:50 ` Dan Malek
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=3C88CDB2.7070905@dgt-lab.com.pl \
--to=krom@dgt-lab.com.pl \
--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).