From: Lukasz Majewski <lukma@denx.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Ksummit-discuss@lists.linuxfoundation.org,
Jonas Jensen <jonas.jensen@gmail.com>,
Alexander Sverdlin <alexander.sverdlin@gmail.com>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Deprecation / Removal of old hardware support
Date: Tue, 11 Sep 2018 11:37:25 +0200 [thread overview]
Message-ID: <20180911113725.5d91b945@jawa> (raw)
In-Reply-To: <CACRpkdYi66Lgq7OAGchQyfqEUUGVKV9m3YzL6t_nS+Hm0G2rRg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3860 bytes --]
Hi Linus,
> 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.)
Thank you for putting me on CC.
>
> 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.
The ARMv4T shall be supported. The 15 years may be a bare minimum for
some "heavy duty/industrial" systems...
It may happen that the same HW (certified already) will be used for 30+
years (with the SW BSP replaced a few times).
>
> 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.
The "unspecified hydraulic systems" do have a way to update the SW
(which is already done).
>
> 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.
Frankly speaking the possibility to have the new kernel in a relatively
easy (and cheap) way was a strong motivator to add support to mainline.
>
> 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.)
I do must agree here. In general ARM9 (v4T) will stay with us for a
long, long time.
In the kernel community we pose a lot of attention to security (for
example the prompt reaction on meltdown/spectre), but in the same time
we tend to forget about the "long lived" devices and force their
maintainers to use 2.6.x kernels..... (or even 2.4.x).
>
> 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.
+1
>
> Yours,
> Linus Walleij
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-09-11 9:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 14:04 [Ksummit-discuss] [MAINTAINERS SUMMIT] Deprecation / Removal of old hardware support 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
2018-09-11 9:37 ` Lukasz Majewski [this message]
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=20180911113725.5d91b945@jawa \
--to=lukma@denx.de \
--cc=Ksummit-discuss@lists.linuxfoundation.org \
--cc=alexander.sverdlin@gmail.com \
--cc=jonas.jensen@gmail.com \
--cc=linus.walleij@linaro.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.