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 / 64 bit support
Date: Tue, 19 Jan 2010 16:43:19 +0100 [thread overview]
Message-ID: <20100119154319.GB23161@linux-mips.org> (raw)
In-Reply-To: <A7DEA48C84FD0B48AAAE33F328C020140474ADC8@BBY1EXM11.pmc_nt.nt.pmc-sierra.bc.ca>
On Mon, Jan 18, 2010 at 07:57:06AM -0800, Anoop P.A. wrote:
> I am working on enabling Highmem support and 64 Bit support
>
> 1. 64 Bit support
>
> As Ralf suggested I have tried enabling 64 bit support. I have reached
> up to a point where I can boot the kernel with 512MB memory (logs
> attached). How ever if I increase mem above > 512 I am not even getting
> single print from kernel.
You told the kernel mem=1024M. That's memory at physical address zero
so overlaps with I/O address ranges. Boom. The reason that you for
further with highmem is the same except except that probably by pure luck
the allocation order got things to fail a little later.
To debug this sort of case I suggest you get early printk to work for your
board or maybe you have a working EJTAG probe and debugger.
Btw, what is the point of putting ASCII boot logs into word files inflating
them 10x and getting half the mail filters of this world to throw the
attachments or entire email away?
Ralf
next prev parent reply other threads:[~2010-01-19 17:08 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
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 [this message]
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=20100119154319.GB23161@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).