linux-kernel - Re: [Celinux-dev] Invitation and RFC: Linux Plumbers Device Tree track proposed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 4 May 2015 18:20:35 -0500
From:	Rob Herring <robherring2@...il.com>
To:	Rob Landley <rob@...dley.net>
Cc:	"Rowand, Frank" <Frank.Rowand@...ymobile.com>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"devicetree-compiler@...r.kernel.org" 
	<devicetree-compiler@...r.kernel.org>,
	"linux-embedded@...r.kernel.org" <linux-embedded@...r.kernel.org>,
	"celinux-dev@...ts.celinuxforum.org" 
	<celinux-dev@...ts.celinuxforum.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [Celinux-dev] Invitation and RFC: Linux Plumbers Device Tree
 track proposed

On Fri, May 1, 2015 at 4:22 PM, Rob Landley <rob@...dley.net> 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.

> 2) Feed one of the dtb files to qemu to instantiate a bunch of devices.

I'd like this too. The QEMU maintainers don't really agree. I think
the ARM virt platform is the wrong way around with QEMU generating the
DT. There was a patch series to allow sysbus devices to be created on
the command line like you can with PCI. This would have allowed a
front end script to generate a QEMU command line from a DT. I'm not
sure if it ever got in.

It would lower the bar to adding new platforms to just writing models
for blocks perhaps. I'm not sure there's enough interest. The number
of ARM platforms supported in QEMU is much less than the kernel.

Rob

[1] https://git.kernel.org/cgit/linux/kernel/git/devicetree/devicetree-rebasing.git/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/