From nobody Wed May 22 17:20:11 2024 X-Original-To: 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 4VkykX1xq1z5M55v for ; Wed, 22 May 2024 17:20:52 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) (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 4VkykW6xQpz4gbh for ; Wed, 22 May 2024 17:20:51 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x1030.google.com with SMTP id 98e67ed59e1d1-2b432be5cc9so1455642a91.3 for ; Wed, 22 May 2024 10:20:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1716398448; x=1717003248; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ljScmBrc+OU/KcqOq5rYXbsfWey+FWtv83yq2Y9Hb7g=; b=AbSClAY0/O1C2ERJd+0C7v/9KUdxpmAGo+Xq4CXX2RZB/D4fg8wU9A4SchrNdh7sxy mGO0/lulCB3QGORNvaFwmtWVdnjnrPAqxoq+P2b+XreCgqBOyIf2nJdfAUuoIfDWgE7t RZyYeqKveuszSYDYJoO+l6zj6e79BW5Pq2Pcp14O5gWfaHOD6N6RbWSL3gfgI6AoN7LE aoVqnvtIqXsMdZukMyJJ0qh3HPOJlGNH7T3mjYjIdX4KBYucIiV67KSWqk31LFUltpK4 xuQ46gZU1kIhGUQpd8QkSAVELp4umehHvZkkvWWjd3dlmJDHyf0cZeKRnSL0e9j8basH 0BtQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716398448; x=1717003248; 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=ljScmBrc+OU/KcqOq5rYXbsfWey+FWtv83yq2Y9Hb7g=; b=MPiZPfJuRYf/syD5IDuTs5gh4TbYjWDEZhs6nnV+oigMMFUClMIaRfJEbKcjMvXztN ekZXBFmSrfuaervkfnPGB9K4oJnFTJL8At6G4tBbS059YA7K6X4n9aBaEPINdB/C67n9 9H3VCc6yw3Ht8n3niHmh2qpmDpeFcKbSR0/0TA3QcNzY8GjVCuBPgYNbUK9hwd0T5mqE 70nm8uJ8qlaG/3njN6P8yHHjvH47MuaD75bRBpDnJevPCAZeSONTI5Vzd23X+ipRfSOO gytDCLp2V14YIjuXUZt6DSKOypUXYKPUwJCktBBuHOUnkcbKap5a93UwQJFg3z4AdHBX siWg== X-Forwarded-Encrypted: i=1; AJvYcCXDEK8Z5EKPzGYucdsM4ifT3DQAfd5ll1+cI06BSKqvenFxs6HOumuExWAsSN5syO48yqR8HRDsetI8kiSY2TA= X-Gm-Message-State: AOJu0YwWbyB5PNcLokIF1XkBAI1VnKuA9nKR84qgv5DpuBE2weJIC56F QdyCUS+nw67+vaDef93eaaIWEThxazMmo7P3tUmSuBRMjJV+SFMLL93BzZzl988U/I/7fXUGREF Kb4P+/8J/c5WpORoFuXiz13Y8Fs2U2F5cdTg= X-Google-Smtp-Source: AGHT+IEus+BOKV6a6GD+h76/ay7FWSEMHczk1u2fTtt6J+6CIR6be+Z2zQOYnLjpBwU6hDx53w5haCdPaF1qyBvhcpw= X-Received: by 2002:a17:90a:1788:b0:2ae:6e16:da91 with SMTP id 98e67ed59e1d1-2bd9f461d5fmr2772559a91.29.1716398447509; Wed, 22 May 2024 10:20:47 -0700 (PDT) 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: <18B789E4-5891-4F3E-BAB6-05FD45949438@yahoo.com> <1923834610.13708.1716392599662@localhost> <6117F301-D584-40F7-9022-F90103FF5468@yahoo.com> In-Reply-To: <6117F301-D584-40F7-9022-F90103FF5468@yahoo.com> From: Mario Marietto Date: Wed, 22 May 2024 19:20:11 +0200 Message-ID: Subject: Re: vmm (bhyve) on GICv2 To: Mark Millard Cc: Ronald Klop , arm@freebsd.org, Lexi Winter Content-Type: multipart/alternative; boundary="000000000000c1ce3406190e278c" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4VkykW6xQpz4gbh --000000000000c1ce3406190e278c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Can someone confirm that bhyve works ok on the RockPro64 (RK3399) ? Has bhyve been patched in relation to this bug : https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D277559 ? I read that there is a huge amount of work to do on the RPI5 before it works with FreeBSD. And anyway,it does not support bhyve. So if I will buy a soc,it will be the RockPro64.... On Wed, May 22, 2024 at 6:50=E2=80=AFPM Mark Millard wr= ote: > On May 22, 2024, at 08:43, Ronald Klop wrote: > > > >> Van: Mark Millard > >> Datum: woensdag, 22 mei 2024 17:34 > >> Aan: Lexi Winter > >> CC: Mario Marietto , arm@freebsd.org > >> Onderwerp: Re: vmm (bhyve) on GICv2 > >> On May 22, 2024, at 00:25, Lexi Winter wrote: > >> > >> > Mario Marietto: > >> >> On Wed, May 22, 2024 at 9:03AM Lexi Winter wrote: > >> >>> i was pleased to see ARM64 vmm has been merged to main recently. > >> >>> > >> >>> i have several use-cases to run bhyve on RPi4, but unfortunately > this > >> >>> hardware only supports GICv2 while vmm requires GICv3. > >> >>> > >> >>> does anyone have an idea if GICv2 is likely to be supported in the > >> >>> future? > >> >> > >> >> Does RPi5 support GICv3 ? I would like to know which kind of > relatively > >> >> cheap arm hardware can run bhyve. > >> > > >> > i don't know off hand, but i do know FreeBSD doesn't support RPi5 at > >> > all right now, so this is not an immediate solution :-) > >> > >> I boot and run a RPi5 via EDK2 in the microsd card slot and a USB3 > >> UFS system media (that has lots of different swap partition sizes > >> for use on various machines with widely varying amounts of RAM): > >> > >> # gpart show -pl > >> =3D> 40 249737136 mmcsd0 GPT (119G) > >> 40 2008 - free - (1.0M) > >> 2048 249733120 mmcsd0p1 RPi5-edk2 (119G) > >> 249735168 2008 - free - (1.0M) > >> > >> =3D> 34 1875384941 da0 GPT (894G) > >> 34 32734 - free - (16M) > >> 32768 501760 da0p1 PkgBaseEFI (245M) > >> 534528 20971520 da0p2 PkgBaseSwp10 (10G) > >> 21506048 29360128 da0p3 PkgBaseSwp14 (14G) > >> 50866176 33554432 da0p4 PkgBaseSwp16 (16G) > >> 84420608 67108864 da0p5 PkgBaseSwp32 (32G) > >> 151529472 96468992 da0p6 PkgBaseSwp46 (46G) > >> 247998464 268435456 da0p7 PkgBaseSwp128 (128G) > >> 516433920 7340032 da0p8 PkgBaseSwp3p5 (3.5G) > >> 523773952 13631488 da0p10 PkgBaseSwp6p5 (6.5G) > >> 537405440 1337979528 da0p9 PkgBaseUFS (638G) > >> 1875384968 7 - free - (3.5K) > >> > >> See: https://github.com/worproject/rpi5-uefi > >> > >> # uname -apKU > >> FreeBSD aarch64-main-pkgs 15.0-CURRENT FreeBSD 15.0-CURRENT #5 > main-n269589-9dcf39575efb-dirty: Sun Apr 21 01:42:00 PDT 2024 > root@aarch64-main-pbase:/usr/obj/BUILDs/main-CA76-nodbg-clang/usr/main-s= rc/arm64.aarch64/sys/GENERIC-NODBG-CA76 > arm64 aarch64 1500018 1500018 > >> > >> That kernel is at: /boot/kernel.CA76-NODBG/kernel in my context. > >> > >> But I also have kernels that I got from: > >> > >> https://pkg.freebsd.org/FreeBSD:15:aarch64/base_latest/ > >> > >> that boot it as well: > >> > >> # strings /boot/kernel.GENERIC-NODEBUG/kernel | grep 15.0- > >> @(#)FreeBSD 15.0-CURRENT main-n269581-dfa39133b333 GENERIC-NODEBUG > >> FreeBSD 15.0-CURRENT main-n269581-dfa39133b333 GENERIC-NODEBUG > >> 15.0-CURRENT > >> > >> And the debug version (witness and such): > >> > >> # strings /boot/kernel/kernel | grep 15.0- > >> @(#)FreeBSD 15.0-CURRENT main-n269581-dfa39133b333 GENERIC > >> FreeBSD 15.0-CURRENT main-n269581-dfa39133b333 GENERIC > >> 15.0-CURRENT > >> > >> (It has beem a while since I updated.) > >> > >> All these kernels boot a world that I got from the same: > >> > >> https://pkg.freebsd.org/FreeBSD:15:aarch64/base_latest/ > >> > >> I do have another world in a directory tree that I built that I > >> can chroot to. > >> > >> =3D=3D=3D > >> Mark Millard > >> marklmi at yahoo.com > >> > > > > > > Hi, > > > > This looks nice. Are there any FreeBSD patches needed to boot a RPI5? O= r > only an up-to-date EDK2? > > The kernels and world installed via use of: > > https://pkg.freebsd.org/FreeBSD:15:aarch64/base_latest/ > > that I referenced were/are used unmodified. Those materials are > as built by the FreeBSD project, not built by me. > > I build my other kernels and the world that I can chroot to > in order to experiment with builds that explicitly target > Cortext-A76 instruction set compatible aarch64 contexts. Such > is not required. The same Cortex-A76 kernels and world can be > used on the Windows DevKit 2023's combination of Cortex-X1C's > and Cortex-A78C's. > > I have only tried EDK2 as distributed via: > > https://github.com/worproject/rpi5-uefi/ > > I have not built it myself. > > > And if it works well can we collaborate in documenting the RPI5 on > https://wiki.freebsd.org/arm/Raspberry%20Pi? > > I'll note that my normal use is headless: serial console and > ssh-over-ethernet. The EtherNet use is via a USB3 dongle: the > built-in EtherNet is not supported via EDK2. > > Also, I leave the microsd card that has EDK2 on it in the > microsd card slot and do not normally have it mounted. But > the /etc/fstab that I use has a line: > > /dev/gpt/RPi5-edk2 /RPi5-edk2 msdosfs rw,noatime,noauto > 0 0 > > to mount it when desired. Presuming the /RPi5-edk2/ was > created previously: > > # mount /RPi5-edk2 > > # ls -loaT /RPi5-edk2 > total 2180 > drwxr-xr-x 1 root wheel - 32768 Dec 31 23:00:00 1979 . > drwxr-xr-x 26 root wheel - 512 May 22 09:29:16 2024 .. > -rwxr-xr-x 1 root wheel uarch 2031616 Mar 16 03:43:48 2024 RPI_EFI.fd > -rwxr-xr-x 1 root wheel - 76038 Mar 15 20:46:12 2024 > bcm2712-rpi-5-b.dtb > -rwxr-xr-x 1 root wheel uarch 474 Apr 19 18:38:24 2024 config.txt > -rwxr-xr-x 1 root wheel uarch 474 Apr 19 18:38:24 2024 > config.txt.m_m_edk2_rpi5 > > # cat /RPi5-edk2/config.txt > armstub=3DRPI_EFI.fd > device_tree_address=3D0x1f0000 > device_tree_end=3D0x210000 > > # Force 32 bpp framebuffer allocation. > framebuffer_depth=3D32 > > # Disable compensation for displays with overscan. > disable_overscan=3D1 > > # Force maximum USB power regardless of the power supply. > usb_max_current_enable=3D1 > > # Force maximum CPU speed. > force_turbo=3D1 > > # > # Local additions: > enable_uart=3D1 > uart_2ndstage=3D1 > dtdebug=3D1 > disable_commandline_tags=3D1 > # > [pi5] > over_voltage_delta=3D100000 > arm_freq=3D2600 > [all] > > The local additions are not required. > > I'll note that: > > https://github.com/worproject/rpi5-uefi/blob/master/README.md > > documents ACPI mode as supporting (extracted from a table): > > OS: FreeBSD > Version: 13.2 > Tested/supported hardware: Display, UART, USB, SD, PCIe > Notes: * SD is limited to HS. > > DeviceTree mode is documented with just: > > QUOTE > The included DTB is meant for the RPi downstream 6.1.y kernel. > END QUOTE > > And, so, FreeBSD is likely not a useful match to DeviceTree > mode at this time. > > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > > --=20 Mario. --000000000000c1ce3406190e278c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Can someone confirm that bhyve works ok on the RockPr= o64 (RK3399) ? Has bhyve been patched in relation to this bug :
<= br>

