From owner-freebsd-arm@freebsd.org Mon Mar 29 00:36:25 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 0F1F65B5374 for ; Mon, 29 Mar 2021 00:36:25 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out1.migadu.com (out1.migadu.com [IPv6:2001:41d0:2:863f::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4F7ttH3nPPz3rPD for ; Mon, 29 Mar 2021 00:36:22 +0000 (UTC) (envelope-from greg@unrelenting.technology) Date: Mon, 29 Mar 2021 00:36:10 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=key1; t=1616978173; 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=f0UruD0hujZfjWyjISA3iCvJaFAeXYK5YRi0sYAEcoE=; b=qAmQwUxg7vQoQomO6HajI+PHLQGUqCx202ojEAY5kdAoN9QaHcZPiS43mhnqgvwxru5HXF FrPI4PhbfvjETO470l4s1pcwHGhOWfcCH1IF9/6NB/VcVJWHL/9D8K3QReCgSYglzH9hvY bucOYcPsrqTsjM+rczlvN8Pee2nHr48PEibrpsvns6y5mh2ddZBxdcesPVQGKb18x5Bndj u8g/1ZSNrFZed6d2ZlCD3xdMNXhoEGT/cApq0YP1F9SWWOk1W3w2DvlamCrTQ6/0n9ezgX flA0GnULARB4pS52VdMkwoStlBJ3XR/fHd+OjXz7kUHb9k+cwJ7kfYq6YJmBPA== X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Greg V To: Mark Millard , Marcin Wojtas CC: freebsd-arm Subject: Re: Any good alternative to Raspberry for Arm64? In-Reply-To: <05C76F74-37E6-42D6-83B6-E5B34C920516@yahoo.com> References: <7b284f7718556f1cf0a7a205c98db6b1@pyret.net> <8F8F3491-3E1F-45C8-BF61-09F7557F48A5@googlemail.com> <265dbf9c33f4ce09c702c9d7fae93c9b@pyret.net> <05C76F74-37E6-42D6-83B6-E5B34C920516@yahoo.com> Message-ID: <13518D86-E611-4438-A405-7121D69A4E70@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: greg@unrelenting.technology X-Rspamd-Queue-Id: 4F7ttH3nPPz3rPD X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=key1 header.b=qAmQwUxg; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 2001:41d0:2:863f:: as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-2.98 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2001:41d0:2:863f:::from]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=key1]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip6:2001:41d0:2:863f::]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; SPAMHAUS_ZRD(0.00)[2001:41d0:2:863f:::from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; NEURAL_HAM_SHORT(-0.98)[-0.980]; FREEMAIL_TO(0.00)[yahoo.com,semihalf.com]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:16276, ipnet:2001:41d0::/32, country:FR]; MID_RHS_MATCH_FROM(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: Mon, 29 Mar 2021 00:36:25 -0000 On March 28, 2021 11:44:25 PM UTC, Mark Millard via freebsd-arm wrote: >On 2021-Mar-28, at 15:52, Marcin Wojtas wrote: > >> H Mark, >>=20 >> niedz=2E, 28 mar 2021 o 22:15 Mark Millard via freebsd-arm >> napisa=C5=82(a): >>>=20 >>> On 2021-Mar-28, at 12:48, Klaus K=C3=BCchemann via freebsd-arm wrote: >>>>=20 >>>>> =2E =2E =2E >>>>=20 >>>> Anyone successfully booting from nvme on any aarch64-board ?? >>>=20 >>> As reported on the list earlier, I plugged a Optane 480 GiByte >>> into a MACCHIATObin Double Shot's PCIe in a system that's microsd >>> card had the EDK2-variant build from: >>>=20 >>> https://unrelentingtech=2Es3=2Edualstack=2Eeu-west-1=2Eamazonaws=2Ecom= /flash-image-2020-07-01-mainline-tfa=2Ebin >>>=20 >>> and the system just worked (/dev/nda0)=2E I updated the FreeBSD in >>> this configuration and that booted too=2E >>>=20 >>> (The Optane was originally initialized while in a amd64 system >>> and so was boot-ready when first plugged into an aarch64=2E) >>>=20 >>> This is not the MACCHIATObin's normal configuration and things >>> were put back to normal after the experiment=2E >>>=20 >>> The MACCHIATObin Double Shot has 4 Cortex-A72 cores=2E >>>=20 >>=20 >> MacchiatoBin has fully opensource firmware, with the mainline >> edk2/TF-A one can boot FreeBSD with DT or ACPI=2E The referenced image >> from Greg should also be fine=2E The only significant interface missing >> is the built-in PP2 NIC=2E Interestingly, OpenBSD already has a mvpp2 driver=2E I don't really have t= he motivation to port it right now, but hey, someone could=E2=80=A6 >My memory was that there was some issue of "legacy" >PCIe devices showing up as duplicated and some change >was put in that avoided that --but prevented "modern" >PCIe devices from working=2E As I remember, disabling >the change was one reason Greg created his variant: >upstream choose which type of devices it wanted to >support and Greg went the other way=2E (No one has >support covering both contexts on the MACCHIATObin >Double Short?) Last thing I remember, Marcin promised to make a setup menu toggle for the= offset ;) > removal of a headless flag in FADT=20 I don't know if that even affects anything, I probably just copied the cha= nge from somewhere, but I like it out of a pure desire for correctness=2E >There were also edk2 additions of 3 lines >involving something like: > >MdeModulePkg/Bus/Pci/NvmExpressDxe/NvmExpressDxe=2Einf This might've happened upstream too by now, but yes, this is necessary to = boot from NVMe=2E