Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757508AbdLQTlg (ORCPT ); Sun, 17 Dec 2017 14:41:36 -0500 Received: from mail-out.m-online.net ([212.18.0.10]:59570 "EHLO mail-out.m-online.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754757AbdLQTle (ORCPT ); Sun, 17 Dec 2017 14:41:34 -0500 X-Auth-Info: iMdlTTzqs+PyHFxWzcp6tfXOb0ntne4N9bZ2FL5AxT4= Date: Sun, 17 Dec 2017 20:41:22 +0100 From: Lukasz Majewski To: Arnd Bergmann Cc: Alexander Sverdlin , Linus Walleij , Hartley Sweeten , Russell King , Linux ARM , Linux Kernel Mailing List , Olof Johansson Subject: Re: [PATCH v5 0/4] ARM: ep93xx: ts72xx: Add support for BK3 board Message-ID: <20171217204122.0a10a5e1@jawa> In-Reply-To: References: <20171116232239.16823-1-lukma@denx.de> <20171211233625.5689-1-lukma@denx.de> <1513153607.2439.2.camel@Nokia-N900> Organization: denx.de X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/pMfnPCP0qr+ZmccFx8dH1y/"; protocol="application/pgp-signature" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3550 Lines: 97 --Sig_/pMfnPCP0qr+ZmccFx8dH1y/ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Arnd, > On Wed, Dec 13, 2017 at 9:26 AM, Alexander Sverdlin > wrote: > > On Wed Dec 13 08:34:22 2017 Linus Walleij > > wrote: =20 > >> Arnd has been nudging me to do DT conversion for EP93xx > >> so if there are many active industrial users of these > >> I should prioritize it, because these things have 20+ years > >> support cycles. =20 > > > > I'm not sure how important or necessary at all is to change > > anything in these legacy platforms. =20 >=20 > I suspect that at several points in the next 5 to 10 years, we will > remove additional platforms or CPU types, as we tend to do when a > platform becomes a maintenance burden and is clearly not used by > anyone. I suppose that at least the last argument is not the case here :-). >=20 > It's hard to predict in advance what triggers the removal, but as the > number of platforms that are not using DT or ARCH_MULTIPLATFORM > goes down to a small number, there will be increased interested in > either removing or converting the remaining ones. This is not an > immediate danger at the moment, since we still have 14 platforms that > are not using ARCH_MULTIPLATFORM, and 23 that have remaining > board files, but you don't want to be the last user of the last > platform after the other ones are done ;-) :-) >=20 > >> We also need to think about upholding support in GCC for > >> ARMv4(t) for the foreseeable future if there is a big web of > >> random deeply embedded systems out there that will need > >> updates. =20 > > > > But we should definitely preserve at least what we have. =20 >=20 > Plain ARMv4 (and earlier) support in gcc is already marked > 'deprecated' and will likely be gone in gcc-8 (it's still there as of > last week). ARMv4T is going to be around for a while, and you can > even keep building for ARMv4 using "-march=3Darmv4t -marm" when linking > with 'ld --fix-v4bx'. I think that we shall start complaining on the gcc-devel mailing list now. I would be hard to wake up in 2 years time and realise that we don't have a modern compiler. >=20 > Debian recently did a survey to find out whether there were still > users on ARMv4 or ARMv4T, and the result was that probably everyone is > on ARMv5E or ARMv6 for the ARM port (which is separate from the > ARMHF port that is ARMv7+). See also > https://lists.debian.org/debian-user/2017/11/msg00379.html > and let them know quickly if you use Debian stable releases and > plan to update to Debian 10 (Buster) in the future. >=20 > Arnd Best regards, Lukasz Majewski -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de --Sig_/pMfnPCP0qr+ZmccFx8dH1y/ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEgAyFJ+N6uu6+XupJAR8vZIA0zr0FAlo2yGIACgkQAR8vZIA0 zr03fAf/fQotm0FxmNqnWQvgcBFuK9XmhJz1IBDJPSvCwKrDJyuFb2rKj2qvU9Um Iey1ldjwXJeVoUrtgrhFpg+MuB/ZXrisz6nvT1fJF8ODkxu3CfkvyaFJzdtTdtzv jHLZM71CAwPN7j2+sFlNlatT/WoHmrvPa/bhD53ah4x0ngSStw4EEs8ZfAc57QWp bkg4846Ik2U2QotjjOjLAthEmsCChWTwoHksOnrFLu7Ls+ZSvHN2/Dn+LpA3Bsie 1mo7/tHbmCnvZRPmscVcxOe3r+vz234h8TvSIySh4GvWyGWzJ+fAvE5Bo9+mh+Vt /i/hRQP8bwEXa3N98Q8HBJWV/hSvBg== =N7+i -----END PGP SIGNATURE----- --Sig_/pMfnPCP0qr+ZmccFx8dH1y/--