All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Running GRUB under qemu on PowerPC
Date: Wed, 16 Jan 2008 16:52:46 -0500	[thread overview]
Message-ID: <1200520366.6793.14.camel@dv> (raw)
In-Reply-To: <20080116193344.GA2181@thorin>

On Wed, 2008-01-16 at 20:33 +0100, Robert Millan wrote:
> On Wed, Jan 16, 2008 at 01:22:48PM -0500, Pavel Roskin wrote:
> > 
> > I guess the simplest approach would be to assume that we have a certain
> > amount of memory that would be enough for GRUB.
> 
> What a mess.  What does Linux do?  They have to support callbacks to get the
> memory map, so it can't just claim everything.

I don't see any references to "available" in the Linux code, except for
some exotic machines.  Neither does yaboot use anything like that.

yaboot loads under qemu, but hangs trying to load the Linux kernel (both
extracted from the Fedora 8 rescue disk), so I don't know if Linux would
boot.

It seems to me that Linux uses "#size-cells" and "#address-cells" (see
drivers/of/base.c and arch/powerpc/kernel/prom_parse.c)

As for yaboot, I have no idea.  It gets a handle for "/memory" but never
uses it.  I don't see any references to "cells".

> In any case, if you have to make this assumption, considering reusing the
> HEAP_MIN_SIZE macro, which has the same meaning.

OK, I'll try.

-- 
Regards,
Pavel Roskin



  reply	other threads:[~2008-01-16 21:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16  8:19 [PATCH] Running GRUB under qemu on PowerPC Pavel Roskin
2008-01-16 10:40 ` Robert Millan
2008-01-16 18:22   ` Pavel Roskin
2008-01-16 19:33     ` Robert Millan
2008-01-16 21:52       ` Pavel Roskin [this message]
2008-01-16 22:51         ` Robert Millan
2008-01-18  5:07           ` Pavel Roskin
2008-01-18 15:05             ` Robert Millan
2008-01-23 11:07 ` Marco Gerards
2008-01-23 11:22   ` Robert Millan

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=1200520366.6793.14.camel@dv \
    --to=proski@gnu.org \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.