linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Chandru <chandru@in.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: device tree in open firmware on power6
Date: Thu, 8 May 2008 16:32:50 +1000	[thread overview]
Message-ID: <18466.40594.804958.249766@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <48229BF5.9090602@in.ibm.com>

Chandru writes:

> When I set linux 2.6.26-rc1 as default kernel to boot in 
> /etc/yaboot.conf, then the device tree in open firmware shows only one 
> memory node ( the same memory node appears in /proc/device-tree/memory@0 
> ).  But when RHEL5.2 kernel is set as default in /etc/yaboot.conf then 
> the device tree in open firmware shows plenty of memory nodes. Following 
> is the open firmware output..

Current kernels tell the firmware that they can handle having memory
represented in the /ibm,dynamic-reconfiguration-memory node, which is
a more compact representation than having it represented in multiple
/memory@xxx nodes.  Therefore firmware reports most of the memory in
the /ibm,dynamic-reconfiguration-memory node you have here:

> linux-2.6.26-rc1:
> 
> <snip>
> 0 > dev / ls
> ...
> 000000caf1b8:   /PowerPC,POWER6@6
> 000000cb0120: /memory@0
> 000000cb83d8: /ibm,dynamic-reconfiguration-memory

and only gives you one /memory@xxx node, which represents the real
memory area.  See sections C.6.2.3 and C.6.6.2 of PAPR for more
information.

Paul.

      reply	other threads:[~2008-05-08  6:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08  6:21 device tree in open firmware on power6 Chandru
2008-05-08  6:32 ` Paul Mackerras [this message]

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=18466.40594.804958.249766@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=chandru@in.ibm.com \
    --cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).