From owner-freebsd-arm@freebsd.org Tue Oct 15 10:03:59 2019 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 37A4815A3FE for ; Tue, 15 Oct 2019 10:03:59 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46srcF6jtyz40Xg for ; Tue, 15 Oct 2019 10:03:57 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 35595658; Tue, 15 Oct 2019 12:03:55 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=bJGJlylnKoCs7exPCpOSMLVG2KY=; b=seZxlKv8nS2bVw5bg5VlMCjGdoew oT0FbuTgadWZaaEEMQwiLC2r99Cg3/h4WU2l1Zgpl9s7+Km08U9D/J3ULq8LRsbs KMuqqsQaQOykIRpPT0c2IQ4wIpMolijM/e88RjoYUI54vKGhCGx7Bq5C1UuftRnR ZVHkvEjkouNGCgY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=XYzskallco8CVP+wQpc9nmKsqoMq9ncpt6yVn7BAvY14BhD8KRnwmPp9 txTvIx/qEp6IhzBjHes+fUvwN6ZCk1OTy3fawN/+MyuYz/JW/lADugOMpfrwz01W Iz4ohcWPT4c77IqwH8SSU0BRTrcD8sVabjOZe5D6SFq4zxXhjik= Received: from sonic.home.blih.net (ip-9.net-89-3-105.rev.numericable.fr [89.3.105.9]) by mail.blih.net (OpenSMTPD) with ESMTPSA id d8e58048 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Tue, 15 Oct 2019 12:03:55 +0200 (CEST) Date: Tue, 15 Oct 2019 12:03:55 +0200 From: Emmanuel Vadot To: Henri Hennebert Cc: Henri Hennebert via freebsd-arm , Thomas Skibo Subject: Re: PINE64+ 2GB - with U-Boot SPL 2019.10 - bootaa64.efi do not find UFS partition Message-Id: <20191015120355.91c54cbd23d2bf95c9566f7e@bidouilliste.com> In-Reply-To: References: <15D5331A-C76D-4EBC-8992-9B04A0C0EDC5@yahoo.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 46srcF6jtyz40Xg X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bidouilliste.com header.s=mail header.b=seZxlKv8; dmarc=none; spf=pass (mx1.freebsd.org: domain of manu@bidouilliste.com designates 212.83.177.182 as permitted sender) smtp.mailfrom=manu@bidouilliste.com X-Spamd-Result: default: False [-1.36 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bidouilliste.com:s=mail]; NEURAL_HAM_MEDIUM(-0.84)[-0.845,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:212.83.177.182/32]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[bidouilliste.com]; NEURAL_HAM_LONG(-1.00)[-0.997,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[bidouilliste.com:+]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(0.38)[ip: (-0.69), ipnet: 212.83.160.0/19(2.46), asn: 12876(0.11), country: FR(-0.00)]; ASN(0.00)[asn:12876, ipnet:212.83.160.0/19, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Oct 2019 10:03:59 -0000 On Tue, 15 Oct 2019 10:26:24 +0200 Henri Hennebert via freebsd-arm wrote: > On 10/13/19 8:41 PM, Thomas Skibo via freebsd-arm wrote: > >> > >> I put FreeBSD-12.1-RC1-arm64-aarch64-PINE64.img on the sd card. It is > >> created with u-boot 2019-07 and boot correctly. > >> > >> If I put u-boot 2019-10 the same problem occurs. > >=20 > > Without r352446, loader.efi cannot work with u-boot 2019.10. So, a 12.= 1 image isn?t going to be compatible with u-boot 2019.10. I?ve verified th= is on a Zynq board. > >=20 > > Also, boot1.efi won?t work with u-boot 2019.10 but I tried Emmanuel?s s= uggestion to use loader.efi directly and that worked. Then, as an experime= nt I backed out change r352446 in the loader and I got all the same error m= essages as Henri. > >=20 > > releng/12.1 at r353543 have loader.efi (as bootaa64.efi) booting the=20 > kernel with u-boot 2019.10 :-) >=20 > The error is still there with boot1.efi as bootaa64.efi. >=20 > Henri This will not be fixed. boot1.efi was never used for arm/arm64 and the main goal is to remove it anyway. --=20 Emmanuel Vadot