Re: [9front] Reform MNT Boot Process

["Sigrid Solveig Haflínudóttir" <sigrid@ftrv.se>]

Quoth alex-ml@posteo.de:
> My guess would be that flash.bin (built via the mkfile) is loading the 
> kernel with the information from boot.scr (also built via mkfile). Is 
> that right? In this case, the boot process would be a bit easier than 
> described above (at least with fewer steps).

Yes.  flash.bin is U-Boot built for Reform.  It is in turn the one
loading the kernel by following the instructions in boot.txt (which
gets "compiled" into boot.scr).

> In /sys/src/cmd/aux/txt2uimage.c/, which is used in the recipe for 
> boot.scr, there are some numbers that I would like to understand where 
> they come from. Is there some documentation explaining how an uimage and 
> / or header has to look like? Unfortunately I wasn't able to find this 
> information on https://docs.u-boot.org/.
> 
> And the same question for /sys/src/boot/reform/boot.txt/, where some 
> addresses are given. How do I obtain this information?

"uImage" is a wrapper for whichever files you intend to use with
U-Boot.  In this specific case it tells U-Boot it's a "script" file
with a specific load address (where to put the "raw" unwrapped data)
and an entry point (where to start execution from).  I am not sure
where to find any documentation for this besides looking at U-Boot
sources (include/image.h describes a lot of it).

>
> I am very sorry for my beginner questions and I would really appreciate 
> any explanations/hints to help me understand what happens during the 
> boot process.

Don't think it's beginner questions but even if those were, no harm in
asking.