Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Florian Lohoff <flo@rfc822.org>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: kernel hang indigo2 current cvs more specific
Date: Tue, 4 Apr 2000 21:02:57 +0200	[thread overview]
Message-ID: <20000404210257.A1517@paradigm.rfc822.org> (raw)
In-Reply-To: <Pine.GSO.4.10.10004041057310.24463-100000@dandelion.sonytel.be>; from Geert Uytterhoeven on Tue, Apr 04, 2000 at 10:59:43AM +0200

On Tue, Apr 04, 2000 at 10:59:43AM +0200, Geert Uytterhoeven wrote:
> 
> Perhaps this helps: the bootmem stuff in arch/mips/ddb5074/prom.c works fine.
> The DDB5074 has 64 MB of fixed non-upgradable memory at physical 0x00000000
> virtual 0x80000000.

Do you or anyone else have a clue why i cant find anything like this

    bootmap_size = init_bootmem(start_pfn, mem_size >> PAGE_SHIFT);

    /* Free the entire available memory after the _end symbol.  */
    free_start += bootmap_size;
    free_bootmem(free_start, free_end-free_start);

in the arch/mips/sgi/kernel/ directory ? Could it be that this structure
is new and has never been implemented for the IP22 ?

Yep - Thats it - In 2.3.21 this init_bootmem thing doesnt exists - And though
dec hasnt got it - In 2.3.99pre3 the dec has it - But not the sgi *grrrrr*

Flo
-- 
Florian Lohoff		flo@rfc822.org		      	+49-5241-470566
"Technology is a constant battle between manufacturers producing bigger and
more idiot-proof systems and nature producing bigger and better idiots."

  reply	other threads:[~2000-04-04 19:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-03 23:54 kernel hang indigo2 current cvs more specific Florian Lohoff
2000-04-04  8:22 ` Florian Lohoff
2000-04-04  8:59   ` Geert Uytterhoeven
2000-04-04 19:02     ` Florian Lohoff [this message]
2000-04-04 19:11       ` Florian Lohoff
2000-04-04 20:34     ` Florian Lohoff

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=20000404210257.A1517@paradigm.rfc822.org \
    --to=flo@rfc822.org \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=linux@cthulhu.engr.sgi.com \
    /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