linux-mips
[Top] [All Lists]

Re: Help in enabling HIGHMEM support / 64 bit support

To: "Anoop P.A." <Anoop_P.A@pmc-sierra.com>
Subject: Re: Help in enabling HIGHMEM support / 64 bit support
From: Ralf Baechle <ralf@linux-mips.org>
Date: Tue, 19 Jan 2010 16:43:19 +0100
Cc: linux-mips@linux-mips.org
In-reply-to: <A7DEA48C84FD0B48AAAE33F328C020140474ADC8@BBY1EXM11.pmc_nt.nt.pmc-sierra.bc.ca>
References: <Pine.LNX.4.64.0912131240100.24267@ask.diku.dk> <A7DEA48C84FD0B48AAAE33F328C020140457EE41@BBY1EXM11.pmc_nt.nt.pmc-sierra.bc.ca> <20091214173509.GB15067@linux-mips.org> <A7DEA48C84FD0B48AAAE33F328C020140474ADC8@BBY1EXM11.pmc_nt.nt.pmc-sierra.bc.ca>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.20 (2009-08-17)
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

<Prev in Thread] Current Thread [Next in Thread>