linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: "Absolut Hunter" <absoluthunter@comcast.net>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Linux 2.4.25 / MPC8280 / ram config vs Linux instability?
Date: Mon, 11 Jul 2005 11:39:05 -0700	[thread overview]
Message-ID: <bd3bf2b4d8489c491b4c3cee2d38a4b2@embeddededge.com> (raw)
In-Reply-To: <20050711134713.D767067C13@ozlabs.org>


On Jul 11, 2005, at 6:38 AM, Absolut Hunter wrote:

> ..... However, my goal is
> to map SRAM <8ns speeds> down to the address 0x00000000, to map the 
> vector
> table, so I can achieve a very fast interrupt response time.

The things Linux does to cause interrupt latencies are going to ensure
you aren't going to see any differences to the "interrupt response 
time." :-)
 From a system perspective, you are going to be much better off using
your SRAM for CPM data buffering than for any general software use.

> Does anyone have any idea what would cause this instability?

Yeah, I can't find a way to actually map the memory as you have
described.  You actually have the SRAM and SDRAM multiply mapped
on top of one another, and depending upon which chip selects
are used and the values in their registers, you are selecting between
the two memories.  Several cases exist.  You are either mapping the
SRAM on top of the SDRAM, or vice versa.  You really have only 32M
of memory available, so any access to the "upper" 2M is wrapping
around to the lower memory.  Basically, you have a big mess ;-)

You need to map these memories to modulo their size, so to put
the 2M at low memory, you are going to have a hole up to a 32M
boundary before you can map the SDRAM.  It's possible to do
this, but not without some custom Linux modifications.

Thanks.

	-- Dan

  parent reply	other threads:[~2005-07-11 18:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-11 13:38 Linux 2.4.25 / MPC8280 / ram config vs Linux instability? Absolut Hunter
2005-07-11 14:01 ` Michael Richardson
2005-07-11 14:03 ` Mark Chambers
2005-07-11 14:22 ` Wolfgang Denk
2005-11-02 13:49   ` About 2.6.14 on AMCC Yosemite board KylongMu
2005-11-02 16:46     ` Wolfgang Denk
2005-11-06 15:55       ` Today's 2.6.14 can't finish build with yosemite-defconfig KylongMu
2005-11-11  2:04       ` 11-11-05 2.6.14 on AMCC Yosemite board(boot error) KylongMu
2005-11-11  8:39         ` Wolfgang Denk
2005-11-12 16:47           ` KylongMu
2005-11-12 18:01             ` Problem solved: " KylongMu
2005-11-12 23:32               ` Wolfgang Denk
2005-11-12 23:30             ` Wolfgang Denk
2005-07-11 18:39 ` Dan Malek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-11 13:59 Linux 2.4.25 / MPC8280 / ram config vs Linux instability? Steven Blakeslee
2005-07-11 14:02 Absolut Hunter
2005-07-11 14:39 ` Michael Richardson

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=bd3bf2b4d8489c491b4c3cee2d38a4b2@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=absoluthunter@comcast.net \
    --cc=linuxppc-embedded@ozlabs.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).