Hello Mark,

On Mon, Nov 25, 2024 at 12:01:33AM +0100, Mark Kettenis wrote:
> > Date: Sun, 24 Nov 2024 01:08:14 +0300
> > From: Paul Fertser <fercerpav@gmail.com>
> > 
> > Hello,
> > 
> > On Sat, Nov 23, 2024 at 10:24:48PM +0100, Mark Kettenis wrote:
> > > > Here follows the updated diff which handles the non-deprecated node
> > > > name.
> > > 
> > > Thanks.  I committed this version of the diff.
> > 
> > Thank you for the review and taking care of it indeed!
> > 
> > Should I be somehow bumping my other arm64 patches (including the one
> > to documentation) if they do not get any specific feedback after a
> > predefined number of days or do you and other maintainers keep track
> > of pending code without extra noise and I should just be patient?
> 
> I was very busy the last few weeks, so some patience is required ;).

Sure, I'm just very new to OpenBSD so have no idea how it normally
goes, hence asking. Thanks for the clarifications.

> However, bumping after a week or two is probably a good idea.  I think
> we've committed all your diffs now.  So if we missed one, let us know!

I also have this idea to make the installation doc slightly better for
the newcomers (also probably some more experienced users too as nobody
on IRC could tell me the proper location):

https://marc.info/?l=openbsd-tech&m=173149654910875&w=2

Not sure if it's right to mention interactive prompt there in the
post-inst notes, probably not, but this boot> interaction is only
mentioned before in the Raspberry Pi specific section so easy to miss.

I'd also probably would like to see something like the following diff
there as it wasn't quite obvious to me that in modern U-Boot for arm64
it's customary to set FDT_FILE that way and "vendor" is not a literal
but should be substituted.

---

diff --git distrib/notes/arm64/prep distrib/notes/arm64/prep
index a016236d1627..e2b8be968ad6 100644
--- distrib/notes/arm64/prep
+++ distrib/notes/arm64/prep
@@ -36,8 +36,8 @@ Running EFI payloads with U-Boot:

 If the U-Boot target supports "distro_bootcmd" efiboot will automatically
 be loaded by placing bootaa64.efi into /efi/boot/bootaa64.efi on a FAT
-filesystem.  With dtb files placed in /vendor/, /dtbs/vendor/, or
-/dtb/current/vendor/.
+filesystem.  With dtb files placed in /<vendor>/, /dtbs/<vendor>/, or
+/dtb/current/<vendor>/.
 
 If the U-Boot target supports bootefi but not automatically finding it with
 "distro_bootcmd" then it must be loaded manually or by U-Boot commands or