From: Matt Porter <mporter@kernel.crashing.org>
To: "Barbier, Renaud (GE Infrastructure)" <Renaud.Barbier@ge.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 440GX MMU problem
Date: Fri, 3 Dec 2004 11:05:45 -0700 [thread overview]
Message-ID: <20041203110545.A25168@home.com> (raw)
In-Reply-To: <45ABD2373C33C4459D42B40EC4F346F2047DC3D4@FTWMLVEM03.e2k.ad.ge.com>; from Renaud.Barbier@ge.com on Fri, Dec 03, 2004 at 06:12:31AM -0600
On Fri, Dec 03, 2004 at 06:12:31AM -0600, Barbier, Renaud (GE Infrastructure) wrote:
>
> I am using linux 2.4.26 on a 440GX with 512MB of SDRAM.
> >From U-boot I can see the whole memory.
> If I boot Linux, unless I set the boot parameter mem=256M (or less).
> it will not boot. Linux does not seem to go further than the MMU_setup.
Verified that the 440GX eval with 512MB works on both 2.4.26 and current
2.4. Works For Me(tm).
> Any idea why it cannot use 512MB?
A broken board port would do it. If you deviate for any reason
from the stock kernel configuration you can shoot yourself in the
foot real fast. If you can provide some details on your custom
board and port, somebody may be able to help you.
-Matt
next prev parent reply other threads:[~2004-12-03 18:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 12:12 440GX MMU problem Barbier, Renaud (GE Infrastructure)
2004-12-03 17:40 ` Eugene Surovegin
2004-12-03 18:05 ` Matt Porter [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-03 17:45 Barbier, Renaud (GE Infrastructure)
2004-12-03 18:08 ` Matt Porter
2004-12-03 20:52 Barbier, Renaud (GE Infrastructure)
2004-12-03 21:56 VanBaren, Gerald (AGRE)
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=20041203110545.A25168@home.com \
--to=mporter@kernel.crashing.org \
--cc=Renaud.Barbier@ge.com \
--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).