From nobody Tue Dec 06 03:35:31 2022 X-Original-To: freebsd-arm@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 4NR5fS04RXz4jYdH for ; Tue, 6 Dec 2022 03:35:44 +0000 (UTC) (envelope-from archimedes.gaviola@gmail.com) Received: from mail-yb1-xb32.google.com (mail-yb1-xb32.google.com [IPv6:2607:f8b0:4864:20::b32]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NR5fR4G0bz3GkG for ; Tue, 6 Dec 2022 03:35:43 +0000 (UTC) (envelope-from archimedes.gaviola@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yb1-xb32.google.com with SMTP id d131so13665357ybh.4 for ; Mon, 05 Dec 2022 19:35:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=fxKlpi4AAxlGBCIa0+Lh/zZOQm8ylquzkkdmfEoYb9s=; b=kkr7nj+BYR/C0fU1qTSDAom0qMVjGsgMu5nil2SR8nB89BzcZB35B4Nxw045o9ZNY6 rS65lrKldwhyd4bUG8PMsvYUkfqcwxHBLM2jRsjSkKBhOKEU8WWSEno8/YiRcDDlzidc HqMckxT1wY0R1JOIiL600O8KJGh1MWi4xXtb2+8HuYhBbL/TferMzrennnBDRj7hQ2xQ IkC8XrXL0v+4rxICPyy1qhoI6aCdJ929CQjRlODh+z7w+YfOSlbh01Ezk6XYutr63liR YTQDgBqxqNuvBnC13WialALOMUA1TlHaX/LKPJDymbwShFZvPjJMJNhOIDyDAO0mk+rX YKAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=fxKlpi4AAxlGBCIa0+Lh/zZOQm8ylquzkkdmfEoYb9s=; b=WDPaJMJY1fU14G5AxHar5l0Z2I6sc4EYJSRPAP7iyDqZx9CWMiwqS4a8kYzkGe2aDZ BC5Vv+s94Fui2ye2vs4Hs4SSjSyNN00zcnGOapKhw0/D3dA9e2Wi4V8f0Zzv9wpaOBgB T0VoKLP49egqD3/h45AkaNeM8nMnKQfhGTgcKvbL0Y6JOW1b7jIMxMfbsXFyEI281bC+ 09Bip3tY1b1kHjsf1wCYotCejDiUqWVaI/rKV0qS1yvvYDOyxIQSQtjh8M3LhYVMA/lF +Wr5ed6v5VVJeSGOR5fGDQPts2oia5PQFzR9Z8IzgyWgrzuIm9WzlFTTr7Hk3jv1di1y drcA== X-Gm-Message-State: ANoB5pkS9Hju4g46UmSrTcZbjNAQZrQip7Ap9HPUND5U/9Ghz2HScX8T 30kypjU36UD6HaRRGzwkumXcmS0LDXzDpu4E4Yo= X-Google-Smtp-Source: AA0mqf7U98zksXycYhVZBc6GbWcYE7FwXWiL7N66BwkuHMqp+qcsOO6xMNAy6cTmSDa56Z3ZRX7zC6IxbuQt9QbiTgA= X-Received: by 2002:a25:24c3:0:b0:6cd:3a43:cd47 with SMTP id k186-20020a2524c3000000b006cd3a43cd47mr61316369ybk.428.1670297742619; Mon, 05 Dec 2022 19:35:42 -0800 (PST) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Archimedes Gaviola Date: Tue, 6 Dec 2022 11:35:31 +0800 Message-ID: Subject: Re: Raspberry Pi 3B loader.efi and bootaa64.efi To: Warner Losh Cc: "freebsd-arm@freebsd.org" Content-Type: multipart/alternative; boundary="0000000000009e3a7305ef207f78" X-Rspamd-Queue-Id: 4NR5fR4G0bz3GkG X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --0000000000009e3a7305ef207f78 Content-Type: text/plain; charset="UTF-8" On Tue, Dec 6, 2022 at 10:56 AM Warner Losh wrote: > > > On Mon, Dec 5, 2022, 7:51 PM Archimedes Gaviola < > archimedes.gaviola@gmail.com> wrote: > >> Hi, >> >> Is there any difference between /boot/loader.efi and >> /boot/msdos/EFI/BOOT/bootaa64.efi? I have successfully created an RPi 3B >> image from scratch but I just copied the bootaa64.efi from my build machine >> to the image and it booted successfully. Lately I found out that when >> /boot/loader.efi is copied and renamed as >> /boot/msdos/EFI/BOOT/bootaa64.efi, it will boot successfully as well. >> > > > Typically they are the same thing. > Hi Warner, Thanks for your response and confirmation! At least this time I will use the loader.efi as my source for bootaa64.efi everytime I build an image. Thanks and best regards, Archimedes > Warner > >> Thanks and best regards, >> Archimedes >> -- >> Archimedes Gaviola >> > -- Archimedes Gaviola --0000000000009e3a7305ef207f78 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Tue, Dec 6, 2022 at 10:56 AM Warner Losh <imp@bsdimp.com> wrote:


On Mon, Dec 5, 2022, 7:51 PM Archime= des Gaviola <archimedes.gaviola@gmail.com> wrote:
Hi,

Is there a= ny difference between /boot/loader.efi and /boot/msdos/EFI/BOOT/bootaa64.ef= i? I have successfully created an RPi 3B image from scratch but I just copi= ed the bootaa64.efi from my build machine to the image and it booted succes= sfully. Lately I found out that when /boot/loader.efi is copied and renamed= as /boot/msdos/EFI/BOOT/bootaa64.efi, it will boot successfully as well.

=
Typically they are the same thing.
<= /blockquote>

Hi Warner,
<= div dir=3D"auto">
Thanks for your response and c= onfirmation! At least this time I will use the loader.efi as my source for = bootaa64.efi everytime I build an image.

<= div dir=3D"auto">Thanks and=C2=A0best regards,
Archi= medes


Warner=C2=A0
Thanks= and=C2=A0best regards,
Archimedes
--
Archimedes Gaviola
--
Archimedes Gaviola
--0000000000009e3a7305ef207f78--