51e35be7cb
The pc_x86_64_efi reference defconfig is targeted towards an EFI environment but the kernel which comes with it does not enable EFI support by default. Booting this defconfig without kernel EFI support on a qemu virtual machine with EFI firmware resulted in no output to tty1 or ttyS0. Enabling EFI support in the kernel fixed this and seems saner for an EFI reference Buildroot defconfig. Adding CONFIG_EFI to board/pc/linux-extras.config also affects pc_x86_64_bios_defconfig which doesn't require it, however it was observed that the extra overhead is small and so this is preferred rather than having a separate config file. This was tested with qemu 2.6.0 running with kvm enabled and firmware EFI v2.60 by EDK II. Also built and verified bios defconfig on the same setup but with BIOS firmware instead. Signed-off-by: Erico Nunes <nunes.erico@gmail.com> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com> |
||
|---|---|---|
| .. | ||
| genimage-bios.cfg | ||
| genimage-efi.cfg | ||
| linux-extras.config | ||
| post-image.sh | ||
| readme.txt | ||
Bare PC sample config ===================== 1. Build First select the appropriate target you want. For BIOS-based boot strategy: $ make pc_x86_64_bios_defconfig Or for EFI: $ make pc_x86_64_efi_defconfig Add any additional packages required and build: $ make 2. Write the pendrive The build process will create a pendrive image called sdcard.img in output/images. Write the image to a pendrive: $ dd if=output/images/disk.img of=/dev/sdc; sync Once it's done insert it into the target PC and boot. Remember that if said PC has another boot device you might need to select this alternative for it to boot. In the case of EFI boot you might need to disable Secure Boot from the setup as well. 3. Enjoy