From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: John Williams <john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org>
Cc: Michal Simek
<michal.simek-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org>,
devicetree-discuss
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: Cmdline FDT query tool
Date: Thu, 27 May 2010 15:17:08 +1000 [thread overview]
Message-ID: <20100527051708.GC3603@yookeroo> (raw)
In-Reply-To: <AANLkTikLBDLhSlbLHRCoymDIvbkdU7OVhFnDTpqMXNHt-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Thu, May 27, 2010 at 11:40:51AM +1000, John Williams wrote:
> On Sat, May 22, 2010 at 10:17 AM, David Gibson
> <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org> wrote:
> > On Tue, May 18, 2010 at 12:20:05PM -0600, Grant Likely wrote:
> >> On Mon, May 17, 2010 at 8:03 PM, John Williams
> >> <john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org> wrote:
> >> > Hi Grant,
> >> >
> >> > At ELC I mentioned a tool I'd written that basically hacked u-boot's
> >> > "fdt" command into a commandline util for querying DTBs. You can do
> >> > stuff like this:
> >> >
> >> > $ fdt-tool system.dtp print
> >> >
> >> > <dump entire DTB in text format>
> >> >
> >> > $ fdt-tool system.dtb list /cpus/cpu@0 xlnx,use-dcache
> >> > xlnx,use-dcache = <0x1>
> >> >
> >> > and so on.
> >>
> >> Cool. Thanks John.
> >>
> >> I agree with David. It would probably be useful to include in the
> >> libfdt (which U-Boot fdt support makes use of too) source repo. Seems
> >> like a useful tool.
> >
> > Of course, to incorporate it with libfdt, it would need to be BSD
> > dual-licensed, like the rest of libfdt, and we'd need sign-offs from
> > all authors to that effect.
>
> I have no problem with that, but since I ripped the guts of it
> directly from u-boot there'll be a conversation to be had there.
Ok. Do you have the means to track down the people with whom this
conversation needs to happen?
--
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:[~2010-05-27 5:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 2:03 Cmdline FDT query tool John Williams
[not found] ` <AANLkTilo68Va3EzuWq3SPzv-YpXt-7Ty7Us_Q0Fw_Nmv-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-18 8:53 ` David Gibson
2010-05-18 18:20 ` Grant Likely
[not found] ` <AANLkTinlyoA-FqbtWh939l9qoc6QDnKwPzNVnjgHFcVc-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-22 0:17 ` David Gibson
2010-05-27 1:40 ` John Williams
[not found] ` <AANLkTikLBDLhSlbLHRCoymDIvbkdU7OVhFnDTpqMXNHt-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-27 5:17 ` David Gibson [this message]
2010-05-27 5:35 ` John Williams
[not found] ` <AANLkTinJGSz_1bNK8y3JTwqkseU5dg8oIdvT7ir7Mq6u-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-27 6:23 ` David Gibson
2010-06-21 1:50 ` John Williams
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=20100527051708.GC3603@yookeroo \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org \
--cc=michal.simek-g5w7nrANp4BDPfheJLI6IQ@public.gmane.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