From: Steve McIntyre <steve.mcintyre-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
dte-all-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
system-dt-ZwoEplunGu1b+pB8xrm1Mtaxn9tAw+E3@public.gmane.org
Cc: Grant Likely <Grant.Likely-5wv7dgnIgG8@public.gmane.org>,
Arnd Bergmann <arnd-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
Frank Rowand
<frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Rob Herring <Rob.Herring-5wv7dgnIgG8@public.gmane.org>,
Mark Brown <mark.brown-5wv7dgnIgG8@public.gmane.org>,
Stefano Stabellini
<stefanos-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
Bruce Ashfield
<bruce.ashfield-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
Benjamin Gaignard
<benjamin.gaignard-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: System DT - thinking a sprint would help
Date: Thu, 6 Feb 2020 15:59:07 +0000 [thread overview]
Message-ID: <20200206155907.GQ6796@tack.einval.com> (raw)
Hi all!
[ tl;dr - we're trying to organise a sprint - see the end ]
Due to the Linux on Arm meetup this week, quite a few of our DT
community happened to be in Cambridge together last night. We took the
opportunity to get together for food and beer, and we naturally ended
up mulling over a whole range of things, not least the ongoing System
DT design work.
As is the nature of this kind of gathering, we had a whole range of
opinions and ideas, much more than I can faithfully recall to share
here in great detail. Grant has been keen to try and keep system-dt
compatible with Linux DT usage if that's possible, and Stefano has
been working with that in mind. Rob is concerned about how things
might scale with lots of domains, for example. Olof is keen to talk
about a higher-level design to make it easier to express complex
layouts. And so on.
There is one thing that *did* stand out: we agreed that it's probably
time to try and get all of the interested people in a room together
for a few days with a whiteboard, to really thrash out what's needed
and how to achieve it. With the right people, we can go through all
our needs, pick up the ideas we have and hopefully get some prototypes
ready to evaluate.
So, who's interested? I believe all the people in CC here are likely
keen to be involved. Anybody else?
Although we have Linaro Connect in Budapest at the end of March,
that's really *not* a good place to try and meet up, for a couple of
reasons: not everybody will be there, and we'll have too many
distractions to be able to focus on this. Let's *not* do that.
AFAICS we're geographically roughly split between US/Canada and
Europe, so I'm thinking a week in either the US or Europe, some time
in the next 2-3 months:
* Would a week before or after Connect work, in Europe (16th-20th
March, or 30th March to 3rd April)? I can look for options in the
UK easily, with maybe either Arm or Linaro hosting.
* Alternatively, a week's meeting in the US, deliberately avoiding
the Connect week so we don't wipe people out with travel: Maybe 2-6
or 9-13 March? Or push back into April if that's too short notice,
of course. Would Xilinx be able to host something for us, maybe? Or
another possibility might be the Linaro office in Nashua?
I'm open to other suggestions for time and venue. Let's try to make
something work here?
Cheers,
Steve
--
Steve McIntyre steve.mcintyre-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs
next reply other threads:[~2020-02-06 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 15:59 Steve McIntyre [this message]
[not found] ` <20200206155907.GQ6796-RWaXQMOneMVkKwkEErXb8g@public.gmane.org>
2020-02-06 17:04 ` System DT - thinking a sprint would help Francois Ozog
2020-02-10 11:17 ` Grant Likely
[not found] ` <3a06abe9-b8b7-0157-d881-f5e19176fc2f-5wv7dgnIgG8@public.gmane.org>
2020-02-10 14:28 ` Steve McIntyre
[not found] ` <20200210142812.GA18978-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2020-02-10 15:52 ` Grant Likely
[not found] ` <010001701b769f8f-8cbe493b-840f-4055-a955-e7b1bebe87f6-000000@email.amazonses.com>
[not found] ` <010001701b769f8f-8cbe493b-840f-4055-a955-e7b1bebe87f6-000000-p/GC64/jrecnJqMo6gzdpkEOCMrvLtNR@public.gmane.org>
2020-02-06 17:48 ` [System-dt] " Nathalie Chan King Choy
[not found] ` <BYAPR02MB5621F0DA2DA2C69C318DE8C0A51D0-JPgLbEBPuzqwE48iOvlP/6nrV9Ap65cLvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2020-02-07 15:48 ` Loic PALLARDY
[not found] ` <d276b22b6e8249bc9eda9f92f9f52f5f-GGltqRL9kSEdIAuSVraBWEEOCMrvLtNR@public.gmane.org>
2020-02-07 19:08 ` Steve McIntyre
[not found] ` <20200207190841.GE32331-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2020-02-08 1:39 ` Stefano Stabellini
2020-02-08 17:37 ` Steve McIntyre
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=20200206155907.GQ6796@tack.einval.com \
--to=steve.mcintyre-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=Grant.Likely-5wv7dgnIgG8@public.gmane.org \
--cc=Rob.Herring-5wv7dgnIgG8@public.gmane.org \
--cc=arnd-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=benjamin.gaignard-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=bruce.ashfield-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
--cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dte-all-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=mark.brown-5wv7dgnIgG8@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
--cc=stefanos-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
--cc=system-dt-ZwoEplunGu1b+pB8xrm1Mtaxn9tAw+E3@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).