Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 13 Dec 2022 10:48:24 -0700
From:      Warner Losh <imp@bsdimp.com>
To:        "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>
Subject:   Re: FreeBSD 14: Poll armv6 deprecated or removed
Message-ID:  <CANCZdfquBUCQsxYL83cQoLm2s04qvO%2BOz-h88zYwT2DmXdKKBw@mail.gmail.com>
In-Reply-To: <CANCZdfr_WsHbbeY6FyKxFdx7dOaFEhk%2BiJLYQ6F4rLOUuf-zRQ@mail.gmail.com>
References:  <CANCZdfr_WsHbbeY6FyKxFdx7dOaFEhk%2BiJLYQ6F4rLOUuf-zRQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000adafd305efb93a37
Content-Type: text/plain; charset="UTF-8"

Sorry for the lag of a year, it's been a crazy time for me and this fell
through the cracks.

On Thu, Oct 28, 2021 at 9:37 AM Warner Losh <imp@bsdimp.com> wrote:

> Greetings,
>
> Given that the number of available and useful armv6 boards has fallen to
> almost zero, the time has come to look hard at armv6.
>
> There's a number of options.
>
> 1. Keep it as is. This will only happen if there's a lot more users than
> we think (and we think there's nearly zero users of FreeBSD 13 and newer
> that would want to run FreeBSD 14).
>
> 2. Stop building packages. Given it's small to non-existent user base, it
> makes no sense to provide a package building service for it.
> 2a. We should likely do this anyway for all stable branches since it's a
> net negative in terms of cost/benefit analysis: lots of effort to produce,
> very little use.
>
> 3. Disconnect it from universe: This will mean it will rot, though. It's a
> necessary step in removal.
>
> 4. Remove support for armv6 in base entirely. This will orphan any RPiB
> and RPi0 users out there. However, the RPiB hasn't been sold in a few
> years, and the RPI0's connectivity is severely lacking given no SDIO
> support.
>
> So, which of these steps do we do before FreeBSD 14 and which before
> FreeBSD 15?
>
> My vote would be to do 1-4 for 14 including 2a.
>

After discussing this offline and distilling the responses here, on IRC,
etc, I'd like to propose we do the following:

(1) Stop building packages for armv6 entirely, on all branches. While there
are some users, they can still use poudriere to build package sets
themselves. Usage data suggests there's not enough demand for these
packages.
(2) Move armv6 to an 'EXTRA' target in make universe (eg make universe
EXTRA_TARGETS=t). Powerpc does this today with powerpcspe since it's not
completely supported in base. People that care can continue to build it as
part of universe and we'll fix things that are broken, reported to us and
have patches that don't regress other platforms.
(3) After the stable/14 branch next May or June, we'll remove build support
from ports (very little) and src. We'll also start to tear down armv6
support as we see it and are working in other areas, and expect that work
to be done before stable/15 is branched in a predicted 2025.
(4) Immediately stop including armv6 -current snapshots as generated by re@.
(5) re@ won't create armv6 release images or artifacts for stable/14, 14.0,
etc. Users wishing to build it can do so.

I've send email to re@ asking about #4 and #5.

Warner

--000000000000adafd305efb93a37
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Sorry for the lag of a year, it&#39;s been a crazy ti=
me for me and this fell through the cracks.</div><br><div class=3D"gmail_qu=
ote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Oct 28, 2021 at 9:37 AM =
Warner Losh &lt;<a href=3D"mailto:imp@bsdimp.com">imp@bsdimp.com</a>&gt; wr=
ote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D=
"ltr">Greetings,<br><div><br></div><div>Given that the number of available =
and useful armv6 boards has fallen to almost zero, the time has come to loo=
k hard at armv6.</div><div><br></div><div>There&#39;s a number of options.<=
/div><div><br></div><div>1. Keep it as is. This will=C2=A0only happen if th=
ere&#39;s a lot more users than we think (and we think=C2=A0there&#39;s nea=
rly zero users of FreeBSD 13 and newer that would want to run FreeBSD 14).<=
/div><div><br></div><div>2. Stop building packages. Given it&#39;s small to=
 non-existent user base, it makes no sense to provide a package building se=
rvice for it.</div><div>2a. We should likely do this anyway for all stable =
branches since it&#39;s a net negative in terms of cost/benefit analysis: l=
ots of effort to produce, very little use.</div><div><br></div><div>3. Disc=
onnect it from universe: This will mean it will rot, though. It&#39;s a nec=
essary step in removal.</div><div><br></div><div>4. Remove support for armv=
6 in base entirely. This will orphan any RPiB and RPi0 users out there. How=
ever, the RPiB hasn&#39;t been sold in a few years, and the RPI0&#39;s conn=
ectivity is severely=C2=A0lacking given no SDIO support.</div><div><br></di=
v><div>So, which of these steps do we do before FreeBSD 14 and which before=
 FreeBSD 15?</div><div><br></div><div>My vote would be to do 1-4 for 14 inc=
luding 2a.</div></div></blockquote><div><br></div><div>After discussing thi=
s offline and distilling the responses here, on IRC, etc, I&#39;d like to p=
ropose we do the following:</div><div><br></div><div>(1) Stop building pack=
ages for armv6 entirely, on all branches. While there are some users, they =
can still use poudriere to build package sets themselves. Usage data sugges=
ts there&#39;s not enough demand for these packages.</div><div>(2) Move arm=
v6 to an &#39;EXTRA&#39; target in make universe (eg make universe EXTRA_TA=
RGETS=3Dt). Powerpc does this today with powerpcspe since it&#39;s not comp=
letely supported in base. People that care can continue to build it as part=
 of universe and we&#39;ll fix things that are broken, reported to us and h=
ave patches that don&#39;t regress other platforms.</div><div>(3) After the=
 stable/14 branch next May or June, we&#39;ll remove build support from por=
ts (very little) and src. We&#39;ll also start to tear down armv6 support a=
s we see it and are working in other areas, and expect that work to be done=
 before stable/15 is branched in a predicted 2025.</div><div>(4) Immediatel=
y stop including armv6 -current snapshots as generated by re@.</div><div>(5=
) re@ won&#39;t create armv6 release images or artifacts for stable/14, 14.=
0, etc. Users wishing to build it can do so.</div><div><br></div><div>I&#39=
;ve send email to re@ asking about #4 and #5.</div><div><br></div><div>Warn=
er</div></div></div>

--000000000000adafd305efb93a37--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfquBUCQsxYL83cQoLm2s04qvO%2BOz-h88zYwT2DmXdKKBw>