ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>,
	Alexander Sverdlin <alexander.sverdlin@gmail.com>,
	Lukasz Majewski <lukma@denx.de>,
	Jonas Jensen <jonas.jensen@gmail.com>
Cc: Ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Deprecation / Removal of old hardware support
Date: Tue, 11 Sep 2018 10:37:36 +0200	[thread overview]
Message-ID: <CACRpkdYi66Lgq7OAGchQyfqEUUGVKV9m3YzL6t_nS+Hm0G2rRg@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a0a=eAwAg5i6z-5Hs56BXKP3CSsv2383zuMh6TrrDPwug@mail.gmail.com>

Including Alexander Sverdlin, Lukasz Majewski  and Jonas
Jensen here, they may or may not be able to share some of
their industrial IoT experience. (Contract terms with vendors
may make it necessary to stay silent sometimes.)

On Mon, Sep 10, 2018 at 11:41 PM Arnd Bergmann <arnd@arndb.de> wrote:
> On Mon, Sep 10, 2018 at 5:35 PM Linus Walleij <linus.walleij@linaro.org> wrote:

> > My ARMv4 is another example, but I can point at new devices
> > beging deployed as we speak, using that ISA, even though it is
> > from 1999. So it has many active users (and maintainers).
>
> Note that even though gcc is dropping ARMv4 support from new
> compilers, you can still use old toolchains, and there are tricks to
> make ARMv4T binary code work on ARMv4. However, if gcc
> ever stops supporting ARMv4T, this becomes a problem. My guess
> is that will take another 10 years though, and we might have
> removed some or all of the individual ARMv4 platforms by then.

ARMv4 is becoming a trouble, not that it is hard to maintain,
actually we're on top of things there. The problem is that among
the FA526 systems from Faraday and the ARMv4T in EP93xx
there are very serious IoT deployments that have been going
on for soon 15 years and continuing.

New MOXA ART ARMv4 FA526 systems are being deployed
in buildings across the planet as we speak. They just replaced
one in the office block where I sit, that is how I got to know.

These are mostly for ventilation and
similar systems but also heavy duty from Liebherr controlling
unspecified hydraulic systems. The ventilation systems are
definately Internet-connected, I don't know about the others.

These pose an increasing security threat, and for that reason
I personally feel it is irresponsible to remove the option to
create new kernels and upgrade these devices.

I think for depreciation one has to be aware that some archs
used in IoT deployments have life cycles of 20-30 or more years,
whereas some tablet or handset SoCs may be something like
5 years maximum before maintainers get annoyed that you
even use them.

Sometimes I get the feeling that people focused on desktops
or servers suffer from velocitate (speed blindness) and think
everybody is like them. (Well don't we all.)

With all the hoopla about IoT in the business right now since
a year or two back, the question of their extremely long life
cycle and effect on development has not really been
considered AFAICT those are some of the most important
systems to keep maintained.

Yours,
Linus Walleij

  parent reply	other threads:[~2018-09-11  8:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-10 14:04 Peter Huewe
2018-09-10 15:31 ` Linus Walleij
2018-09-10 21:40   ` Arnd Bergmann
2018-09-10 22:02     ` Guenter Roeck
2018-09-11  8:49       ` Geert Uytterhoeven
2018-09-11 17:27         ` Guenter Roeck
2018-09-11 17:58           ` Geert Uytterhoeven
2018-09-11 18:27             ` Guenter Roeck
2018-09-11 18:37               ` Daniel Vetter
2018-09-11  8:37     ` Linus Walleij [this message]
2018-09-11  9:37       ` Lukasz Majewski
2018-09-11 19:33         ` Greg KH
2018-09-11 21:39           ` Laurent Pinchart
2018-09-11 21:50             ` Thomas Gleixner
2018-09-12  6:40               ` Geert Uytterhoeven
2018-09-12 10:23                 ` Arnd Bergmann
2018-09-12  6:26             ` Greg KH
2018-09-12  6:49               ` Peter Huewe
2018-09-12  7:07                 ` Greg KH
2018-09-11 10:52       ` Mark Brown
2018-09-11 11:22         ` Linus Walleij
     [not found]           ` <TY2PR0101MB2526376DEFC241B754A19A6AE21C0@TY2PR0101MB2526.apcprd01.prod.exchangelabs.com>
2018-09-27 15:25             ` SZ Lin (林上智)
2018-09-28 10:45               ` Thomas Gleixner
2018-09-11 11:53       ` Arnd Bergmann
2018-09-11 21:28         ` Alexander Sverdlin
2018-09-11 21:16       ` Alexander Sverdlin

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=CACRpkdYi66Lgq7OAGchQyfqEUUGVKV9m3YzL6t_nS+Hm0G2rRg@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=Ksummit-discuss@lists.linuxfoundation.org \
    --cc=alexander.sverdlin@gmail.com \
    --cc=arnd@arndb.de \
    --cc=jonas.jensen@gmail.com \
    --cc=lukma@denx.de \
    /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