Date: Wed, 22 May 2024 19:20:11 +0200 From: Mario Marietto <marietto2008@gmail.com> To: Mark Millard <marklmi@yahoo.com> Cc: Ronald Klop <ronald-lists@klop.ws>, arm@freebsd.org, Lexi Winter <lexi@le-fay.org> Subject: Re: vmm (bhyve) on GICv2 Message-ID: <CA%2B1FSijd2abM9a5B98CAMRApUJt7UhTgrQrj%2BZvVHwJv2rT7tQ@mail.gmail.com> In-Reply-To: <6117F301-D584-40F7-9022-F90103FF5468@yahoo.com> References: <Zk2YnPCESoEHC-8D@ilythia.eden.le-fay.org> <CA%2B1FSihooPem=qRFFU7RG21UKUf-uCrW_CPMvH1NxROArXivPA@mail.gmail.com> <Zk2d8lACXhhD9V9p@ilythia.eden.le-fay.org> <18B789E4-5891-4F3E-BAB6-05FD45949438@yahoo.com> <1923834610.13708.1716392599662@localhost> <6117F301-D584-40F7-9022-F90103FF5468@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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 <marklmi@yahoo.com> wr= ote: > On May 22, 2024, at 08:43, Ronald 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 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 <div dir=3D"ltr"><div>Can someone confirm that bhyve works ok on the RockPr= o64 (RK3399) ? Has bhyve been patched in relation to this bug :</div><div><= br></div><div><a href=3D"https://bugs.freebsd.org/bugzilla/show_bug.cgi?id= =3D277559" target=3D"_blank">https://bugs.freebsd.org/bugzilla/show_bug.cgi= ?id=3D277559</a></div><div><br></div><div>?</div><div><br></div><div>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....<br></div><div><br></div><div><br></div></div><br><= div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, May= 22, 2024 at 6:50=E2=80=AFPM Mark Millard <<a href=3D"mailto:marklmi@yah= oo.com" target=3D"_blank">marklmi@yahoo.com</a>> wrote:<br></div><blockq= uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p= x solid rgb(204,204,204);padding-left:1ex">On May 22, 2024, at 08:43, Ronal= d Klop <<a href=3D"mailto:ronald-lists@klop.ws" target=3D"_blank">ronald= -lists@klop.ws</a>> wrote:<br> <br> <br> >> Van: Mark Millard <<a href=3D"mailto:marklmi@yahoo.com" target= =3D"_blank">marklmi@yahoo.com</a>><br> >> Datum: woensdag, 22 mei 2024 17:34<br> >> Aan: Lexi Winter <<a href=3D"mailto:lexi@le-fay.org" target=3D"= _blank">lexi@le-fay.org</a>><br> >> CC: Mario Marietto <<a href=3D"mailto:marietto2008@gmail.com" t= arget=3D"_blank">marietto2008@gmail.com</a>>, <a href=3D"mailto:arm@free= bsd.org" target=3D"_blank">arm@freebsd.org</a><br> >> Onderwerp: Re: vmm (bhyve) on GICv2<br> >> On May 22, 2024, at 00:25, Lexi Winter <<a href=3D"mailto:lexi@= le-fay.org" target=3D"_blank">lexi@le-fay.org</a>> wrote:<br> >> <br> >> > Mario Marietto:<br> >> >> On Wed, May 22, 2024 at 9:03AM Lexi Winter <<a href=3D= "mailto:lexi@le-fay.org" target=3D"_blank">lexi@le-fay.org</a>> wrote:<b= r> >> >>> i was pleased to see ARM64 vmm has been merged to mai= n recently.<br> >> >>><br> >> >>> i have several use-cases to run bhyve on RPi4, but un= fortunately this<br> >> >>> hardware only supports GICv2 while vmm requires GICv3= .<br> >> >>><br> >> >>> does anyone have an idea if GICv2 is likely to be sup= ported in the<br> >> >>> future?<br> >> >><br> >> >> Does RPi5 support GICv3 ? I would like to know which kind= of relatively<br> >> >> cheap arm hardware can run bhyve.<br> >> ><br> >> > i don't know off hand, but i do know FreeBSD doesn't = support RPi5 at<br> >> > all right now, so this is not an immediate solution :-)<br> >> <br> >> I boot and run a RPi5 via EDK2 in the microsd card slot and a USB3= <br> >> UFS system media (that has lots of different swap partition sizes<= br> >> for use on various machines with widely varying amounts of RAM):<b= r> >> <br> >> # gpart show -pl<br> >> =3D>=C2=A0 =C2=A0 =C2=A0 =C2=A040=C2=A0 249737136=C2=A0 =C2=A0 = mmcsd0=C2=A0 GPT=C2=A0 (119G)<br> >>=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)<br> >>=C2=A0 =C2=A0 =C2=A0 =C2=A0 2048=C2=A0 249733120=C2=A0 mmcsd0p1=C2= =A0 RPi5-edk2=C2=A0 (119G)<br> >>=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)<br> >> <br> >> =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)<br> >>=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)<br> >>=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)<br> >>=C2=A0 =C2=A0 =C2=A0 =C2=A0534528=C2=A0 =C2=A0 20971520=C2=A0 =C2= =A0da0p2=C2=A0 PkgBaseSwp10=C2=A0 (10G)<br> >>=C2=A0 =C2=A0 =C2=A021506048=C2=A0 =C2=A0 29360128=C2=A0 =C2=A0da0p= 3=C2=A0 PkgBaseSwp14=C2=A0 (14G)<br> >>=C2=A0 =C2=A0 =C2=A050866176=C2=A0 =C2=A0 33554432=C2=A0 =C2=A0da0p= 4=C2=A0 PkgBaseSwp16=C2=A0 (16G)<br> >>=C2=A0 =C2=A0 =C2=A084420608=C2=A0 =C2=A0 67108864=C2=A0 =C2=A0da0p= 5=C2=A0 PkgBaseSwp32=C2=A0 (32G)<br> >>=C2=A0 =C2=A0 151529472=C2=A0 =C2=A0 96468992=C2=A0 =C2=A0da0p6=C2= =A0 PkgBaseSwp46=C2=A0 (46G)<br> >>=C2=A0 =C2=A0 247998464=C2=A0 =C2=A0268435456=C2=A0 =C2=A0da0p7=C2= =A0 PkgBaseSwp128=C2=A0 (128G)<br> >>=C2=A0 =C2=A0 516433920=C2=A0 =C2=A0 =C2=A07340032=C2=A0 =C2=A0da0p= 8=C2=A0 PkgBaseSwp3p5=C2=A0 (3.5G)<br> >>=C2=A0 =C2=A0 523773952=C2=A0 =C2=A0 13631488=C2=A0 da0p10=C2=A0 Pk= gBaseSwp6p5=C2=A0 (6.5G)<br> >>=C2=A0 =C2=A0 537405440=C2=A0 1337979528=C2=A0 =C2=A0da0p9=C2=A0 Pk= gBaseUFS=C2=A0 (638G)<br> >>=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)<br> >> <br> >> See: <a href=3D"https://github.com/worproject/rpi5-uefi" rel=3D"no= referrer" target=3D"_blank">https://github.com/worproject/rpi5-uefi</a><br>; >> <br> >> # uname -apKU<br> >> 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<br> >> <br> >> That kernel is at: /boot/kernel.CA76-NODBG/kernel in my context.<b= r> >> <br> >> But I also have kernels that I got from:<br> >> <br> >> <a href=3D"https://pkg.freebsd.org/FreeBSD:15:aarch64/base_latest/= " rel=3D"noreferrer" target=3D"_blank">https://pkg.freebsd.org/FreeBSD:15:a= arch64/base_latest/</a><br> >> <br> >> that boot it as well:<br> >> <br> >> # strings /boot/kernel.GENERIC-NODEBUG/kernel | grep 15.0-<br> >> @(#)FreeBSD 15.0-CURRENT main-n269581-dfa39133b333 GENERIC-NODEBUG= <br> >> FreeBSD 15.0-CURRENT main-n269581-dfa39133b333 GENERIC-NODEBUG<br> >> 15.0-CURRENT<br> >> <br> >> And the debug version (witness and such):<br> >> <br> >> # strings /boot/kernel/kernel | grep 15.0-<br> >> @(#)FreeBSD 15.0-CURRENT main-n269581-dfa39133b333 GENERIC<br> >> FreeBSD 15.0-CURRENT main-n269581-dfa39133b333 GENERIC<br> >> 15.0-CURRENT<br> >> <br> >> (It has beem a while since I updated.)<br> >> <br> >> All these kernels boot a world that I got from the same:<br> >> <br> >> <a href=3D"https://pkg.freebsd.org/FreeBSD:15:aarch64/base_latest/= " rel=3D"noreferrer" target=3D"_blank">https://pkg.freebsd.org/FreeBSD:15:a= arch64/base_latest/</a><br> >> <br> >> I do have another world in a directory tree that I built that I<br= > >> can chroot to.<br> >> <br> >> =3D=3D=3D<br> >> Mark Millard<br> >> marklmi at <a href=3D"http://yahoo.com" rel=3D"noreferrer" target= =3D"_blank">yahoo.com</a><br> >> <br> >=C2=A0 =C2=A0<br> > <br> > Hi,<br> > <br> > This looks nice. Are there any FreeBSD patches needed to boot a RPI5? = Or only an up-to-date EDK2?<br> <br> The kernels and world installed via use of:<br> <br> <a href=3D"https://pkg.freebsd.org/FreeBSD:15:aarch64/base_latest/" rel=3D"= noreferrer" target=3D"_blank">https://pkg.freebsd.org/FreeBSD:15:aarch64/ba= se_latest/</a><br> <br> that I referenced were/are used unmodified. Those materials are<br> as built by the FreeBSD project, not built by me.<br> <br> I build my other kernels and the world that I can chroot to<br> in order to experiment with builds that explicitly target<br> Cortext-A76 instruction set compatible aarch64 contexts. Such<br> is not required. The same Cortex-A76 kernels and world can be<br> used on the Windows DevKit 2023's combination of Cortex-X1C's<br> and Cortex-A78C's.<br> <br> I have only tried EDK2 as distributed via:<br> <br> <a href=3D"https://github.com/worproject/rpi5-uefi/" rel=3D"noreferrer" tar= get=3D"_blank">https://github.com/worproject/rpi5-uefi/</a><br>; <br> I have not built it myself.<br> <br> > And if it works well can we collaborate in documenting the RPI5 on <a = href=3D"https://wiki.freebsd.org/arm/Raspberry%20Pi" rel=3D"noreferrer" tar= get=3D"_blank">https://wiki.freebsd.org/arm/Raspberry%20Pi</a>?<br>; <br> I'll note that my normal use is headless: serial console and<br> ssh-over-ethernet. The EtherNet use is via a USB3 dongle: the<br> built-in EtherNet is not supported via EDK2.<br> <br> Also, I leave the microsd card that has EDK2 on it in the<br> microsd card slot and do not normally have it mounted. But<br> the /etc/fstab that I use has a line:<br> <br> /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<br> <br> to mount it when desired. Presuming the /RPi5-edk2/ was<br> created previously:<br> <br> # mount /RPi5-edk2<br> <br> # ls -loaT /RPi5-edk2<br> total 2180<br> drwxr-xr-x=C2=A0 =C2=A01 root wheel -=C2=A0 =C2=A0 =C2=A0 =C2=A032768 Dec 3= 1 23:00:00 1979 .<br> 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 ..<br> -rwxr-xr-x=C2=A0 =C2=A01 root wheel uarch 2031616 Mar 16 03:43:48 2024 RPI_= EFI.fd<br> -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<br> -rwxr-xr-x=C2=A0 =C2=A01 root wheel uarch=C2=A0 =C2=A0 =C2=A0474 Apr 19 18:= 38:24 2024 config.txt<br> -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<br> <br> # cat /RPi5-edk2/config.txt<br> armstub=3DRPI_EFI.fd<br> device_tree_address=3D0x1f0000<br> device_tree_end=3D0x210000<br> <br> # Force 32 bpp framebuffer allocation.<br> framebuffer_depth=3D32<br> <br> # Disable compensation for displays with overscan.<br> disable_overscan=3D1<br> <br> # Force maximum USB power regardless of the power supply.<br> usb_max_current_enable=3D1<br> <br> # Force maximum CPU speed.<br> force_turbo=3D1<br> <br> #<br> # Local additions:<br> enable_uart=3D1<br> uart_2ndstage=3D1<br> dtdebug=3D1<br> disable_commandline_tags=3D1<br> #<br> [pi5]<br> over_voltage_delta=3D100000<br> arm_freq=3D2600<br> [all]<br> <br> The local additions are not required.<br> <br> I'll note that:<br> <br> <a href=3D"https://github.com/worproject/rpi5-uefi/blob/master/README.md" r= el=3D"noreferrer" target=3D"_blank">https://github.com/worproject/rpi5-uefi= /blob/master/README.md</a><br> <br> documents ACPI mode as supporting (extracted from a table):<br> <br> 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<br> Version:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A013.2<br> Tested/supported hardware: Display, UART, USB, SD, PCIe<br> 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.<br> <br> DeviceTree mode is documented with just:<br> <br> QUOTE<br> The included DTB is meant for the RPi downstream 6.1.y kernel.<br> END QUOTE<br> <br> And, so, FreeBSD is likely not a useful match to DeviceTree<br> mode at this time.<br> <br> =3D=3D=3D<br> Mark Millard<br> marklmi at <a href=3D"http://yahoo.com" rel=3D"noreferrer" target=3D"_blank= ">yahoo.com</a><br> <br> </blockquote></div><br clear=3D"all"><br><span class=3D"gmail_signature_pre= fix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature">Mario.<br></d= iv> --000000000000c1ce3406190e278c--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B1FSijd2abM9a5B98CAMRApUJt7UhTgrQrj%2BZvVHwJv2rT7tQ>