... folder with three files in it, bcm2837....dtb, ns2-svk.dtb, vulcan-eval.dtb. I assume the vulkan file has the mesa/graphic stuff in it. In u-boot, efi, grub2, there does not seem to be any other device tree stuff. If running as desktop and not hardware GPIO coding then it works fine if a bit slow ...

Joking aside, there is the text string "EFI PART" in the 2837 bootrom. Wassat about?

This is for Windows 10 core on Pi. It uses EFI boot. Yes you are right, the typical boot process for Windows 10 IoT Core looks ... powers on and runs the SoC firmware bootloader. The bootloader launches the UEFI environment and UEFI applications. The UEFI environment launches the Boot Manager, ...

Is it possible to force the boot loader to break into the EFI boot menu on power up? https://en.wikipedia.org/wiki/EFI_system_partition ... options but basics the same), completely different to a x86 PC with UEFI BIOS: http://wiki.beyondlogic.org/index.php?title=Understanding_RaspberryPi_Boot_Process

... device Scanning mmc 0:1... 7192 bytes read in 80 ms (86.9 KiB/s) Found EFI removable media binary efi/boot/bootaa64.efi reading efi/boot/bootaa64.efi ... boot menu on this console EFI stub: Booting Linux Kernel... EFI stub: UEFI Secure Boot is enabled. EFI stub: Using DTB from configuration table ...

... [ 0.000000] Memory limited to 96MB [guest0/uart0] [ 0.000000] efi: Getting EFI parameters from FDT: [guest0/uart0] [ 0.000000] efi: UEFI not found. [guest0/uart0] [ 0.000000] cma: Reserved 16 MiB at 0x0000000045000000 [guest0/uart0] ...

Yes , even Windows 10 "IoT Core" has to use the firmware. Firmware is not software-specific but hardware-specific. All OS on desktop PCs will use the BIOS/EFI/UEFI.

All OS on the Raspberry must use start.elf and bootcode.bin etc.

ghans

Except that the final detail must differ between Raspbian and IoT. One of the files in the \EFIESP\EFI\ tree replaces what would be the Linux core image. I am just not sure which one it is (or all ?). bootarm.efi bootmgfw.efi mobilestartup.efi NT Kernel 10 (was originially ...

Except that the final detail must differ between Raspbian and IoT. One of the files in the \EFIESP\EFI\ tree replaces what would be the Linux core image. I am just not sure which one it is (or all ?). bootarm.efi bootmgfw.efi mobilestartup.efi NT Kernel 10 (was originially ...

Except that the final detail must differ between Raspbian and IoT. One of the files in the \EFIESP\EFI\ tree replaces what would be the Linux core image. I am just not sure which one it is (or all ?). bootarm.efi bootmgfw.efi mobilestartup.efi NT Kernel 10 (was originially ...

... this one work only with efi enabled custom bootloader (not released by dark forces team) http://forum.xda-developers.com/showpost.php?p=43072252&postcount=4 ... work for Windows IoT (I suppose that Raspberry firmware doesn't support UEFI natively unlike linaro's kernels for beagleboards) for booting ...

... this one work only with efi enabled custom bootloader (not released by dark forces team) http://forum.xda-developers.com/showpost.php?p=43072252&postcount=4 ... work for Windows IoT (I suppose that Raspberry firmware doesn't support UEFI natively unlike linaro's kernels for beagleboards) for booting ...

... and as time goes on it will be phased out completely in favor of UEFI and its GPT. if the raspberry pi supported EFI out of the box like a mac, then we would ...

... too. 2.) add support for GPT partition tables and expect to find a boot.efi file if a GPT is used as well as the usual text files and kernel.img ... and as time goes on it will be phased out completely in favor of UEFI and its GPT. if the raspberry pi supported EFI out of the box like a ...