From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx.com>,
"linuxppc-dev list" <linuxppc-dev@ozlabs.org>
Subject: Re: Virtex device tree generator proof of concept
Date: Wed, 6 Dec 2006 16:14:33 -0700 [thread overview]
Message-ID: <528646bc0612061514mbcb2627wbe83cd47a06b31b9@mail.gmail.com> (raw)
In-Reply-To: <977C41F842E66D4CB2E41332313B615002F76196@XSJ-EXCHVS1.xlnx.xilinx.com>
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?
Possible, but there are probably better ways do deal with those; like
just allocating and registering a platform device; or adding nodes to
the existing tree. If you're able to probe a device, then do you need
to describe it with a device tree fragment?
What scenario are you thinking about?
Cheers,
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next parent reply other threads:[~2006-12-06 23:14 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 ` Grant Likely [this message]
2006-12-06 23:47 ` Virtex device tree generator proof of concept David Gibson
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=528646bc0612061514mbcb2627wbe83cd47a06b31b9@mail.gmail.com \
--to=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 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).