From: Linus Walleij <linus.walleij@linaro.org>
To: "Mark Brown" <broonie@kernel.org>,
"SZ Lin (林上智)" <sz.lin@moxa.com>,
"Holsety Chen (陳憲輝)" <Holsety.Chen@moxa.com>,
"Harry YJ Jhou (周亞諄)" <harryyj.jhou@moxa.com>,
"Jimmy Chen (陳永達)" <jimmy.chen@moxa.com>
Cc: Ksummit-discuss@lists.linuxfoundation.org,
Alexander Sverdlin <alexander.sverdlin@gmail.com>,
Lukasz Majewski <lukma@denx.de>,
Jonas Jensen <jonas.jensen@gmail.com>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Deprecation / Removal of old hardware support
Date: Tue, 11 Sep 2018 13:22:03 +0200 [thread overview]
Message-ID: <CACRpkdbcRCBFoBa88qKWHQMW-dTppH8pxxnUZZibrtUwtohgLg@mail.gmail.com> (raw)
In-Reply-To: <20180911105233.GA8018@sirena.org.uk>
Found some moxa.com mail addresses in the kernel log,
so including them. You can speak about the status of the
MOXA ART deployments if you like, I am talking about
On Tue, Sep 11, 2018 at 12:52 PM Mark Brown <broonie@kernel.org> wrote:
> On Tue, Sep 11, 2018 at 10:37:36AM +0200, Linus Walleij wrote:
>
> > 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.)
>
> Conversely, the approaches that keep stable kernels going also get
> applied to designing hardware that people intend to be stable - if
> it works well enough now why try something new, especially where that
> new stuff is most likely going to be more expensive to either buy or
> work with?
Exactly. I think this is what happened at MOXA with the ART SoC.
It seems that MOXA made that with a bunch of consultants from
Faraday in Taiwan supplying their IP blocks and know-how. Since
then they have had zero incentive to upgrade the SoC to a newer
version, as this SoC handles the ethernet, GPIO and serial lines
they need just fine.
They recently made a new design using Freescale (now NXP)
LS1021a dualcore A7, but I can see that the ART (ARMv4) in
EM-1240 and their EP93xx products (ARMv4T) are still in active
deployment and even recommended for new projects, samples can
be easily obtained.[1]
And this is good stuff, it's rock solid at this point. I just wish and
hope that they really invest in using the very latest kernels
also for these elder boards even though I rarely hear from them
on the mailing lists.
At companies that have their internal ASIC design teams I
sometimes get the feeling that these are churning out newer
and more powerful ASICs as a therapeutic exercise just to
keep their skills up. But I hope it is pure prejudice on my
part.
Yours,
Linus Walleij
[1] https://www.moxa.com/product/compact_fanless_computers.htm
next prev parent reply other threads:[~2018-09-11 11:22 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
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 [this message]
[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=CACRpkdbcRCBFoBa88qKWHQMW-dTppH8pxxnUZZibrtUwtohgLg@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=Holsety.Chen@moxa.com \
--cc=Ksummit-discuss@lists.linuxfoundation.org \
--cc=alexander.sverdlin@gmail.com \
--cc=broonie@kernel.org \
--cc=harryyj.jhou@moxa.com \
--cc=jimmy.chen@moxa.com \
--cc=jonas.jensen@gmail.com \
--cc=lukma@denx.de \
--cc=sz.lin@moxa.com \
/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