Date: Wed, 13 Jun 2018 10:39:06 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> To: Warner Losh <imp@bsdimp.com> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>, "freebsd-arch@freebsd.org" <arch@freebsd.org> Subject: Re: Armeb removal before 12 Message-ID: <201806131739.w5DHd6sl040722@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <CANCZdfoVYJbJEM-PhKL3Y_edp=X6Smb1uYHrEiYSm%2BZXsTmzdw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I'd like to remove armeb before 12.0. > > It's poorly supported today. > > Nobody has tested the concurrency kit changes on it. And ck is now > mandatory. We don't even know if it works or not. > > Last time we asked, it took quite a while to find users. > > It maxes out at 256MB of RAM. This is barely large enough for FreeBSD to > run in. 64MB is usable for 32 bit archs, I have many VM's running in that configuration, so this item should not be in this list. > > The hardware was last made almost a decade ago. > > It uses non-standard non-mainstream boot loaders (boot technology has moved > on from redboot). > > The cost of doing API sweeps, make universe runs, etc exceeds the benefit > to the project. > > So, given all these factors, it sounds like a good candidate for retirement. > > Therefore, I'd like to remove it on July 15th. > > Comments? (please keep them on topic to this specific thing: there's other > things that may also be past their freshness date, we'll discuss those in a > separate thread). Given all the other valid reasons, I have no objection to removal of armeb. -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201806131739.w5DHd6sl040722>