All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Running GRUB under qemu on PowerPC
Date: Fri, 18 Jan 2008 16:05:53 +0100	[thread overview]
Message-ID: <20080118150553.GA16187@thorin> (raw)
In-Reply-To: <1200632851.9493.6.camel@dv>

On Fri, Jan 18, 2008 at 12:07:31AM -0500, Pavel Roskin wrote:
> 
> On Wed, 2008-01-16 at 23:51 +0100, Robert Millan wrote:
> > On Wed, Jan 16, 2008 at 04:52:46PM -0500, Pavel Roskin wrote:
> > > 
> > > It seems to me that Linux uses "#size-cells" and "#address-cells" (see
> > > drivers/of/base.c and arch/powerpc/kernel/prom_parse.c)
> > 
> > We use "#size-cells" and "#address-cells" too, but they aren't useful by
> > themselves.  They describe the layout of /memory/available.
> > 
> > See kern/powerpc/ieee1275/openfw.c:grub_available_iterate()
> 
> As I understand, Linux uses "ranges", although it's hard to be sure.
> There are many references to "ranges" in Linux sources under
> arch/powerpc, although many of them are pertinent to buses rather than
> to the system memory.  Open Hack'Ware provides "ranges" for the memory.

/memory/available is organized in ranges (address, whose length is described
by #address-cells, and size, whose length is described by #size-cells).  Is
that what you mean?

> As for yaboot, it uses "claim" both for its needs and for loading the
> kernel.  And that's probably what GRUB could do.

It is:

loader/powerpc/ieee1275/linux.c:      found_addr = grub_claimmap (linux_addr, linux_size);
loader/powerpc/ieee1275/multiboot2.c:  rc = grub_claimmap (phdr->p_paddr, phdr->p_memsz);

-- 
Robert Millan

<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call… if you are unable to speak?
(as seen on /.)



  reply	other threads:[~2008-01-18 15:07 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
2008-01-16 22:51         ` Robert Millan
2008-01-18  5:07           ` Pavel Roskin
2008-01-18 15:05             ` Robert Millan [this message]
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=20080118150553.GA16187@thorin \
    --to=rmh@aybabtu.com \
    --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.