From: Jason Cooper <jason@lakedaemon.net>
To: Olof Johansson <olof@lixom.net>
Cc: Rob Herring <robh@kernel.org>,
Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] ARM legacy board DT conversion finalization
Date: Fri, 16 May 2014 00:10:22 -0400 [thread overview]
Message-ID: <20140516041022.GY27822@titan.lakedaemon.net> (raw)
In-Reply-To: <CAOesGMi0JrTp9kUVDod4duBOCZ+wNRJ0dMmgvBX7jEQRjE5cCA@mail.gmail.com>
On Thu, May 15, 2014 at 08:30:10PM -0700, Olof Johansson wrote:
> Hi,
>
> On Thu, May 15, 2014 at 12:42 PM, Jason Cooper <jason@lakedaemon.net> wrote:
> > On Thu, May 15, 2014 at 01:50:02PM -0500, Rob Herring wrote:
> >> On Thu, May 15, 2014 at 7:15 AM, Grant Likely <grant.likely@secretlab.ca> wrote:
> >> > On Sun, 11 May 2014 08:37:29 -0400, Jonathan Corbet <corbet@lwn.net> wrote:
> >> >> On Sat, 10 May 2014 23:00:09 -0400
> >> >> Jason Cooper <jason@lakedaemon.net> wrote:
> >> >>
> >> >> > 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.
> >> >>
> >> >> This *really* looks like an ARM minisummit topic to me; hopefully one
> >> >> of those is in the works?
> >> >
> >> > It does, doesn't it? I wouldn't want this as a main ksummit topic.
> >> >
> >> > The problem with ARM minisummits these days is it is very easy to
> >> > devolve into a nothing-but-dt meeting with a bunch of people sitting
> >> > around looking either annoyed or bored. We weren't able to pull enough
> >> > topics together when we tried to do an ARM minisummit at the ELC.
> >> >
> >> > Instead of a traditional ARM minisummit, perhaps we should do an ARM
> >> > platforms minisprint instead. Light on any kind of presentations, but
> >> > have the right people in the room to try and knock out some of the
> >> > legacy backlog (which is kind of what Jason described)
> >>
> >> Isn't a large part of the backlog cases of we need DT bindings for X?
> >> There are cases like moving platforms to common clk, but is there
> >> anything to discuss for those? Most of those cases need bodies to work
> >> on them. It seems like the rest of the todo lists could become an all
> >> DT discussion. I'm not saying it shouldn't happen, just pointing out
> >> where I think sprint discussions will go.
> >
> > As gregkh mentioned for the staging tree:
> >
> > $ ls arch/arm/*/TODO
> >
> > would be helpful for folks who aren't familiar with an SoC, but can
> > easily generate patches. imho, this is work for *after* the proposed
> > discussion. We don't currently have a good idea which directories to
> > deprecate, convert, or leave to bit rot. Once we do, I think the TODO
> > list would be helpful.
>
> Anyone should feel free to add a TODO file and list in their machine
> directory at any given time. I don't think there's need for discussion
> before that happens.
If there's a maintainer adding a todo file, then by default, that keeps
it out of bitrot and deprecation categories :)
> There's also the elinux.org wikis if you want to
> keep it out of the kernel -- keeping the TODO around for old kernel
> versions might not be very useful so having it out of tree might be
> just as fine.
>
> > My main reason for raising this topic was the proximity to LinuxCon.
> > There's a better chance of getting some distro representation to give us
> > valuable feedback: "This SoC is quiet, no patches, but is actively used"
> > and "We thought the kernel guys had a reason for keeping that one."
>
> Funny, I would have thought ELC to have been a much more suitable
> venue for that, especially since the older ARM platforms tend to be
> embedded, and not generic compute ones. :)
I agree, but I couldn't make it there this year :(
Also, when I initially submitted this proposal I didn't know if there
was going to be a ARM mini-summit or not. If not, I thought this might
be worth discussing amongst the ARM folks for an hour or so.
> > eg: I know ixp4xx had an active community around it at one time for the
> > NSLU2, and the Gateworks boards used that SoC. Are there people still
> > running it? Well, my Dad is, but I can fix that if needed. ;-)
>
> I suspect it'll be hard to get that answered at LinuxCon, nor at an
> ARM maintainer summit since the fringe platforms tend to not be
> represented there either.
Ok, I assumed *everybody* in the Linux ecosystem went to LinuxCon. I've
never actually been to one, but that museum was really crowded in
Edinburgh. I figured that _must_ be everybody. :)
Joking aside, I concede your point. It looks like the last two mvebu
legacy platforms (dove, mv78xx0) might get merged into mach-mvebu during
the next cycle. After that, we can reach out to the Debian and OpenWRT
guys and see what legacy platforms are in use or rotting. We can go
from there.
thx,
Jason.
next prev parent reply other threads:[~2014-05-16 4:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 3:00 Jason Cooper
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 [this message]
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=20140516041022.GY27822@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--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