From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Scott Wood" <scottwood@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Printing device tree on running system
Date: Thu, 20 Sep 2007 12:21:30 -0400 [thread overview]
Message-ID: <9e4733910709200921u3ffd6a37pe0ef268a2a171973@mail.gmail.com> (raw)
In-Reply-To: <20070920160804.GA15796@ld0162-tx32.am.freescale.net>
On 9/20/07, Scott Wood <scottwood@freescale.com> wrote:
> On Thu, Sep 20, 2007 at 11:55:10AM -0400, Jon Smirl wrote:
> > Is there a command for printing the device tree on a running system? I
> > want to see what changes the various device drivers made to the DTC I
> > started with.
>
> It's exported in /proc/device-tree, if support is built into the kernel.
That worked, didn't know the option existed.
>
> It might be interesting to make dtc support turning that into a dts...
That would be useful, you could do a diff and see how the tree was altered.
The case I just looked at was old code manually building entries for
i2c devices in the tree, but with an updated dts the devices are
already in the tree which explains the error I got about conflicting
device nodes.
>
> -Scott
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2007-09-20 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 15:55 Printing device tree on running system Jon Smirl
2007-09-20 16:08 ` Scott Wood
2007-09-20 16:21 ` Jon Smirl [this message]
2007-09-20 4:57 ` Josh Boyer
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=9e4733910709200921u3ffd6a37pe0ef268a2a171973@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=scottwood@freescale.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).