Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 28 May 2023 09:08:32 -0700
From:      Mark Millard <marklmi@yahoo.com>
To:        Emmanuel Vadot <manu@bidouilliste.com>, freebsd-arch <freebsd-arch@freebsd.org>
Subject:   Re: Future of 32-bit platforms (including i386)
Message-ID:  <00E63ECC-2E7B-4C9F-9903-A8BD67278C00@yahoo.com>
References:  <00E63ECC-2E7B-4C9F-9903-A8BD67278C00.ref@yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Emmanuel Vadot <manu_at_bidouilliste.com> wrote on
Date: Wed, 24 May 2023 06:35:55 UTC :

> . . .
>=20
> I personnaly see armv7 in "degraded maintainance mode" since 13.0,
> nothing really intersting was added, no new SoC support even if there
> was some interesting one that we could support, no new drivers for
> supported platforms. We even lost TI BeagleBone support because no one
> really have the time to keep support up to date.
> I still have some little cute boards that I want to use from time to
> time but the lack of proper porting of new language (like rust and =
iirc
> go have problems too) is making new software unusable on those boards
> (you can't even make some "smart speaker" for spotify as all the
> spotify clients are in rust).
> IMX6 support is stalled since ian@ passed away and mmel@ isn't very
> active atm and they were both the most actives developers for armv7 =
low
> level code.

One of the things for tier 2 is:
(from https://docs.freebsd.org/en/articles/committers-guide/#archs
21.4. Tier 2 section)

QUOTE
Collectively, developers are required to provide the following
to maintain the Tier 2 status of a platform:

    =E2=80=A2 Tier 2 architectures must have an active ecosystem of =
users and developers.
END QUOTE

Is there an implication that, even for 14, the "developers"
part of that for armv7 has dropped off to the point that
tier 2 would reasonably be in question?

=3D=3D=3D
Mark Millard
marklmi at yahoo.com




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00E63ECC-2E7B-4C9F-9903-A8BD67278C00>