From owner-freebsd-current@freebsd.org Fri Mar 1 14:29:07 2019 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9EC45151903A for ; Fri, 1 Mar 2019 14:29:07 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io1-f49.google.com (mail-io1-f49.google.com [209.85.166.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 71A2C828DC; Fri, 1 Mar 2019 14:29:06 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io1-f49.google.com with SMTP id p18so19692492ioh.5; Fri, 01 Mar 2019 06:29:06 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=68IZKtkYY8qFot+fmcTLjMqGlbG8CDZYT0J6qGYgUP8=; b=NXXbXX8g63f3XfR+iiNTR7wJjt+jduTJ7MrxLk4r/PlcjSa4yKbQSnZy58vKXJ9UHc z0qGdYxgQHv3uzGf0HJqzMse5NeMSu0GOfnveGvZDwRDmu1inG0iXDidO9AFryzYAe9C XD0NljEV/q0HydVxZ+ioVLOjptJaZZnZuupBZBuh90Cc2GvdDoX+cDuFcGow1jAK7tvV YE9QCuWUHqvFPTNa5Tayu7xCwkDQcSYBvruH6I/efoEGhMjA3CJYLY9bkNGuVbDdyEsE cWzrllP+5kbBDSX/brwfKXu/cYZGl4JqK1CKu6d/s6RRZKClaOM7exXDoyHOcKGCzeJG v77Q== X-Gm-Message-State: APjAAAVvjrWTd3ORnIepH7jpr8y6lAcwoxOrdDkO+2PLy3qnGL9SQdOb J3/pdOhI3IicCpc42+1czf2P5dhzRsxZU/BfBl5G1g== X-Google-Smtp-Source: APXvYqw2p0NeVwxa9kKpszMZ8wk+R44RoRrPU6IPCsGuJGEJZoKWcGglv07pLMaeBSQBrTT7uNajlUo+faAxsRi9BTI= X-Received: by 2002:a6b:fb02:: with SMTP id h2mr2816416iog.239.1551450538455; Fri, 01 Mar 2019 06:28:58 -0800 (PST) MIME-Version: 1.0 References: <20190222033924.GA25285@troutmask.apl.washington.edu> <20190222060410.GA25817@troutmask.apl.washington.edu> <20190223032644.GA14058@troutmask.apl.washington.edu> <20190223163947.GB18805@troutmask.apl.washington.edu> <20190228183214.GA17372@troutmask.apl.washington.edu> <55eb26fb977fe90e323a8721e39bfc0185d994ba.camel@freebsd.org> In-Reply-To: <55eb26fb977fe90e323a8721e39bfc0185d994ba.camel@freebsd.org> From: Ed Maste Date: Fri, 1 Mar 2019 09:28:44 -0500 Message-ID: Subject: Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd To: Ian Lepore Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 71A2C828DC X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of carpeddiem@gmail.com designates 209.85.166.49 as permitted sender) smtp.mailfrom=carpeddiem@gmail.com X-Spamd-Result: default: False [-5.76 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE(-2.97)[ip: (-8.93), ipnet: 209.85.128.0/17(-3.82), asn: 15169(-2.03), country: US(-0.07)]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[49.166.85.209.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.78)[-0.777,0]; FORGED_SENDER(0.30)[emaste@freebsd.org,carpeddiem@gmail.com]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[emaste@freebsd.org,carpeddiem@gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Mar 2019 14:29:07 -0000 On Thu, 28 Feb 2019 at 14:13, Ian Lepore wrote: > > I have been of the opinion that armv[67] has met all the bullet points > to be a tier-1 arch for several years, but nobody seemed interested in > declaring it so. Now it'll never happen, because there seems to be > growing momentum to throw everything 32-bit under the bus and declare > freebsd to be a 64-bit-only OS. Netflix wins; those of us building > smaller embedded products will eventually be forced to move to linux. I don't think this is the case. For one example, see the effort kib@ has been putting in (under Foundation sponsorship) on FreeBSD/i386. One of my co-op students this term is working on building out our hardware continuous integration testbed, including 32-bit Arm targets like the BeagleBone Black. Now, i386 has not been our primary reference platform for some time, and I expect that for 32-bit ports FreeBSD will largely be cross-built from amd64, arm64, or powerpc64 hosts. I think this is absolutely fine, and we can still support 32-bit devices well, but our current tier definitions don't fit this model well.