LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: Flattened device tree for Pegasos
Date: Tue, 14 Feb 2006 09:27:08 +1100	[thread overview]
Message-ID: <1139869628.5237.18.camel@localhost.localdomain> (raw)
In-Reply-To: <20060213180320.GB4530@mag.az.mvista.com>

On Mon, 2006-02-13 at 11:03 -0700, Mark A. Greer wrote:
> On Mon, Feb 13, 2006 at 09:12:12AM +1100, Benjamin Herrenschmidt wrote:
> > On Fri, 2006-02-10 at 18:46 -0600, Kumar Gala wrote:
> > > On Fri, 10 Feb 2006, Mark A. Greer wrote:
> > > 
> > > > If anyone happens to have a Pegasos running the merged powerpc kernel
> > > > handy, I would greatly appreciate a dump of flattened device tree that
> > > > it uses.
> > > 
> > > We really need to put OF tree's somewhere that people can get to, maybe 
> > > penguinppc.org.
> > > 
> > > Ben, Segher, Paul:
> > > 
> > > You guys have either access to HW or tree dump's already.  Would you be 
> > > willing to share them?
> > 
> > There is an unresolved issue about what is the (c) for those
> > device-tree, especially since the Apple ones may contain driver blobs...
> 
> Is that still an issue for the flattened dev tree version(s)?
> 
> I'd still like a flattened dev tree for the pegasos if that's legal. :)

The issue is the (c) of Apple trees mostly... that is, I don't think I
can post my collection of Apple device-tree snapshots online.

Ben.

      reply	other threads:[~2006-02-13 22:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-11  0:48 Flattened device tree for Pegasos Mark A. Greer
2006-02-11  0:46 ` Kumar Gala
2006-02-11  0:58   ` Mark A. Greer
2006-02-12 22:12   ` Benjamin Herrenschmidt
2006-02-13 18:03     ` Mark A. Greer
2006-02-13 22:27       ` Benjamin Herrenschmidt [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=1139869628.5237.18.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=mgreer@mvista.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