From: "tiejun.chen" <tiejun.chen@windriver.com>
To: "Arshad, Farrukh" <Farrukh_Arshad@mentor.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Kernel not booting when supplying boot parameter mem
Date: Wed, 28 Dec 2011 14:18:33 +0800 [thread overview]
Message-ID: <4EFAB4B9.1020205@windriver.com> (raw)
In-Reply-To: <93CD5F41FDBC6042A6B449764F3B35CC050CB4E4@EU-MBX-03.mgc.mentorg.com>
Arshad, Farrukh wrote:
> Hi Tiejun,
>
> Thanks for your response. Yes, I am running two kernels one on each core in SAMP configuration on P1022RDK board. Given is my memory partitioning. Core 0 is loading fine but Core 1 is not loading. CONFIG_RELOCATABLE is not set.
>
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> Core | Base Address | Size | Uboot parameters | Kernel Configuration |
> -----------------------------|---------------------------|-------------------------------------|------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|
> Core 0 (MEL RT Kernel) | 0x0000,0000 | 0x1000,0000 - 256 (MB) |bootm_low = 0x0000,0000, bootm_size = 0x1000,0000 | CONFIG_PHYSICAL_START = 0x0000,0000, CONFIG_KERNEL_START = 0xC000,0000 |
> Core 1 (LTIB Kernel) |0x1000,0000 | 0x0800,0000 - 128 (MB) |bootm_low = 0x1000,0000, bootm_size = 0x0800,0000 | CONFIG_PHYSICAL_START = 0x1000,0000, CONFIG_KERNEL_START = 0xC000,0000 |
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
Please check if the following commit is already in your kernel:
------
powerpc: Fix memory limits when starting at a non-zero address
memblock_enforce_memory_limit() takes the desired maximum quantity of memory
to end up with, not an address above which memory will not be used.
Tiejun
next prev parent reply other threads:[~2011-12-28 6:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-23 15:07 Kernel not booting when supplying boot parameter mem Arshad, Farrukh
2011-12-27 11:07 ` tiejun.chen
2011-12-28 6:05 ` Arshad, Farrukh
2011-12-28 6:18 ` tiejun.chen [this message]
2011-12-28 9:26 ` Arshad, Farrukh
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=4EFAB4B9.1020205@windriver.com \
--to=tiejun.chen@windriver.com \
--cc=Farrukh_Arshad@mentor.com \
--cc=linuxppc-dev@lists.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 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.