From: Geert Uytterhoeven <geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>
To: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Rob Landley <rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org>,
"Rowand,
Frank" <Frank.Rowand-/MT0OVThwyLZJqsBc5GL+g@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-embedded-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-embedded-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"celinux-dev-idqoXFIVOFIh9xQPArXXUATG8MYbGj4l@public.gmane.org"
<celinux-dev-idqoXFIVOFIh9xQPArXXUATG8MYbGj4l@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [Celinux-dev] Invitation and RFC: Linux Plumbers Device Tree track proposed
Date: Tue, 5 May 2015 09:34:08 +0200 [thread overview]
Message-ID: <CAMuHMdV7xfbBYL5fhudObdwNVJ0L_1_h0ozT+U4Lpx=Mu9UGhw@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqKkZYEMdYmh=JkA6O34a+7mKy=SgB2XxzgTM70mihgQeQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Rob
On Tue, May 5, 2015 at 1:20 AM, Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> On Fri, May 1, 2015 at 4:22 PM, Rob Landley <rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org> 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?
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2015-05-05 7:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-11 19:20 Invitation and RFC: Linux Plumbers Device Tree track proposed Rowand, Frank
[not found] ` <8251B150E4DF5041A62C3EA9F0AB2E0603A53FE1082E-6yWnlZQfN9JoBVljSLT0Ysm4BeyDBExM@public.gmane.org>
2015-04-12 0:05 ` Rob Landley
[not found] ` <CAOS_Y6Qmt2KTRu6urPs-Y1e2Xv1QPNTaQHH4_N8Kk8XU7n+ecQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-12 7:53 ` [Celinux-dev] " Geert Uytterhoeven
2015-04-13 5:13 ` David Gibson
2015-04-14 15:36 ` Rob Herring
[not found] ` <CAL_JsqL0FdvKtGTxFNYxtrGWkm3z-1m0v9dHwYezCtkFOW6EgQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-14 17:14 ` Mark Rutland
2015-04-14 20:58 ` Arnd Bergmann
2015-05-26 16:31 ` Jon Loeliger
2015-05-01 13:32 ` Matt Porter
2015-05-01 21:22 ` [Celinux-dev] " Rob Landley
[not found] ` <5543EE80.5060109-VoJi6FS/r0vR7s880joybQ@public.gmane.org>
2015-05-02 7:51 ` Geert Uytterhoeven
2015-05-04 23:20 ` [Celinux-dev] " Rob Herring
[not found] ` <CAL_JsqKkZYEMdYmh=JkA6O34a+7mKy=SgB2XxzgTM70mihgQeQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-05 7:34 ` Geert Uytterhoeven [this message]
[not found] ` <CAMuHMdV7xfbBYL5fhudObdwNVJ0L_1_h0ozT+U4Lpx=Mu9UGhw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-05 19:32 ` Rob Herring
2015-05-06 3:28 ` [Celinux-dev] " David Gibson
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='CAMuHMdV7xfbBYL5fhudObdwNVJ0L_1_h0ozT+U4Lpx=Mu9UGhw@mail.gmail.com' \
--to=geert-td1emuhucqxl1znqvxdv9g@public.gmane.org \
--cc=Frank.Rowand-/MT0OVThwyLZJqsBc5GL+g@public.gmane.org \
--cc=celinux-dev-idqoXFIVOFIh9xQPArXXUATG8MYbGj4l@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-embedded-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org \
--cc=robherring2-Re5JQEeQqe8AvxtiuMwx3w@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;
as well as URLs for NNTP newsgroup(s).