distrib/utils/embedded/files/armv7_boot_nonefi.cmd

[Brook Milligan <brook%nmsu.edu@localhost>]

I am trying to understand the arm firmware files that are installed in /boot.  I would like clarification on two points.

First, the contents of the file distrib/utils/embedded/files/armv7_boot_nonefi.cmd includes lots of lines like the following:

	setenv kernel netbsd.ub

The kernel variable is then used for loading the kernel image into u-boot.  However, it seems that release builds install netbsd-GENERIC.ub, not netbsd.ub.

My first questions are, how is this supposed to work?  Does it in fact work, or is this left over from earlier days when other kernels were installed?  Are there any conditions under which netbsd.ub, not netbsd-GENERIC.ub, is installed?

Second, the decision to install either armv7_boot.cmd or armv7_boot_nonefi.cmd is made depending on whether or not ${release}/usr/mdec/bootarm.efi exists (see distrib/utils/embedded/conf/arm7.conf).  What determines whether the bootarm.efi file is installed?  Or is it always installed?

Thanks for your help.

Cheers,
Brook