From: Ralf Baechle <ralf@linux-mips.org>
To: "Anoop P.A." <Anoop_P.A@pmc-sierra.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Help in enabling HIGHMEM support
Date: Mon, 14 Dec 2009 17:35:09 +0000 [thread overview]
Message-ID: <20091214173509.GB15067@linux-mips.org> (raw)
In-Reply-To: <A7DEA48C84FD0B48AAAE33F328C020140457EE41@BBY1EXM11.pmc_nt.nt.pmc-sierra.bc.ca>
On Mon, Dec 14, 2009 at 05:34:13AM -0800, Anoop P.A. wrote:
> We have a requirement to use a bigger RAM (1 GB / 2GB) with a RM9000
> based SOC. I thought of going with HIGHMEM path rather than enabling
> 64bit support thinking it will be easier.
This sounds like sawing off 32 legs just to be able to make use of a
free [1] wheelchair.
> I have tried enabling HIGMEM in kernel. Board boots fine with a 512 MB
> RAM plugged in. But if I connect a 1 GB RAM kernel will not boot. I am
> not even getting single print from kernel. I am using linux-2.6.18
> kernel.
>
> It will be great if get any pointers suggestions in debugging this?
With this amount of RAM, use a 64-bit kernel if you can. You'll be
happy not to know about all the headaches you will never encounter.
Ralf
[1] Conditions apply.
next prev parent reply other threads:[~2009-12-14 17:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 11:40 [PATCH 1/9] arch/mips/alchemy: Correct code taking the size of a pointer Julia Lawall
2009-12-14 13:34 ` Help in enabling HIGHMEM support Anoop P.A.
2009-12-14 13:34 ` Anoop P.A.
2009-12-14 17:35 ` Ralf Baechle [this message]
2010-01-18 15:57 ` Help in enabling HIGHMEM support / 64 bit support Anoop P.A.
2010-01-18 15:57 ` Anoop P.A.
2010-01-19 14:55 ` Anoop P.A.
2010-01-19 14:55 ` Anoop P.A.
2010-01-19 15:43 ` Ralf Baechle
2010-01-20 13:03 ` Anoop P.A.
2010-01-20 13:03 ` Anoop P.A.
2009-12-24 13:22 ` [PATCH 1/9] arch/mips/alchemy: Correct code taking the size of a pointer Ralf Baechle
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=20091214173509.GB15067@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Anoop_P.A@pmc-sierra.com \
--cc=linux-mips@linux-mips.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).