linux-kernel - 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-next>] [day] [month] [year] [list]

Date:	Sat, 11 Apr 2015 21:20:33 +0200
From:	"Rowand, Frank" <Frank.Rowand@...ymobile.com>
To:	"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: Invitation and RFC: Linux Plumbers Device Tree track proposed

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

I am looking for several things at the moment:

   1) Suggestions of additional topics to be discussed.

   2) Emails or other messages expressing an interest in attending the
      device tree track.

   3) Commitments to attend the device tree track (the conference committee
      is looking at attendee interest and commitments as part of the process
      of accepting the device tree track).

   4) Identifying additional people who should attend the device tree track.

The desired outcome of the device tree track is to encourage the future
development of tools, process, etc to make device tree related development,
test, review and system administration more efficient, faster, easier, more
robust, and to improve troubleshooting and debugging facilities.  Some
examples of areas of interest could include:
   - make it easier to create correct device tree source files
   - support for debugging incorrect device tree source files
   - create a kernel that correctly boots one or more specific device trees
     (eg a kernel configured to include the proper drivers and subsystems)
   - create drivers that properly work for a device tree binding definition
   - create drivers that support detecting errors in the related node(s) in
     a device tree

The wiki page lists additional areas of interest.

Thanks,

Frank Rowand
Sony Mobile Communications
--
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/