From: David Gibson <david@gibson.dropbear.id.au>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>
Subject: Re: Virtex device tree generator proof of concept
Date: Thu, 7 Dec 2006 10:47:57 +1100 [thread overview]
Message-ID: <20061206234757.GD17446@localhost.localdomain> (raw)
In-Reply-To: <528646bc0612061514mbcb2627wbe83cd47a06b31b9@mail.gmail.com>
Hmm.. I seem to have missed the beginning of this thread, somehow.
On Wed, Dec 06, 2006 at 04:14:33PM -0700, Grant Likely wrote:
> On 12/6/06, Stephen Neuendorffer <stephen.neuendorffer@xilinx.com> wrote:
> >
> > Hi Grant,
> >
> > This looks really cool... I've hacked around in it a bit to generate
> > device trees that go more completely through dtc. (I'd be happy
> > to push these modifications back to you, if you're interested...)
>
> Yes please, send me your patches.
>
> >
> > I'm curious if you've heard of anyone using device trees other than
> > at boot time: for instance, using an incomplete device tree blob to
> > represent components discovered at runtime? It looks like it should
> > be possible to rip out alot of the code from kernel/powerpc/prom.c in
> > recent kernels to parse incomplete device trees, too... Any thoughts?
That reminds me: I was definitely thinking about implementing a
"graft" function in libfdt for merging a tree from one blob into
another.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2006-12-06 23:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <977C41F842E66D4CB2E41332313B615002F76196@XSJ-EXCHVS1.xlnx.xilinx.com>
2006-12-06 23:14 ` Virtex device tree generator proof of concept Grant Likely
2006-12-06 23:47 ` David Gibson [this message]
2006-12-07 0:19 Stephen Neuendorffer
-- strict thread matches above, loose matches on Subject: below --
2006-11-29 19:16 Grant Likely
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=20061206234757.GD17446@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=stephen.neuendorffer@xilinx.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 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.