From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Loeliger <jdl@freescale.com>
Cc: "linuxppc-embedded@ozlabs.org" <linuxppc-embedded@ozlabs.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: Booting the linux-ppc64 kernel & flattened device tree v0.4
Date: Thu, 02 Jun 2005 07:56:48 +1000 [thread overview]
Message-ID: <1117663009.19020.61.camel@gaston> (raw)
In-Reply-To: <1117645131.6517.31.camel@cashmere.sps.mot.com>
On Wed, 2005-06-01 at 11:58 -0500, Jon Loeliger wrote:
> On Wed, 2005-06-01 at 03:26, Benjamin Herrenschmidt wrote:
> > Here's the fourth version of my document along with new kernel patches
> > for the new improved flattened format, and the first release of the
> > device-tree "compiler" tool. The patches will be posted as a reply to
> > this email. The compiler, dtc, can be downloaded, the URL is in the
> > document.
>
> Ben,
>
> Does it make sense to do this as well?
You mean include lsprop ? Well, I have another version of lsprop hacked
here that can generate a "source", but dtc can do it too now ... I think
we may just make dtc able to output in "lsprop" format too :) But I'll
talk to david (CC'd, he's the author of dtc).
Ben.
next prev parent reply other threads:[~2005-06-01 21:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 8:26 Booting the linux-ppc64 kernel & flattened device tree v0.4 Benjamin Herrenschmidt
2005-06-01 8:28 ` Benjamin Herrenschmidt
2005-06-03 7:18 ` Benjamin Herrenschmidt
2005-06-03 17:19 ` Discuss: Adding OF Flat Dev Tree to ppc32 Jon Loeliger
2005-06-08 3:06 ` Benjamin Herrenschmidt
2005-06-15 19:00 ` Jon Loeliger
2005-06-15 21:52 ` Benjamin Herrenschmidt
2005-06-21 23:41 ` Tom Rini
2005-06-01 16:58 ` Booting the linux-ppc64 kernel & flattened device tree v0.4 Jon Loeliger
2005-06-01 21:56 ` Benjamin Herrenschmidt [this message]
2005-06-01 19:54 ` Jon Loeliger
2005-06-01 21:58 ` Benjamin Herrenschmidt
2005-06-02 7:09 ` David Gibson
2005-06-03 8:19 ` David Gibson
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=1117663009.19020.61.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=jdl@freescale.com \
--cc=linuxppc-embedded@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).