From: Jason Cooper <jason@lakedaemon.net>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
Kevin Hilman <khilman@linaro.org>
Cc: Rob Herring <robh@kernel.org>,
Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>,
ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] [TECH TOPIC] ARM legacy board DT conversion finalization
Date: Sat, 10 May 2014 23:00:09 -0400 [thread overview]
Message-ID: <20140511030009.GO12708@titan.lakedaemon.net> (raw)
All,
Over the past couple of years, the ARM sub-arch maintainers have been
doing a great amount of work migrating to devicetree.
In conjunction with this effort, we've been slowly migrating the
existing legacy platforms (board files) over to devicetree. For the
small part the mvebu maintainers are responsible for, we can see the
light at the end of the tunnel now. :-)
I imagine several other sub-arches are in a similar situation. I think
it would be useful for us all to sit down, compare notes, and pool our
resources/experiences to coordinate a final push.
So, I'm proposing a session where each sub-arch gives a brief run-down
of the status of the legacy board conversion, and wraps up with a todo
list. After all of the sub-arches have given their status (5 - 10
minutes each?), we hash out helping each other with the final pieces.
Also on the agenda, discussing the fate of the legacy sub-arches that
haven't even begun conversion to devicetree.
The intended outcome would be to have a sorted list of remaining
conversions, and who is pitching in to help out for each item. Also, a
sorted list of unconverted sub-arches, broken down into 'deprecate',
'convert', and 'seek info'.
On a final note, I'd like to include a hobbyist voice or two in here.
Since a lot of the legacy platforms are supported by embedded Debian,
OpenWRT, and similar, getting an idea of which ones we can deprecate
would save quite a bit of work.
I haven't heard word of an ARM mini-summit yet. If that happens,
obviously this topic would be most appropriate there.
Nominations:
Jason Cooper (auto-nominated)
Andrew Lunn
Gregory Clement
Sebastian Hesselbarth (auto-nominated)
Thomas Petazzoni (auto-nominated)
I can think of several names from the ARM Linux mailinglist, but since I
can't create a conclusive list, I'll leave it up to the individuals to
pipe up if they are interested.
thx,
Jason.
next reply other threads:[~2014-05-11 3:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 3:00 Jason Cooper [this message]
2014-05-11 12:37 ` Jonathan Corbet
2014-05-11 13:59 ` Alexandre Belloni
2014-05-11 14:22 ` Olof Johansson
2014-05-15 12:15 ` Grant Likely
2014-05-15 13:38 ` Jason Cooper
2014-05-15 18:50 ` Rob Herring
2014-05-15 19:42 ` Jason Cooper
2014-05-16 3:30 ` Olof Johansson
2014-05-16 4:10 ` Jason Cooper
2014-05-16 18:31 ` Ben Hutchings
2014-05-16 18:42 ` Jason Cooper
2014-05-16 22:20 ` Ben Hutchings
2014-05-19 12:20 ` Arnd Bergmann
2014-05-19 22:41 ` Peter Maydell
2014-05-19 23:06 ` Rob Herring
2014-05-20 8:08 ` Arnd Bergmann
2014-05-22 14:44 ` Rob Herring
2014-05-23 13:48 ` Linus Walleij
2014-05-23 14:42 ` Arnd Bergmann
2014-05-23 13:46 ` Linus Walleij
2014-05-23 13:40 ` Linus Walleij
2014-05-23 13:57 ` Arnd Bergmann
2014-05-16 3:39 ` Olof Johansson
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=20140511030009.GO12708@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=arnd@arndb.de \
--cc=khilman@linaro.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=olof@lixom.net \
--cc=robh@kernel.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