| To: | "Maciej W. Rozycki" <macro@ds2.pg.gda.pl> |
|---|---|
| Subject: | Re: crash in __alloc_bootmem_core on SGI current cvs |
| From: | Ralf Baechle <ralf@oss.sgi.com> |
| Date: | Tue, 16 Jan 2001 17:23:51 -0200 |
| Cc: | Florian Lohoff <flo@rfc822.org>, linux-mips@oss.sgi.com |
| In-reply-to: | <Pine.GSO.3.96.1010116172956.5546O-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Tue, Jan 16, 2001 at 05:34:45PM +0100 |
| References: | <20010116142449.B13302@bacchus.dhis.org> <Pine.GSO.3.96.1010116172956.5546O-100000@delta.ds2.pg.gda.pl> |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.2.5i |
On Tue, Jan 16, 2001 at 05:34:45PM +0100, Maciej W. Rozycki wrote: > > The Indy has it's memory starting at phys. 0x08000000; a part of it is also > > mirrored at physical address zero. So in case of an Indy the totalpages > > number should indicate 128mb too much which means that Flo's machine should > > have only 128mb real memory. Right Florian? > > The memory map suggests it is so. > > But how does the Indy handle our kernel being linked at 0x80000000? Does > the kernel always fit the mirrored area? Indy kernels are linked to 0x88002000. Ralf |
| Previous by Date: | Re: crash in __alloc_bootmem_core on SGI current cvs, Ralf Baechle |
|---|---|
| Next by Date: | Current CVS (010116) Boots OK, Ian Chilton |
| Previous by Thread: | Re: crash in __alloc_bootmem_core on SGI current cvs, Maciej W. Rozycki |
| Next by Thread: | Re: crash in __alloc_bootmem_core on SGI current cvs, Maciej W. Rozycki |
| Indexes: | [Date] [Thread] [Top] [All Lists] |