All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: laurent.pinchart@capflow.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: linux-2.4.18 & copy-back cache mode
Date: Wed, 06 Mar 2002 11:28:39 -0500	[thread overview]
Message-ID: <3C8643B7.60506@embeddededge.com> (raw)
In-Reply-To: 3C8637A2.7020401@capflow.com


Laurent Pinchart wrote:


> It's a Rev. D.3

Hmmmm....I regularly use one of those for testing (maybe it's an 855T),
and it seems OK for me.  The first one I had didn't work well, but
it was tracked down to a UPM/SDRAM timing problem.  People keep talking
about running > 50 MHz bus on these newer parts, is there something
different about the memory controller that allows this and may cause
compatibility problems?  I have (fortunately :-) not looked at this
level of detail in the newer parts.

When you disable copyback you also disable burst mode write from
the CPU core.


	-- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-03-06 16:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-06  9:14 linux-2.4.18 & copy-back cache mode Laurent Pinchart
2002-03-06 14:52 ` Dan Malek
2002-03-06 15:37   ` Laurent Pinchart
2002-03-06 16:28     ` Dan Malek [this message]
2002-03-06 17:09       ` Wolfgang Denk
2002-03-06 19:50         ` Dan Malek
2002-03-07  2:42           ` serial console on 405GP Kim, Kwansuk
2002-03-11  0:36             ` Sangmoon Kim
  -- strict thread matches above, loose matches on Subject: below --
2002-03-07 22:18 linux-2.4.18 & copy-back cache mode Navin Boppuri
2002-03-08 14:41 ` Wojciech Kromer
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
2002-03-12 15:58 Navin Boppuri

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=3C8643B7.60506@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=laurent.pinchart@capflow.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.