From nobody Wed May 24 06:35:55 2023 X-Original-To: freebsd-arch@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QR1fP36p2z4CJF1 for ; Wed, 24 May 2023 06:35:57 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QR1fP0Ywxz3sSv; Wed, 24 May 2023 06:35:56 +0000 (UTC) (envelope-from manu@bidouilliste.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1684910155; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=TBW69mGfTZHqBGB4ZhhsvBp0vTQPgFhL39x6SKA8Oz0=; b=GydwVo0S8aAYfk8rZn+KnEsB++ICcz6rOi4LPLEmI80D/sKmW6KQ2ZeisgztumR7rX6F1q N9ofHkfemayKpvPQAU6Tfr0DYTsgYLppFLSlQf2CKZ3Z8N91GchYOjHlla8ql3tfb/AIby UIpCHXLHHvc+B/te/1oj4/Efj1NZ1eM= Received: from skull.home.blih.net (lfbn-lyo-1-2174-135.w90-66.abo.wanadoo.fr [90.66.97.135]) by mx.blih.net (OpenSMTPD) with ESMTPSA id c7dc47b1 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Wed, 24 May 2023 06:35:55 +0000 (UTC) Date: Wed, 24 May 2023 08:35:55 +0200 From: Emmanuel Vadot To: 'freebsd-arch' Cc: John Baldwin Subject: Re: Future of 32-bit platforms (including i386) Message-Id: <20230524083555.632d968778e2d1c05a04359f@bidouilliste.com> In-Reply-To: <5a08b091-a1a5-1928-18e1-16c3bddb1a7f@FreeBSD.org> References: <5a08b091-a1a5-1928-18e1-16c3bddb1a7f@FreeBSD.org> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4QR1fP0Ywxz3sSv X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12876, ipnet:212.83.128.0/19, country:FR] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Tue, 23 May 2023 16:46:51 -0700 John Baldwin wrote: > On 4/27/23 10:19 AM, John Baldwin wrote: > > For 13.0, i386 was demoted from Tier 1 to Tier 2. In the announcement > > of this for 13.0, the project committed to an update on i386's future > > around the time of 14.0. The announcement at the time suggested that > > i386 would be supported less in 14.x than in 13.x. > > > > My proposal is that for 14.x we treat i386 like any other Tier 2 > > platform. That is, release images and packages would only be provided > > on a best-effort basis, and we would not guarantee providing them. I > > think we should also stop shipping binary updates for the base system > > (freebsd-update) for 14.x for i386. > > > > A larger question is what to do about 32-bit platforms moving forward. > > My proposal for powerpc, i386, and armv[67] is that we say publicly > > that we anticipate not supporting them in 15. That is, that we may > > remove them outright from the tree, or we may leave them in the tree, > > but we do not plan on building packages or release images. Another > > option to consider for 32-bit platforms perhaps in 15 is to remove > > kernel support and only retain the ability to build userland. The > > goal of saying this now-ish (or about the time 14.0 is going to ship) > > would be to give time for users and developers to respond in the > > window between 14.0 and 15.0 so we can evaluate those responses as an > > input into the final decision for 15. > > We discussed this topic during the 15.0 developer summit and the consensus > among the folks present (which is only a subset of our community), is > that there is still interest in supporting armv7 kernels in 15.0, but not > kernels for other platforms. In addition, no one expressed a need for > full 32-bit world support for i386 and powerpc, only for compat32 support > in the kernel, and lib32 (cc -m32) support in userland. > > One question for this is if we think we will have sufficient developer > resources to maintain armv7 kernels for the life of stable/15. We can > largely punt on the final decision for that until close to the release of > 15.0. I think for what we announce for 14.0 we can still say that we > are generally planning to remove 32-bit kernel and world support in 15.0, > but may consider keeping armv7. 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. So I'm really interested in who wants to keep armv7 and why, is it just "I'm using my RPI2 and wants to continue using it" ? Cheers, -- Emmanuel Vadot