From: Steve McIntyre <steve.mcintyre-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: dte-all-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
Subject: Device Tree Evolution Project - call notes - 22nd April
Date: Wed, 22 Apr 2020 18:21:38 +0100 [thread overview]
Message-ID: <20200422172138.GA30250@linaro.org> (raw)
Hi folks!
I'm sharing the notes from our regular meeting that was held
yesterday. We had quite a lot of updates around what we're doing, as
Linaro is just starting the new BUD20 cycle.
More details about the meeting etc. at the end.
Administrative note: this was my last call as tech lead for the DTE
project. I'm leaving my job at Arm and Linaro, off to pastures
new. Somebody else will be picking up the DTE project work. More news
on that soon I hope - watch this space.
Attendees
=========
SteveM - Arm
MarkB - Arm
RobH - Arm
GrantL - Arm
BillF - Linaro
ArndB - Linaro
JensW - Linaro
IliasA - Linaro
VincentG - Linaro
StefanoS - Xilinx
BruceA - Xilinx
LoicP - ST
AlexandreT - ST
cvs - ??
Notes
=====
1. Steve's last call
a. Somebody else will hopefully pick up before the next meeting
2. Arnd has set up a shared central repo for some projects to use
a. already done, just not in public - hosted on github alongside
the devicetree spec and website repos
b. name undecided - let's go with "devicetree-source"
c. He's going to start working with the U-Boot folks to see how to
use that
d. Will be pulling in changes from Linux, updating by release cycle
rather than automatically
e. We'll integrate automated schema checking here
f. Jens looking to start on OP-TEE then TF-A, using this tree too
1. OP-TEE already uses multiple git repos, so adding another one
sounds easy enough
3. Alexandre looking to continue the DT ID at runtime work
a. Waiting on a question to David Gibson, working through review
from the last version of the patch
4. LITE has an engineer lined up for RTOS work, should be introduced
soon
5. System DT update
a. Working out spec updates to allow definition of bus firewalls
b. Lopper ready for an alpha release - git repo on the same
devicetree-org github account should be ready to go ASAP
Background information about DTE
================================
Linaro engineers are working on a range of initiatives in the DT
space, collected together as a project called Device Tree Evolution
(DTE). We hold a discussion call every second Wednesday at 1600 UTC /
1700 BST / 1200 EDT / 0900 PDT. If you would like to be invited,
please ask me (Steve McIntyre).
This is a summary of the notes from the most recent meeting. I aim to
tidy up and post the meeting notes shortly after each meeting. The raw
notes are published at
https://docs.google.com/document/d/e/2PACX-1vRVDrVFWjIOascqZFCO--T8pIqyFB_MDh9cvgyoqhI6Y0tqaA9TcCcvQhcmxi5IY7CG44JfIrCdAUDL/pub
For more information about DTE, see:
* https://www.linaro.org/engineering/core/devicetree-evolution/
* https://www.linaro.org/assets/pdf/Linaro-White-Paper--Device-Tree-Evolution.pdf
Cheers,
--
Steve McIntyre steve.mcintyre-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs
reply other threads:[~2020-04-22 17:21 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=20200422172138.GA30250@linaro.org \
--to=steve.mcintyre-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dte-all-QSEj5FYQhm4dnm+yROfE0A@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).