From: Arnd Bergmann <arnd@arndb.de>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: Rob Herring <robh@kernel.org>,
Jason Cooper <jason@lakedaemon.net>,
Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] ARM legacy board DT conversion finalization
Date: Fri, 23 May 2014 15:57:19 +0200 [thread overview]
Message-ID: <32559195.sfqtkZmVxi@wuerfel> (raw)
In-Reply-To: <CACRpkdZEyHpnmfdXRQjt3mgZu4Nx62osLv+7f5TKtURW8YXZ+Q@mail.gmail.com>
On Friday 23 May 2014 15:40:15 Linus Walleij wrote:
> On Thu, May 15, 2014 at 8:50 PM, Rob Herring <robh@kernel.org> wrote:
>
> > I do think having todo lists would be valuable. I would like to see
> > more than a one off list and have a living document. Linus W had a
> > great spreadsheet on this for multi-platform enablement. Perhaps this
> > would spur people to do some of the clean-ups (or it will just bit rot
> > ).
>
> It's still there:
> https://docs.google.com/spreadsheet/ccc?key=0Aj_PQh-9xwkMdHRHYzRzOEhyMEt5b3UtOFIwcHRpWEE
>
> However I don't think there is much to discuss really. It's just work,
> we know how to do it.
>
> The real problem is that of somebody doing the work, and when maintainers
> don't want to do the work, how to proceed by leaving the platform as-is
> (legacy), delete it (lacking active maintainer) or have some custodian
> like me acquire the hardware and fix it up myself.
>
> Arnd and I have discussed this and we basically think that the StrongARM
> stuff (RISC PC, Netwinder, SA1100-based handhelds etc) are legacy
> systems while all ARMv4T and later are target for modernization if
> and only if an active maintainer is available to pursue the work.
I was also including the XScale based platforms (ixp, iop, pxa) in the
same category as StrongARM, although PXA sticks out a bit as there is new
development going on for that platform.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [Ksummit-discuss] [TECH TOPIC] ARM legacy board DT conversion finalization
Date: Fri, 23 May 2014 15:57:19 +0200 [thread overview]
Message-ID: <32559195.sfqtkZmVxi@wuerfel> (raw)
In-Reply-To: <CACRpkdZEyHpnmfdXRQjt3mgZu4Nx62osLv+7f5TKtURW8YXZ+Q@mail.gmail.com>
On Friday 23 May 2014 15:40:15 Linus Walleij wrote:
> On Thu, May 15, 2014 at 8:50 PM, Rob Herring <robh@kernel.org> wrote:
>
> > I do think having todo lists would be valuable. I would like to see
> > more than a one off list and have a living document. Linus W had a
> > great spreadsheet on this for multi-platform enablement. Perhaps this
> > would spur people to do some of the clean-ups (or it will just bit rot
> > ).
>
> It's still there:
> https://docs.google.com/spreadsheet/ccc?key=0Aj_PQh-9xwkMdHRHYzRzOEhyMEt5b3UtOFIwcHRpWEE
>
> However I don't think there is much to discuss really. It's just work,
> we know how to do it.
>
> The real problem is that of somebody doing the work, and when maintainers
> don't want to do the work, how to proceed by leaving the platform as-is
> (legacy), delete it (lacking active maintainer) or have some custodian
> like me acquire the hardware and fix it up myself.
>
> Arnd and I have discussed this and we basically think that the StrongARM
> stuff (RISC PC, Netwinder, SA1100-based handhelds etc) are legacy
> systems while all ARMv4T and later are target for modernization if
> and only if an active maintainer is available to pursue the work.
I was also including the XScale based platforms (ixp, iop, pxa) in the
same category as StrongARM, although PXA sticks out a bit as there is new
development going on for that platform.
Arnd
next prev parent reply other threads:[~2014-05-23 13:57 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 3:00 [Ksummit-discuss] [TECH TOPIC] ARM legacy board DT conversion finalization Jason Cooper
2014-05-11 3:00 ` Jason Cooper
2014-05-11 12:37 ` [Ksummit-discuss] " Jonathan Corbet
2014-05-11 12:37 ` Jonathan Corbet
2014-05-11 13:59 ` Alexandre Belloni
2014-05-11 13:59 ` Alexandre Belloni
2014-05-11 14:22 ` Olof Johansson
2014-05-11 14:22 ` Olof Johansson
2014-05-15 12:15 ` Grant Likely
2014-05-15 12:15 ` Grant Likely
2014-05-15 13:38 ` Jason Cooper
2014-05-15 13:38 ` Jason Cooper
2014-05-15 18:50 ` Rob Herring
2014-05-15 18:50 ` Rob Herring
2014-05-15 19:42 ` Jason Cooper
2014-05-15 19:42 ` Jason Cooper
2014-05-16 3:30 ` Olof Johansson
2014-05-16 3:30 ` Olof Johansson
2014-05-16 4:10 ` Jason Cooper
2014-05-16 4:10 ` Jason Cooper
2014-05-16 18:31 ` Ben Hutchings
2014-05-16 18:31 ` Ben Hutchings
2014-05-16 18:42 ` Jason Cooper
2014-05-16 18:42 ` Jason Cooper
2014-05-16 22:20 ` Ben Hutchings
2014-05-16 22:20 ` Ben Hutchings
2014-05-19 12:20 ` Arnd Bergmann
2014-05-19 12:20 ` Arnd Bergmann
2014-05-19 22:41 ` Peter Maydell
2014-05-19 22:41 ` Peter Maydell
2014-05-19 23:06 ` Rob Herring
2014-05-19 23:06 ` Rob Herring
2014-05-20 8:08 ` Arnd Bergmann
2014-05-20 8:08 ` Arnd Bergmann
2014-05-22 14:44 ` Rob Herring
2014-05-22 14:44 ` Rob Herring
2014-05-23 13:48 ` Linus Walleij
2014-05-23 13:48 ` Linus Walleij
2014-05-23 14:42 ` Arnd Bergmann
2014-05-23 14:42 ` Arnd Bergmann
2014-05-23 13:46 ` Linus Walleij
2014-05-23 13:46 ` Linus Walleij
2014-05-23 13:40 ` Linus Walleij
2014-05-23 13:40 ` Linus Walleij
2014-05-23 13:57 ` Arnd Bergmann [this message]
2014-05-23 13:57 ` Arnd Bergmann
2014-05-16 3:39 ` Olof Johansson
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=32559195.sfqtkZmVxi@wuerfel \
--to=arnd@arndb.de \
--cc=jason@lakedaemon.net \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.