linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-embedded-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	celinux-dev-idqoXFIVOFIh9xQPArXXUATG8MYbGj4l@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Device Tree at Plumbers, looking for topics and session leaders
Date: Sat, 30 May 2015 14:39:24 -0700	[thread overview]
Message-ID: <556A2E0C.7050702@gmail.com> (raw)

I am looking for additional topics to include in the device tree track
at Plumbers 2015.

I am also soliciting people who would like to be session leaders or
scribes.

I have a limited number of free registration discounts available for
session leaders / presenters.

The format at Plumbers is less about presentations and more about
discussions.  So enough slides and presentation to set the foundation
of the discussion.  Then lots of talking.

The role of the session leader is to
  - present a balanced description of the topic / subject area
  - ensure multiple view points and alternatives are heard

If you want to help shape the future of device tree, then your
role as a member of the audience is to talk.  To provide ideas,
inspiration, your experiences, how the world you live in may be
different than the one that I live in.

The track description is:

  The Linux Plumbers 2015 Device Tree Tools, Validation, and
  Troubleshooting track focuses on tools (programs and scripts),
  techniques, and core support to enable creation of correct device
  trees and to support troubleshooting and debugging of incorrect
  device trees, drivers, and subsystems.

  The tools encompass static (build and pre-boot) and dynamic (boot and
  run-time) environments.

  Areas of interest include

    - inspection
    - verification and validation
    - troubleshooting
    - debugging
    - core support for debugging
    - unit tests
    - designing and implementing drivers for effective debugging
    - impact of overlays (boot and run-time updates to the device tree)
    - bindings
    - documentation

  Topics unrelated to the overall track but of current Device Tree
  interest may be accepted if there is available time

    - ordering of device creation and driver binding

Please contact me if you plan to attend the device tree track.  If
you are also attending other tracks, please list those tracks so that
the Plumbers planning committee can try to minimize the schedule
conflicts between tracks.

General information about plumbers is at:

   http://linuxplumbersconf.org/2015/

Plumbers will be co-located with LinuxCon North America in Seattle
(Plumbers is Aug 19-21, Linuxcon is Aug 17-19).


Hope to see many of you in Seattle.

Regards,

Frank Rowand

                 reply	other threads:[~2015-05-30 21:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=556A2E0C.7050702@gmail.com \
    --to=frowand.list-re5jqeeqqe8avxtiumwx3w@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 \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).