linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
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 16:22:50 +0200	[thread overview]
Message-ID: <20050711142250.BC3253539FE@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 11 Jul 2005 06:38:11 PDT." <20050711134713.D767067C13@ozlabs.org>

In message <20050711134713.D767067C13@ozlabs.org> you wrote:
> 
> If I leave the SRAM mapped at higher addresses 0x10000000 and SDRAM at
> 0x00000000, like U-boot defaults to Linux works great. 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.

How fast is your bus? 8 ns is not exactly very fast.

> I hacked U-boot a little bit to remap these addresses, after all the init

Hacked? No hack at all should have been necessary. This  is  standard
configuration stuff.

> reported to Linux, in the bd->memsize. However, now Linux crashes randomly
> all over the place, mostly sig11's task: swapper. I know this is not an

SO one or your memory banks does not work reliably.

> issue with SDRAM stability, and I can't imagine SRAM having problems seeing
> as its 8ns capable and we're running at 15ns at the moment (66mhz).

And what about the state of your hardware? Did you check the signals,
especially when the CPU is stressing the bus in burst mode?


Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Let the programmers be many and the managers few -- then all will  be
productive.               -- Geoffrey James, "The Tao of Programming"

  parent reply	other threads:[~2005-07-11 14:27 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 [this message]
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 ` Linux 2.4.25 / MPC8280 / ram config vs Linux instability? Dan Malek
  -- strict thread matches above, loose matches on Subject: below --
2005-07-11 13:59 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=20050711142250.BC3253539FE@atlas.denx.de \
    --to=wd@denx.de \
    --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).