From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTP id 09DEE82D for ; Fri, 23 May 2014 13:57:25 +0000 (UTC) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.24]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8AC411FAB5 for ; Fri, 23 May 2014 13:57:23 +0000 (UTC) From: Arnd Bergmann To: ksummit-discuss@lists.linuxfoundation.org Date: Fri, 23 May 2014 15:57:19 +0200 Message-ID: <32559195.sfqtkZmVxi@wuerfel> In-Reply-To: References: <20140511030009.GO12708@titan.lakedaemon.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: Rob Herring , Jason Cooper , Linux ARM Kernel Subject: Re: [Ksummit-discuss] [TECH TOPIC] ARM legacy board DT conversion finalization List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Friday 23 May 2014 15:40:15 Linus Walleij wrote: > On Thu, May 15, 2014 at 8:50 PM, Rob Herring 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