linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, linuxppc64-dev@ozlabs.org
Subject: Re: Merging ppc32 and ppc64
Date: Wed, 10 Aug 2005 12:51:25 +0200	[thread overview]
Message-ID: <1123671086.30257.231.camel@gaston> (raw)
In-Reply-To: <17145.12993.672427.466466@cargo.ozlabs.ibm.com>


> Having the flattened device tree doesn't mean that we will be using
> the device tree less, it means we will be using it _more_.

The reason Segher is freaking out is because he wants to keep OF alive
in the future while the kernel is running.... (at least with SLOF)

I think that would require a different entry point with no flattened
tree, and changing of all the OF accessors to call OF instead of walking
an in-kernel tree. That is far from our current target though.

Ben.

  reply	other threads:[~2005-08-10 10:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03  3:07 Merging ppc32 and ppc64 Paul Mackerras
2005-08-03  5:48 ` Fwd: " Kumar Gala
2005-08-08 17:59 ` Joel Schopp
2005-08-08 23:48   ` Paul Mackerras
2005-08-09 13:09   ` Segher Boessenkool
2005-08-09 13:11     ` Geert Uytterhoeven
2005-08-09 13:30       ` Segher Boessenkool
2005-08-09 14:12         ` Kumar Gala
2005-08-09 14:47           ` Arnd Bergmann
2005-08-09 15:01             ` Kumar Gala
2005-08-09 16:21               ` Tom Rini
2005-08-09 17:41                 ` Kumar Gala
2005-08-09 17:47                   ` Tom Rini
2005-08-09 18:49                     ` Kumar Gala
2005-08-09 15:16           ` Segher Boessenkool
2005-08-09 22:55         ` Paul Mackerras
2005-08-09 23:00           ` Kumar Gala
2005-08-10 10:15           ` Segher Boessenkool
2005-08-09 14:52     ` Olof Johansson
2005-08-09 22:48     ` Paul Mackerras
2005-08-10 10:51       ` Benjamin Herrenschmidt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-04  2:37 Goodman, Brad

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=1123671086.30257.231.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc64-dev@ozlabs.org \
    --cc=paulus@samba.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).