linux-mips
[Top] [All Lists]

Re: something not really right ..

To: Ralf Baechle <ralf@uni-koblenz.de>
Subject: Re: something not really right ..
From: "William J. Earl" <wje@fir.engr.sgi.com>
Date: Sun, 11 Jan 1998 20:24:50 -0800
Cc: Shrijeet Mukherjee <shm@cthulhu.engr.sgi.com>, Linux porting team <linux@cthulhu.engr.sgi.com>
In-reply-to: <19980110120428.62352@thoma.uni-koblenz.de>
References: <Pine.SGI.3.94.980109200218.2493B-100000@tantrik.engr.sgi.com> <19980110120428.62352@thoma.uni-koblenz.de>
Sender: owner-linux@cthulhu.engr.sgi.com
Ralf Baechle writes:
 > On Fri, Jan 09, 1998 at 08:04:57PM -0800, Shrijeet Mukherjee wrote:
 > > 
 > > I tried to compile the latest sources for an Indigo R4k .. with minimal
 > > functionality .. i.e. most of the newer stuff has been left out.
 > > 
 > > after the compilation, trying to bring the machine up by serving the
 > > kernel via NFS/BOOTP gets me this message 
 > > 
 > > sash
 > > "unable to execute bootp()tantrik:/usr/local/boot/vmlinux: Not enough
 > > space"
 > > "unable to load bootp()tantrik:/usr/local/boot/vmlinux: Not enough space"
 > > sash
 > 
 > Did you modify the load address of the kernel?  Indy kernels are by
 > default linked for address 0x88002000 because the Indy has a 128mb
 > hole in it's address space there.  I assumes (wje???) that your box
 > has it's memory mapped from 0x80000000 upwards, so this would only
 > work if you actually have that more than 128mb ...
 > 

     Indy and Indigo R40000 both have the hole at the bottom of the
address space, so main memory is mapped starting at 0x88000000, with
512 KB double-mapped at 0x80000000.


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