3efb5e31fc
The startup.nsh file is useless to boot EFI payloads. We just need to follow the naming detection specified in the UEFI spec. The EFI payload need to be placed in the boot/efi folder in the EFI partition and follow the architecture naming as described below: 32bit : bootia32.efi x64 : bootx64.efi aarch32 : bootarm.efi aarch64 : bootaa64.efi This naming is already right in the packages involved (systemd, grub2, gummiboot), therefore we just need to drop the generation of the startup.nsh file. The usage of the startup.nsh in genimage is also dropped to avoid errors in the image generation. Signed-off-by: Kory Maincent <kory.maincent@bootlin.com> Tested-by: Erico Nunes <nunes.erico@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> |
||
|---|---|---|
| .. | ||
| fs-overlay-graphical/etc | ||
| genimage.cfg | ||
| grub.cfg | ||
| linux.config | ||
| post-build.sh | ||
| readme.txt | ||
How to get started with the MinnowBoard MAX =========================================== 1. Build Apply the defconfig: $ make minnowboard_max_defconfig Add any additional packages required and build: $ make 2. Write the SD card The build process will create a SD card image in output/images. Write the image to an mSD card, insert into the MinnowBoard MAX and power the board on. $ dd if=output/images/sdcard.img of=/dev/mmcblk0; sync The system starts two consoles: one on the serial port and one on HDMI. 3. Enjoy Additional information about this board can be found at http://www.minnowboard.org/.