?

I read= that there is a huge amount of work to do on the RPI5 before it works with= FreeBSD. And anyway,it does not support bhyve. So if I will buy a soc,it w= ill be the RockPro64....



<= div class=3D"gmail_quote">
On Wed, May= 22, 2024 at 6:50=E2=80=AFPM Mark Millard <marklmi@yahoo.com> wrote:
On May 22, 2024, at 08:43, Ronal= d Klop <ronald= -lists@klop.ws> wrote:


>> Van: Mark Millard <marklmi@yahoo.com>
>> Datum: woensdag, 22 mei 2024 17:34
>> Aan: Lexi Winter <lexi@le-fay.org>
>> CC: Mario Marietto <marietto2008@gmail.com>, arm@freebsd.org
>> Onderwerp: Re: vmm (bhyve) on GICv2
>> On May 22, 2024, at 00:25, Lexi Winter <lexi@le-fay.org> wrote:
>>
>> > Mario Marietto:
>> >> On Wed, May 22, 2024 at 9:03AM Lexi Winter <lexi@le-fay.org> wrote: >> >>> i was pleased to see ARM64 vmm has been merged to mai= n recently.
>> >>>
>> >>> i have several use-cases to run bhyve on RPi4, but un= fortunately this
>> >>> hardware only supports GICv2 while vmm requires GICv3= .
>> >>>
>> >>> does anyone have an idea if GICv2 is likely to be sup= ported in the
>> >>> future?
>> >>
>> >> Does RPi5 support GICv3 ? I would like to know which kind= of relatively
>> >> cheap arm hardware can run bhyve.
>> >
>> > i don't know off hand, but i do know FreeBSD doesn't = support RPi5 at
>> > all right now, so this is not an immediate solution :-)
>>
>> I boot and run a RPi5 via EDK2 in the microsd card slot and a USB3=
>> UFS system media (that has lots of different swap partition sizes<= br> >> for use on various machines with widely varying amounts of RAM): >>
>> # gpart show -pl
>> =3D>=C2=A0 =C2=A0 =C2=A0 =C2=A040=C2=A0 249737136=C2=A0 =C2=A0 = mmcsd0=C2=A0 GPT=C2=A0 (119G)
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 40=C2=A0 =C2=A0 =C2=A0 =C2=A0200= 8=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - free -=C2=A0 (1.0M)
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 2048=C2=A0 249733120=C2=A0 mmcsd0p1=C2= =A0 RPi5-edk2=C2=A0 (119G)
>>=C2=A0 =C2=A0249735168=C2=A0 =C2=A0 =C2=A0 =C2=A02008=C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 - free -=C2=A0 (1.0M)
>>
>> =3D>=C2=A0 =C2=A0 =C2=A0 =C2=A0 34=C2=A0 1875384941=C2=A0 =C2= =A0 =C2=A0da0=C2=A0 GPT=C2=A0 (894G)
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A034=C2=A0 =C2=A0 =C2=A0 =C2= =A032734=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - free -=C2=A0 (16M)
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 32768=C2=A0 =C2=A0 =C2=A0 501760=C2=A0 = =C2=A0da0p1=C2=A0 PkgBaseEFI=C2=A0 (245M)
>>=C2=A0 =C2=A0 =C2=A0 =C2=A0534528=C2=A0 =C2=A0 20971520=C2=A0 =C2= =A0da0p2=C2=A0 PkgBaseSwp10=C2=A0 (10G)
>>=C2=A0 =C2=A0 =C2=A021506048=C2=A0 =C2=A0 29360128=C2=A0 =C2=A0da0p= 3=C2=A0 PkgBaseSwp14=C2=A0 (14G)
>>=C2=A0 =C2=A0 =C2=A050866176=C2=A0 =C2=A0 33554432=C2=A0 =C2=A0da0p= 4=C2=A0 PkgBaseSwp16=C2=A0 (16G)
>>=C2=A0 =C2=A0 =C2=A084420608=C2=A0 =C2=A0 67108864=C2=A0 =C2=A0da0p= 5=C2=A0 PkgBaseSwp32=C2=A0 (32G)
>>=C2=A0 =C2=A0 151529472=C2=A0 =C2=A0 96468992=C2=A0 =C2=A0da0p6=C2= =A0 PkgBaseSwp46=C2=A0 (46G)
>>=C2=A0 =C2=A0 247998464=C2=A0 =C2=A0268435456=C2=A0 =C2=A0da0p7=C2= =A0 PkgBaseSwp128=C2=A0 (128G)
>>=C2=A0 =C2=A0 516433920=C2=A0 =C2=A0 =C2=A07340032=C2=A0 =C2=A0da0p= 8=C2=A0 PkgBaseSwp3p5=C2=A0 (3.5G)
>>=C2=A0 =C2=A0 523773952=C2=A0 =C2=A0 13631488=C2=A0 da0p10=C2=A0 Pk= gBaseSwp6p5=C2=A0 (6.5G)
>>=C2=A0 =C2=A0 537405440=C2=A0 1337979528=C2=A0 =C2=A0da0p9=C2=A0 Pk= gBaseUFS=C2=A0 (638G)
>>=C2=A0 =C2=A01875384968=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A07= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - free -=C2=A0 (3.5K)
>>
>> See: https://github.com/worproject/rpi5-uefi
>>
>> # uname -apKU
>> FreeBSD aarch64-main-pkgs 15.0-CURRENT FreeBSD 15.0-CURRENT #5 mai= n-n269589-9dcf39575efb-dirty: Sun Apr 21 01:42:00 PDT 2024=C2=A0 =C2=A0 =C2= =A0root@aarch64-main-pbase:/usr/obj/BUILDs/main-CA76-nodbg-clang/usr/main-s= rc/arm64.aarch64/sys/GENERIC-NODBG-CA76 arm64 aarch64 1500018 1500018
>>
>> That kernel is at: /boot/kernel.CA76-NODBG/kernel in my context. >>
>> But I also have kernels that I got from:
>>
>> https://pkg.freebsd.org/FreeBSD:15:a= arch64/base_latest/
>>
>> that boot it as well:
>>
>> # strings /boot/kernel.GENERIC-NODEBUG/kernel | grep 15.0-
>> @(#)FreeBSD 15.0-CURRENT main-n269581-dfa39133b333 GENERIC-NODEBUG=
>> FreeBSD 15.0-CURRENT main-n269581-dfa39133b333 GENERIC-NODEBUG
>> 15.0-CURRENT
>>
>> And the debug version (witness and such):
>>
>> # strings /boot/kernel/kernel | grep 15.0-
>> @(#)FreeBSD 15.0-CURRENT main-n269581-dfa39133b333 GENERIC
>> FreeBSD 15.0-CURRENT main-n269581-dfa39133b333 GENERIC
>> 15.0-CURRENT
>>
>> (It has beem a while since I updated.)
>>
>> All these kernels boot a world that I got from the same:
>>
>> https://pkg.freebsd.org/FreeBSD:15:a= arch64/base_latest/
>>
>> I do have another world in a directory tree that I built that I >> can chroot to.
>>
>> =3D=3D=3D
>> Mark Millard
>> marklmi at yahoo.com
>>
>=C2=A0 =C2=A0
>
> Hi,
>
> This looks nice. Are there any FreeBSD patches needed to boot a RPI5? = Or only an up-to-date EDK2?

The kernels and world installed via use of:

https://pkg.freebsd.org/FreeBSD:15:aarch64/ba= se_latest/

that I referenced were/are used unmodified. Those materials are
as built by the FreeBSD project, not built by me.

I build my other kernels and the world that I can chroot to
in order to experiment with builds that explicitly target
Cortext-A76 instruction set compatible aarch64 contexts. Such
is not required. The same Cortex-A76 kernels and world can be
used on the Windows DevKit 2023's combination of Cortex-X1C's
and Cortex-A78C's.

I have only tried EDK2 as distributed via:

https://github.com/worproject/rpi5-uefi/

I have not built it myself.

> And if it works well can we collaborate in documenting the RPI5 on https://wiki.freebsd.org/arm/Raspberry%20Pi?

I'll note that my normal use is headless: serial console and
ssh-over-ethernet. The EtherNet use is via a USB3 dongle: the
built-in EtherNet is not supported via EDK2.

Also, I leave the microsd card that has EDK2 on it in the
microsd card slot and do not normally have it mounted. But
the /etc/fstab that I use has a line:

/dev/gpt/RPi5-edk2=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 /RPi5-ed= k2=C2=A0 =C2=A0 =C2=A0 msdosfs rw,noatime,noauto=C2=A0 =C2=A0 =C2=A0 =C2=A0= 0=C2=A0 =C2=A0 =C2=A0 =C2=A00

to mount it when desired. Presuming the /RPi5-edk2/ was
created previously:

# mount /RPi5-edk2

# ls -loaT /RPi5-edk2
total 2180
drwxr-xr-x=C2=A0 =C2=A01 root wheel -=C2=A0 =C2=A0 =C2=A0 =C2=A032768 Dec 3= 1 23:00:00 1979 .
drwxr-xr-x=C2=A0 26 root wheel -=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0512 May 2= 2 09:29:16 2024 ..
-rwxr-xr-x=C2=A0 =C2=A01 root wheel uarch 2031616 Mar 16 03:43:48 2024 RPI_= EFI.fd
-rwxr-xr-x=C2=A0 =C2=A01 root wheel -=C2=A0 =C2=A0 =C2=A0 =C2=A076038 Mar 1= 5 20:46:12 2024 bcm2712-rpi-5-b.dtb
-rwxr-xr-x=C2=A0 =C2=A01 root wheel uarch=C2=A0 =C2=A0 =C2=A0474 Apr 19 18:= 38:24 2024 config.txt
-rwxr-xr-x=C2=A0 =C2=A01 root wheel uarch=C2=A0 =C2=A0 =C2=A0474 Apr 19 18:= 38:24 2024 config.txt.m_m_edk2_rpi5

# cat /RPi5-edk2/config.txt
armstub=3DRPI_EFI.fd
device_tree_address=3D0x1f0000
device_tree_end=3D0x210000

# Force 32 bpp framebuffer allocation.
framebuffer_depth=3D32

# Disable compensation for displays with overscan.
disable_overscan=3D1

# Force maximum USB power regardless of the power supply.
usb_max_current_enable=3D1

# Force maximum CPU speed.
force_turbo=3D1

#
# Local additions:
enable_uart=3D1
uart_2ndstage=3D1
dtdebug=3D1
disable_commandline_tags=3D1
#
[pi5]
over_voltage_delta=3D100000
arm_freq=3D2600
[all]

The local additions are not required.

I'll note that:

https://github.com/worproject/rpi5-uefi= /blob/master/README.md

documents ACPI mode as supporting (extracted from a table):

OS:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 FreeBSD
Version:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A013.2
Tested/supported hardware: Display, UART, USB, SD, PCIe
Notes:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0* SD is limited to HS.

DeviceTree mode is documented with just:

QUOTE
The included DTB is meant for the RPi downstream 6.1.y kernel.
END QUOTE

And, so, FreeBSD is likely not a useful match to DeviceTree
mode at this time.

=3D=3D=3D
Mark Millard
marklmi at yahoo.com



--
Mario.
--000000000000c1ce3406190e278c--