From: konamo <dai.michael@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: AMCC 405ex memory size issue
Date: Sun, 24 May 2009 23:15:41 -0700 (PDT) [thread overview]
Message-ID: <23701685.post@talk.nabble.com> (raw)
In-Reply-To: <23631525.post@talk.nabble.com>
any ideas?
konamo wrote:
>
> Hi all,
> we are using AMCC 405ex kilauea eval board as a demo, not use any
> pci/nand function,
> the board configuration is below:
> u-boot 2009.01,
> linux-2.6.25-rc2,
> 1GB DDR2 memory(2Gbit * 4, 1 rank),
> AMCC powerpc 405ex,
> both 1G and 512MB memory works fine under u-boot, but linux boot fails in
> 1G memory, if we limit mem=512M, linux could boot over nfs. Could anyone
> pls help us how to find the root cause? thanks
>
--
View this message in context: http://www.nabble.com/AMCC-405ex-memory-size-issue-tp23631525p23701685.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.
next prev parent reply other threads:[~2009-05-25 6:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 8:55 AMCC 405ex memory size issue konamo
2009-05-25 6:15 ` konamo [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-25 13:22 Hunter Cobbs
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=23701685.post@talk.nabble.com \
--to=dai.michael@gmail.com \
--cc=linuxppc-dev@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).