Hi Rob

On Tue, May 5, 2015 at 1:20 AM, Rob Herring <robherring2@...> wrote:

On Fri, May 1, 2015 at 4:22 PM, Rob Landley <rob@...> wrote:

On 04/11/2015 02:20 PM, Rowand, Frank wrote:

In recent years there have been proposed tools to aid in the creation of valid
device trees and in debugging device tree issues. An example of this is the
various approaches proposed (with source code provided) to validate device tree
source against valid bindings. As of today, device tree related tools,
techniques, and debugging infrastructure have not progressed very far. I have
submitted a device tree related proposal for the Linux Plumbers 2015 conference
to spur action and innovation in such tools, techniques, and debugging
infrastructure.

The current title of the track is "Device Tree Tools, Validation, and
Troubleshooting". The proposal is located at

http://wiki.linuxplumbersconf.org/2015:device_tree_tools_validation_and_trouble_shooting

Want I want to do is:

1) Download an archive of device tree files describing a bunch of
boards. (Both dts and corresponding dtb files, with maybe a .txt telling
me about the board and the -append line qemu needs to give it any
board-specific kernel command line stuff like "console=myserialport".)

The dts half is here[1]. It is a kernel repository automatically
stripped of everything but dts files.

[1] https://git.kernel.org/cgit/linux/kernel/git/devicetree/devicetree-rebasing.git/

Great!

While "git log" has the "--nomerges" option, cgit hasn't, making it hard to see
the actual changes through the forest of merges.

Any chance merge commits not causing any changes can be stripped out, too?