From: Jan Damborsky <Jan.Damborsky@devcom.cz>
To: "Wells, Charles" <Charles.Wells@nielsenmedia.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Problem with data cache on MPC823E
Date: Wed, 22 Jan 2003 10:02:21 +0100 [thread overview]
Message-ID: <3E2E5E1D.4010002@devcom.cz> (raw)
In-Reply-To: DF2B720CF774D21189EE00805FA7FA220517834D@nmrusdunsx3.nielsenmedia.com
Wells, Charles wrote:
>Jan,
>
>The following question assumes that your DRAM is physically organized as
>32-bits wide and connected to CS1.
>
>Do you have the PS field of BR1 set to 00 (32-bit mode) or is it set to 01
>(8-bit mode)? If it's set to 8-bit mode, a burst access becomes 16 bus
>cycles, which looks a lot like 4 bursts.
>
>Regards,
>Charlie
>
>
Yes,
DRAM is organized as 32-bits wide and connected to CS2 (PS field of BR2
is set to 00 - 32 bit mode).
The problem is that burst access becomes 16 bus cycles only from time to
time. And this problem
occurs only when accessing data cache. Instruction cache use always
correct 4 bus cycle bursts.
Thanks,
Jan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-01-22 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 20:40 Problem with data cache on MPC823E Wells, Charles
2003-01-22 9:02 ` Jan Damborsky [this message]
[not found] <DF2B720CF774D21189EE00805FA7FA220517835A@nmrusdunsx3.nielsenmedia.com>
2003-01-27 7:42 ` Jan Damborsky
-- strict thread matches above, loose matches on Subject: below --
2003-01-21 16:28 Jan Damborsky
2003-01-21 19:49 ` Wolfgang Denk
2003-01-22 9:05 ` Jan Damborsky
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=3E2E5E1D.4010002@devcom.cz \
--to=jan.damborsky@devcom.cz \
--cc=Charles.Wells@nielsenmedia.com \
--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).