linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [ARM ATTEND] general discussion, DT (fragments?) and TrustZone
Date: Fri, 28 Mar 2014 17:35:24 +0100	[thread overview]
Message-ID: <5335A4CC.2000406@atmel.com> (raw)

Hi,

I am Atmel AT91 Co-Maintainer and would like to attend the ARM Linux
mini-summit or BoF. I will be attending ELC as well.

I'd love to discuss the following topics with you guys:

- current effort toward AT91 DT conversion, where do we stand, what
  are the future plans and what are the best ways to move
  old platforms to DT-only

- integration of AT91 to ARM multiplatform initiative. Following our
  adoption of CCF, I would like to summarize what is remaining to be
  done before integrating the multiplatform single zImage kernel

- best DT practices for handling little differences in
  hardware platforms:
  - subtle HW changes in relation to board revisions
  - addition of daughter boards, modules, capes, shields
  - use of DT fragments: status, best practices,
    location of DT fragments
  Without a proper mechanism we quickly observe a huge amount
  of different .dtsi/.dts files popping up!

- TrustZone and the Linaro Open Source Trusted Execution Environment:
  how ARM Linux will interact with this initiative and which part of
  the Linux kernel would implement the calls to the TEE API.


Thanks, bye.
-- 
Nicolas Ferre

                 reply	other threads:[~2014-03-28 16:35 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=5335A4CC.2000406@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=linux-arm-kernel@lists.infradead.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).