Re: Raspberry Pi 4B DS3231 real-time clock
It's in the UEFI firmware setup menu. -- Sent from a phone, apologies for poor formatting. On 24 August 2020 04:01:19 Archimedes Gaviola wrote: > openbsd67rpi4b# dmesg > OpenBSD 6.7-current (GENERIC.MP) #775: Wed Aug 19 00:17:01 MDT 2020 > dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP > real mem = 1996668928 (1904MB) > avail mem = 1903022080 (1814MB) > random: good seed from bootblocks > mainbus0 at root: ACPI You have to switch to DT (device tree) mode to be able to use the RTC. Cheers, Mark Hi Mark, How to accomplish switching to DT mode because I haven't tried it yet and while looking at Raspberry Pi forums and mailing lists those 2 config.txt parameters are only described. Thanks and best regards, Archimedes
Re: Raspberry Pi 4B DS3231 real-time clock
On Mon, Aug 24, 2020 at 3:56 PM Stuart Henderson wrote: > It's in the UEFI firmware setup menu. > > -- > Sent from a phone, apologies for poor formatting. > Hi Stuart, This is noted, I'll check it out later after work. Thanks and best regards, Archimedes
Discuss UEFI settings in arm64.html/INSTALL.arm64
It's not very obvious that there devices that can attach on RPi4 only if the UEFI firmware to set to FDT mode. Also, the UEFI firmware for RPi4 defaults to capping physical memory to 3 GB since the DMA controller can't access memory above 3 GB and Linux doesn't have a workaronud for that. Going by the DMA constraint set up in efiboot.c and arm64/machdep.c, it looks to me like it's safe to disable this cap with OpenBSD. I think it makes sense to mention that in the Raspberry Pi 4 paragraphs in INSTALL.arm64. Diffs below. I posted the arm64.html diff before but it was at the end of another thread so it may not have been noticed... blob - 03a8b09c4376e045df573927e43b49db78a533dd blob + a4b0d39c0a6faa5186719991e9b07245fa578055 --- distrib/notes/arm64/prep +++ distrib/notes/arm64/prep @@ -73,6 +73,18 @@ Install on Raspberry Pi 4: should see a multi-coloured screen followed by UEFI firmware output. If you do not see this, re-check your UEFI firmware installation. + As of this writing, the UEFI firmware's default settings supply the + booted OS with ACPI tables only. The ACPI tables do not include some + onboard devices such as the bwfm(4) wireless interface. In order to + use these devices under OpenBSD, configure the UEFI firmware to + provide both ACPI tables and a firmware device tree (FDT). + + Additionally, the UEFI firmware limits the OS' physical memory to + 3 GB by default because of DMA controller hardware limitations that + cause problems with other operating systems. OpenBSD has a workaround + for the DMA limitation, so it is safe to disable the 3 GB limit when + running OpenBSD. + OpenBSD should boot automatically soon after loading the UEFI firmware. If a monitor is connected you will see messages from the boot loader, but after the kernel has started running you will only see output on blob - 4aae202b2b0e09c1df1e55f2a8cb8b84847c0825 blob + a583aa46fe231ad14f7ecd5e28043f55a39d805d --- arm64.html +++ arm64.html @@ -60,9 +60,20 @@ U-Boot> boot The Raspberry Pi 4 is only supported when using EDK2-based UEFI firmware. -By default the boot ROM will only try to load the firmware off an SD card. -There is no SD/MMC driver yet, but there are no manual steps needed to -boot from a USB disk drive. +By default the boot ROM will only try to load the firmware off an SD card, +but there are no manual steps needed to boot the operating system from a +USB disk drive. The UEFI firmware's ACPI tables provide enough devices +for the system to be usable with USB storage and wired Ethernet; additional +devices such as the +https://man.openbsd.org/arm64/bcmdog.4";>bcmdog(4) +watchdog timer and +https://man.openbsd.org/arm64/bcmirng.4";>bcmirng(4) +RNG can be attached when the firmware is configured to provide a +device tree in addition to ACPI. The SD controller may need to be +set to eMMC2 mode in the firmware in order for it to attach along +with the onboard +https://man.openbsd.org/arm64/bwfm.4";>bwfm(4) +WiFi. Ampere eMAG and AMD Opteron systems come with a UEFI firmware in ROM @@ -150,7 +161,7 @@ An updated device tree may have to be supplied to make 802.11 wireless https://man.openbsd.org/arm64/bwfm.4";>bwfm(4) - on Raspberry Pi 3 and Pinebook Pro + on Raspberry Pi 3/4 and Pinebook Pro Storage @@ -162,7 +173,7 @@ An updated device tree may have to be supplied to make https://man.openbsd.org/arm64/dwmmc.4";>dwmmc(4) on Rockchip RK3328/RK3399 https://man.openbsd.org/arm64/sdhc.4";>sdhc(4) - on Rockchip RK3399 + on Rockchip RK3399 and Raspberry Pi 4 https://man.openbsd.org/arm64/sximmc.4";>sximmc(4) on Allwinner A64/H5
Re: Raspberry Pi 4B DS3231 real-time clock
On Mon, Aug 24, 2020 at 4:01 PM Archimedes Gaviola < archimedes.gavi...@gmail.com> wrote: > > > On Mon, Aug 24, 2020 at 3:56 PM Stuart Henderson > wrote: > >> It's in the UEFI firmware setup menu. >> >> -- >> Sent from a phone, apologies for poor formatting. >> > > Hi Stuart, > > This is noted, I'll check it out later after work. > > Thanks and best regards, > Archimedes > > Hi Mark, After switching to device tree mode in the UEFI firmware the system encountered kernel panic. Here's the link https://i.postimg.cc/VkWp0KPJ/IMG-6798.jpg for the captured boot message. Thank you Stuart for referring me to the UEFI firmware! Thanks and best regards, Archimedes
Re: Discuss UEFI settings in arm64.html/INSTALL.arm64
> From: Todd Carson > Date: Mon, 24 Aug 2020 20:07:24 +0900 > > It's not very obvious that there devices that can attach on RPi4 only if > the UEFI firmware to set to FDT mode. > > Also, the UEFI firmware for RPi4 defaults to capping physical memory to > 3 GB since the DMA controller can't access memory above 3 GB and Linux > doesn't have a workaronud for that. > > Going by the DMA constraint set up in efiboot.c and arm64/machdep.c, it > looks to me like it's safe to disable this cap with OpenBSD. I think it > makes sense to mention that in the Raspberry Pi 4 paragraphs in > INSTALL.arm64. That's correct. OpenBSD can deal with the 3GB limit. In fact it imposes a 1GB DMA limit because there are additional DMA restrictions for the SD controller. > Diffs below. I posted the arm64.html diff before but it was at the end > of another thread so it may not have been noticed... I'm not necessarily against adding this, but a lot of this information isn't really OpenBSD-specific and adding text about all the different quirks of all the ARM boards we support doesn't really scale. But then neither does answering the same questions over and over again on the mailing lists... Stuart, Jonathan, what do you tink? > > blob - 03a8b09c4376e045df573927e43b49db78a533dd > blob + a4b0d39c0a6faa5186719991e9b07245fa578055 > --- distrib/notes/arm64/prep > +++ distrib/notes/arm64/prep > @@ -73,6 +73,18 @@ Install on Raspberry Pi 4: >should see a multi-coloured screen followed by UEFI firmware output. >If you do not see this, re-check your UEFI firmware installation. > > + As of this writing, the UEFI firmware's default settings supply the > + booted OS with ACPI tables only. The ACPI tables do not include some > + onboard devices such as the bwfm(4) wireless interface. In order to > + use these devices under OpenBSD, configure the UEFI firmware to > + provide both ACPI tables and a firmware device tree (FDT). > + > + Additionally, the UEFI firmware limits the OS' physical memory to > + 3 GB by default because of DMA controller hardware limitations that > + cause problems with other operating systems. OpenBSD has a workaround > + for the DMA limitation, so it is safe to disable the 3 GB limit when > + running OpenBSD. > + >OpenBSD should boot automatically soon after loading the UEFI firmware. >If a monitor is connected you will see messages from the boot loader, >but after the kernel has started running you will only see output on > > blob - 4aae202b2b0e09c1df1e55f2a8cb8b84847c0825 > blob + a583aa46fe231ad14f7ecd5e28043f55a39d805d > --- arm64.html > +++ arm64.html > @@ -60,9 +60,20 @@ U-Boot> boot > > > The Raspberry Pi 4 is only supported when using EDK2-based UEFI firmware. > -By default the boot ROM will only try to load the firmware off an SD card. > -There is no SD/MMC driver yet, but there are no manual steps needed to > -boot from a USB disk drive. > +By default the boot ROM will only try to load the firmware off an SD card, > +but there are no manual steps needed to boot the operating system from a > +USB disk drive. The UEFI firmware's ACPI tables provide enough devices > +for the system to be usable with USB storage and wired Ethernet; additional > +devices such as the > +https://man.openbsd.org/arm64/bcmdog.4";>bcmdog(4) > +watchdog timer and > +https://man.openbsd.org/arm64/bcmirng.4";>bcmirng(4) > +RNG can be attached when the firmware is configured to provide a > +device tree in addition to ACPI. The SD controller may need to be > +set to eMMC2 mode in the firmware in order for it to attach along > +with the onboard > +https://man.openbsd.org/arm64/bwfm.4";>bwfm(4) > +WiFi. > > > Ampere eMAG and AMD Opteron systems come with a UEFI firmware in ROM > @@ -150,7 +161,7 @@ An updated device tree may have to be supplied to make > 802.11 wireless > > https://man.openbsd.org/arm64/bwfm.4";>bwfm(4) > - on Raspberry Pi 3 and Pinebook Pro > + on Raspberry Pi 3/4 and Pinebook Pro > > > Storage > @@ -162,7 +173,7 @@ An updated device tree may have to be supplied to make > https://man.openbsd.org/arm64/dwmmc.4";>dwmmc(4) > on Rockchip RK3328/RK3399 > https://man.openbsd.org/arm64/sdhc.4";>sdhc(4) > - on Rockchip RK3399 > + on Rockchip RK3399 and Raspberry Pi 4 > https://man.openbsd.org/arm64/sximmc.4";>sximmc(4) > on Allwinner A64/H5 > > >
Re: Raspberry Pi 4B DS3231 real-time clock
> From: Archimedes Gaviola > Date: Mon, 24 Aug 2020 19:15:56 +0800 > > On Mon, Aug 24, 2020 at 4:01 PM Archimedes Gaviola > wrote: > > On Mon, Aug 24, 2020 at 3:56 PM Stuart Henderson > wrote: > > It's in the UEFI firmware setup menu. > > -- >Sent from a phone, apologies for poor formatting. > > Hi Stuart, > > This is noted, I'll check it out later after work. > > Thanks and best regards, > Archimedes > > > Hi Mark, > > After switching to device tree mode in the UEFI firmware the system > encountered kernel panic. Here's the link > https://i.postimg.cc/VkWp0KPJ/IMG-6798.jpg for the captured boot message. It is still booting in ACPI mode...
Re: Discuss UEFI settings in arm64.html/INSTALL.arm64
> > > > Diffs below. I posted the arm64.html diff before but it was at the end > > of another thread so it may not have been noticed... > > I'm not necessarily against adding this, but a lot of this information > isn't really OpenBSD-specific and adding text about all the different > quirks of all the ARM boards we support doesn't really scale. But > then neither does answering the same questions over and over again on > the mailing lists.. > I have learned a lot about odd platforms and how pre-boot environments work on them by reading INSTALL. docs, so I would not mind if it carries a bit of extras on how to set it up, hopefully saving someone a trip to the mail list archives. -- May the most significant bit of your life be positive.
Re: Raspberry Pi 4B DS3231 real-time clock
On Mon, Aug 24, 2020 at 7:31 PM Mark Kettenis wrote: > > From: Archimedes Gaviola > > Date: Mon, 24 Aug 2020 19:15:56 +0800 > > > > On Mon, Aug 24, 2020 at 4:01 PM Archimedes Gaviola > > wrote: > > > > On Mon, Aug 24, 2020 at 3:56 PM Stuart Henderson > > wrote: > > > > It's in the UEFI firmware setup menu. > > > > -- > >Sent from a phone, apologies for poor formatting. > > > > Hi Stuart, > > > > This is noted, I'll check it out later after work. > > > > Thanks and best regards, > > Archimedes > > > > > > Hi Mark, > > > > After switching to device tree mode in the UEFI firmware the system > > encountered kernel panic. Here's the link > > https://i.postimg.cc/VkWp0KPJ/IMG-6798.jpg for the captured boot > message. > > It is still booting in ACPI mode... > Hi Mark, Not sure if this is an issue in the latest UEFI firmware v1.19? As I already chose and saved Device Tree mode configuration in the selection table. Here's my current UEFI configuration in my system https://i.postimg.cc/xChvtNbw/IMG-6801.jpg. Thanks and best regards, Archimedes
Re: Discuss UEFI settings in arm64.html/INSTALL.arm64
On Mon, Aug 24, 2020 at 01:29:44PM +0200, Mark Kettenis wrote: > > From: Todd Carson > > Date: Mon, 24 Aug 2020 20:07:24 +0900 > > > > It's not very obvious that there devices that can attach on RPi4 only if > > the UEFI firmware to set to FDT mode. > > > > Also, the UEFI firmware for RPi4 defaults to capping physical memory to > > 3 GB since the DMA controller can't access memory above 3 GB and Linux > > doesn't have a workaronud for that. > > > > Going by the DMA constraint set up in efiboot.c and arm64/machdep.c, it > > looks to me like it's safe to disable this cap with OpenBSD. I think it > > makes sense to mention that in the Raspberry Pi 4 paragraphs in > > INSTALL.arm64. > > That's correct. OpenBSD can deal with the 3GB limit. In fact it > imposes a 1GB DMA limit because there are additional DMA restrictions > for the SD controller. > > > Diffs below. I posted the arm64.html diff before but it was at the end > > of another thread so it may not have been noticed... > > I'm not necessarily against adding this, but a lot of this information > isn't really OpenBSD-specific and adding text about all the different > quirks of all the ARM boards we support doesn't really scale. But > then neither does answering the same questions over and over again on > the mailing lists... > > Stuart, Jonathan, what do you tink? I don't have a rpi4, what was the reason for not being able to use U-Boot again? There are some xhci/vl805 changes in git not yet in a non-rc release. > > > > > blob - 03a8b09c4376e045df573927e43b49db78a533dd > > blob + a4b0d39c0a6faa5186719991e9b07245fa578055 > > --- distrib/notes/arm64/prep > > +++ distrib/notes/arm64/prep > > @@ -73,6 +73,18 @@ Install on Raspberry Pi 4: > >should see a multi-coloured screen followed by UEFI firmware output. > >If you do not see this, re-check your UEFI firmware installation. > > > > + As of this writing, the UEFI firmware's default settings supply the > > + booted OS with ACPI tables only. The ACPI tables do not include some > > + onboard devices such as the bwfm(4) wireless interface. In order to > > + use these devices under OpenBSD, configure the UEFI firmware to > > + provide both ACPI tables and a firmware device tree (FDT). > > + > > + Additionally, the UEFI firmware limits the OS' physical memory to > > + 3 GB by default because of DMA controller hardware limitations that > > + cause problems with other operating systems. OpenBSD has a workaround > > + for the DMA limitation, so it is safe to disable the 3 GB limit when > > + running OpenBSD. > > + > >OpenBSD should boot automatically soon after loading the UEFI firmware. > >If a monitor is connected you will see messages from the boot loader, > >but after the kernel has started running you will only see output on > > > > blob - 4aae202b2b0e09c1df1e55f2a8cb8b84847c0825 > > blob + a583aa46fe231ad14f7ecd5e28043f55a39d805d > > --- arm64.html > > +++ arm64.html > > @@ -60,9 +60,20 @@ U-Boot> boot > > > > > > The Raspberry Pi 4 is only supported when using EDK2-based UEFI firmware. > > -By default the boot ROM will only try to load the firmware off an SD card. > > -There is no SD/MMC driver yet, but there are no manual steps needed to > > -boot from a USB disk drive. > > +By default the boot ROM will only try to load the firmware off an SD card, > > +but there are no manual steps needed to boot the operating system from a > > +USB disk drive. The UEFI firmware's ACPI tables provide enough devices > > +for the system to be usable with USB storage and wired Ethernet; additional > > +devices such as the > > +https://man.openbsd.org/arm64/bcmdog.4";>bcmdog(4) > > +watchdog timer and > > +https://man.openbsd.org/arm64/bcmirng.4";>bcmirng(4) > > +RNG can be attached when the firmware is configured to provide a > > +device tree in addition to ACPI. The SD controller may need to be > > +set to eMMC2 mode in the firmware in order for it to attach along > > +with the onboard > > +https://man.openbsd.org/arm64/bwfm.4";>bwfm(4) > > +WiFi. > > > > > > Ampere eMAG and AMD Opteron systems come with a UEFI firmware in ROM > > @@ -150,7 +161,7 @@ An updated device tree may have to be supplied to make > > 802.11 wireless > > > > https://man.openbsd.org/arm64/bwfm.4";>bwfm(4) > > - on Raspberry Pi 3 and Pinebook Pro > > + on Raspberry Pi 3/4 and Pinebook Pro > > > > > > Storage > > @@ -162,7 +173,7 @@ An updated device tree may have to be supplied to make > > https://man.openbsd.org/arm64/dwmmc.4";>dwmmc(4) > > on Rockchip RK3328/RK3399 > > https://man.openbsd.org/arm64/sdhc.4";>sdhc(4) > > - on Rockchip RK3399 > > + on Rockchip RK3399 and Raspberry Pi 4 > > https://man.openbsd.org/arm64/sximmc.4";>sximmc(4) > > on Allwinner A64/H5 > > > > > > > >
Re: Discuss UEFI settings in arm64.html/INSTALL.arm64
> Date: Mon, 24 Aug 2020 22:17:25 +1000 > From: Jonathan Gray > > On Mon, Aug 24, 2020 at 01:29:44PM +0200, Mark Kettenis wrote: > > > From: Todd Carson > > > Date: Mon, 24 Aug 2020 20:07:24 +0900 > > > > > > It's not very obvious that there devices that can attach on RPi4 only if > > > the UEFI firmware to set to FDT mode. > > > > > > Also, the UEFI firmware for RPi4 defaults to capping physical memory to > > > 3 GB since the DMA controller can't access memory above 3 GB and Linux > > > doesn't have a workaronud for that. > > > > > > Going by the DMA constraint set up in efiboot.c and arm64/machdep.c, it > > > looks to me like it's safe to disable this cap with OpenBSD. I think it > > > makes sense to mention that in the Raspberry Pi 4 paragraphs in > > > INSTALL.arm64. > > > > That's correct. OpenBSD can deal with the 3GB limit. In fact it > > imposes a 1GB DMA limit because there are additional DMA restrictions > > for the SD controller. > > > > > Diffs below. I posted the arm64.html diff before but it was at the end > > > of another thread so it may not have been noticed... > > > > I'm not necessarily against adding this, but a lot of this information > > isn't really OpenBSD-specific and adding text about all the different > > quirks of all the ARM boards we support doesn't really scale. But > > then neither does answering the same questions over and over again on > > the mailing lists... > > > > Stuart, Jonathan, what do you tink? > > I don't have a rpi4, what was the reason for not being able to use > U-Boot again? There are some xhci/vl805 changes in git not yet in a > non-rc release. Right. Some rpi4 models need those. For other models the current release might be good enough, but it wasn't the case when I first started working on rpi4 support. The EDK2-based firmware is a bit more user-friendly as it provides a tradional BIOS-like configuration screen and was interesting to me since it provides an ACPI option. > > > blob - 03a8b09c4376e045df573927e43b49db78a533dd > > > blob + a4b0d39c0a6faa5186719991e9b07245fa578055 > > > --- distrib/notes/arm64/prep > > > +++ distrib/notes/arm64/prep > > > @@ -73,6 +73,18 @@ Install on Raspberry Pi 4: > > >should see a multi-coloured screen followed by UEFI firmware output. > > >If you do not see this, re-check your UEFI firmware installation. > > > > > > + As of this writing, the UEFI firmware's default settings supply the > > > + booted OS with ACPI tables only. The ACPI tables do not include some > > > + onboard devices such as the bwfm(4) wireless interface. In order to > > > + use these devices under OpenBSD, configure the UEFI firmware to > > > + provide both ACPI tables and a firmware device tree (FDT). > > > + > > > + Additionally, the UEFI firmware limits the OS' physical memory to > > > + 3 GB by default because of DMA controller hardware limitations that > > > + cause problems with other operating systems. OpenBSD has a workaround > > > + for the DMA limitation, so it is safe to disable the 3 GB limit when > > > + running OpenBSD. > > > + > > >OpenBSD should boot automatically soon after loading the UEFI firmware. > > >If a monitor is connected you will see messages from the boot loader, > > >but after the kernel has started running you will only see output on > > > > > > blob - 4aae202b2b0e09c1df1e55f2a8cb8b84847c0825 > > > blob + a583aa46fe231ad14f7ecd5e28043f55a39d805d > > > --- arm64.html > > > +++ arm64.html > > > @@ -60,9 +60,20 @@ U-Boot> boot > > > > > > > > > The Raspberry Pi 4 is only supported when using EDK2-based UEFI firmware. > > > -By default the boot ROM will only try to load the firmware off an SD > > > card. > > > -There is no SD/MMC driver yet, but there are no manual steps needed to > > > -boot from a USB disk drive. > > > +By default the boot ROM will only try to load the firmware off an SD > > > card, > > > +but there are no manual steps needed to boot the operating system from a > > > +USB disk drive. The UEFI firmware's ACPI tables provide enough devices > > > +for the system to be usable with USB storage and wired Ethernet; > > > additional > > > +devices such as the > > > +https://man.openbsd.org/arm64/bcmdog.4";>bcmdog(4) > > > +watchdog timer and > > > +https://man.openbsd.org/arm64/bcmirng.4";>bcmirng(4) > > > +RNG can be attached when the firmware is configured to provide a > > > +device tree in addition to ACPI. The SD controller may need to be > > > +set to eMMC2 mode in the firmware in order for it to attach along > > > +with the onboard > > > +https://man.openbsd.org/arm64/bwfm.4";>bwfm(4) > > > +WiFi. > > > > > > > > > Ampere eMAG and AMD Opteron systems come with a UEFI firmware in ROM > > > @@ -150,7 +161,7 @@ An updated device tree may have to be supplied to make > > > 802.11 wireless > > > > > > https://man.openbsd.org/arm64/bwfm.4";>bwfm(4) > > > - on Raspberry Pi 3 and Pinebook Pro > > > + on Raspberry Pi 3/4 and Pinebook Pro > > > > >
Re: Raspberry Pi 4B DS3231 real-time clock
Hi Mark, Confirmed that UEFI firmware v1.19 has a problem with the current snapshot when Device Tree mode is enabled. I switched to UEFI v1.18 and it works. I remember now that this is what Raspberry Pi 3B dmesg has which shows "dsxrtc0 at iic0 addr 0x68". Please see attached dmesg outputs with pre-NTP and post-NTP sync. After synch'ing with NTP, the system clock retains its obtained date and time even when it is shutdown and disconnected from the internet. Thanks a lot Mark! Best regards, Archimedes On Mon, Aug 24, 2020 at 7:48 PM Archimedes Gaviola < archimedes.gavi...@gmail.com> wrote: > > > On Mon, Aug 24, 2020 at 7:31 PM Mark Kettenis > wrote: > >> > From: Archimedes Gaviola >> > Date: Mon, 24 Aug 2020 19:15:56 +0800 >> > >> > On Mon, Aug 24, 2020 at 4:01 PM Archimedes Gaviola >> > wrote: >> > >> > On Mon, Aug 24, 2020 at 3:56 PM Stuart Henderson >> > wrote: >> > >> > It's in the UEFI firmware setup menu. >> > >> > -- >> >Sent from a phone, apologies for poor formatting. >> > >> > Hi Stuart, >> > >> > This is noted, I'll check it out later after work. >> > >> > Thanks and best regards, >> > Archimedes >> > >> > >> > Hi Mark, >> > >> > After switching to device tree mode in the UEFI firmware the system >> > encountered kernel panic. Here's the link >> > https://i.postimg.cc/VkWp0KPJ/IMG-6798.jpg for the captured boot >> message. >> >> It is still booting in ACPI mode... >> > > Hi Mark, > > Not sure if this is an issue in the latest UEFI firmware v1.19? As I > already chose and saved Device Tree mode configuration in the selection > table. Here's my current UEFI configuration in my system > https://i.postimg.cc/xChvtNbw/IMG-6801.jpg. > > Thanks and best regards, > Archimedes > openbsd-6.7-snapshot_rpi4b_uefi_v1.18_dt-mode_post-ntp-sync Description: Binary data openbsd-6.7-snapshot_rpi4b_uefi_v1.18_dt-mode_pre-ntp-sync Description: Binary data
