From owner-freebsd-arm@freebsd.org Tue Apr 13 13:44:15 2021 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D7EC95E0948 for ; Tue, 13 Apr 2021 13:44:15 +0000 (UTC) (envelope-from jfc@mit.edu) Received: from outgoing-exchange-1.mit.edu (outgoing-exchange-1.mit.edu [18.9.28.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.outgoing-exchange.mit.edu", Issuer "InCommon RSA Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FKRfR1QJsz4jTD for ; Tue, 13 Apr 2021 13:44:14 +0000 (UTC) (envelope-from jfc@mit.edu) Received: from w92exedge4.exchange.mit.edu (W92EXEDGE4.EXCHANGE.MIT.EDU [18.7.73.16]) by outgoing-exchange-1.mit.edu (8.14.7/8.12.4) with ESMTP id 13DDgmfp006372; Tue, 13 Apr 2021 09:44:13 -0400 Received: from OC11EXPO29.exchange.mit.edu (18.9.4.102) by w92exedge4.exchange.mit.edu (18.7.73.16) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 13 Apr 2021 09:43:41 -0400 Received: from OC11EXPO29.exchange.mit.edu (18.9.4.102) by oc11expo29.exchange.mit.edu (18.9.4.102) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 13 Apr 2021 09:43:52 -0400 Received: from OC11EXPO29.exchange.mit.edu ([18.9.4.102]) by oc11expo29.exchange.mit.edu ([18.9.4.102]) with mapi id 15.00.1497.012; Tue, 13 Apr 2021 09:43:52 -0400 From: John F Carr To: Valery Seys , FreeBSD ARM Subject: Re: Arm64 Tier 1 FreeBSD 13 Phones Thread-Topic: Arm64 Tier 1 FreeBSD 13 Phones Thread-Index: AQHXLenN28eSsugQi0ChWATxC3PxYKquKPMAgAGV0gCAAP5kAIACACSA Date: Tue, 13 Apr 2021 13:43:52 +0000 Message-ID: References: <20210410154750.phxivk7idvza37nx@mutt-hbsd> <008dca83-fc81-dc3d-f2e6-9404e4e2652b@vslash.com> In-Reply-To: <008dca83-fc81-dc3d-f2e6-9404e4e2652b@vslash.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [108.7.221.50] Content-Type: text/plain; charset="us-ascii" Content-ID: <647781D4EE8C9A409D6BBADBC5580AC7@exchange.mit.edu> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Rspamd-Queue-Id: 4FKRfR1QJsz4jTD X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of jfc@mit.edu designates 18.9.28.15 as permitted sender) smtp.mailfrom=jfc@mit.edu X-Spamd-Result: default: False [-1.50 / 15.00]; ARC_NA(0.00)[]; RWL_MAILSPIKE_VERYGOOD(0.00)[18.9.28.15:from]; RCVD_COUNT_FIVE(0.00)[5]; HAS_XOIP(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:18.9.28.0/24]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[mit.edu]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[18.9.28.15:from]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(1.00)[1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:3, ipnet:18.9.0.0/16, country:US]; RCVD_TLS_LAST(0.00)[]; MAILMAN_DEST(0.00)[freebsd-arm] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Porting FreeBSD to ARM processors List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Apr 2021 13:44:15 -0000 On Apr 12, 2021, at 03:10 , Valery Seys wrote: >=20 >=20 > I'm affraid that FreeBSD do not run on a PinePhone. > The dmesg from nycbug comes from a pine64 board, not from a pinephone. Is it known not to run, or merely untested? It looks like every Pine devic= e needs a different configuration. At $200 it is tempting to get one to ex= periment on. Maybe after my current time sink ends in a few weeks. The original message (subject line) reflects a misunderstanding of what "Ti= er 1" means. It means the FreeBSD team will try hard not to break rack mou= nt servers. Tier 1 status doesn't make FreeBSD any more suited to phones t= han Tier 2 status. It doesn't add device or CPU support. See all the diff= iculties with Raspberry Pi. It doesn't add a UI for a small screen. The p= otabi PinePhone project by its own admission hasn't accomplished anything b= ut starting a UI design. But maybe by end of year we can have something th= at works when plugged into a power supply.