From: Florian Boelstler <euphoria@arcor.de>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Reserving small amounts of memory with mem= (MPC85xx, 2.6.15 arch/ppc)
Date: Mon, 16 Jun 2008 16:26:43 +0200 [thread overview]
Message-ID: <g35t76$u50$1@ger.gmane.org> (raw)
In-Reply-To: <485292C2.6030103@freescale.com>
Scott Wood wrote:
> CAM entries can be any power of 4 between 4K and 256M. However, the
> code currently is hardcoded to use no more than 3 entries.
Ah, this explains a lot, thanks.
> Alternately, do you have highmem enabled? That will let you access the
> rest of the RAM that the CAM doesn't map, though I don't know if an
> initrd in highmem works.
I didn't had highmem enabled so far. Now it is and Linux is able to
allocate rest of memory.
It doesn't work if initrd is placed in highmem though. I just put it at
the end of lowmem.
Cheers,
Florian
prev parent reply other threads:[~2008-06-16 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 16:18 Reserving small amounts of memory with mem= (MPC85xx, 2.6.15 arch/ppc) Florian Boelstler
2008-06-12 19:14 ` Sylvain Joyeau
2008-06-13 14:30 ` Florian Boelstler
2008-06-13 15:31 ` Scott Wood
2008-06-16 14:26 ` Florian Boelstler [this message]
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='g35t76$u50$1@ger.gmane.org' \
--to=euphoria@arcor.de \
--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).