Skip to content
Snippets Groups Projects
  1. Jul 25, 2012
  2. Jul 24, 2012
  3. Jul 23, 2012
  4. Jul 22, 2012
  5. Jul 20, 2012
  6. Jul 19, 2012
  7. Jul 18, 2012
  8. Jul 17, 2012
  9. Jun 25, 2012
  10. Jun 24, 2012
  11. May 30, 2012
  12. May 19, 2012
  13. May 03, 2012
  14. Apr 27, 2012
  15. Apr 25, 2012
  16. Apr 19, 2012
  17. Apr 17, 2012
  18. Apr 15, 2012
  19. Apr 11, 2012
    • Gerardo Pozzi's avatar
    • Gerardo Pozzi's avatar
      [configs/releng] Add UEFI boot support via Linux >= 3.3 EFI boot stub on x86_64 · 6caa5bcb
      Gerardo Pozzi authored
      
      Makes an efiboot.img (FAT16) for "El Torito" (additional).
      Under an EFI-system, implies that this .ISO works only if is used
      as "CD-ROM/DVD-ROM" not in ISO-HYBRID-MBR mode.
      If you want, an EFI-ready USB-key, just unpack this "<ISO>/EFI/efiboot.img" (FAT16) to
      "<USB-key-FAT-formatted>/EFI" then copy "<ISO>/arch" and setup the filesystem label.
      
      An aditional EFI shell is provided with an startup script for automatic booting
      until EFI_STUB supports "linux.conf" to pass boot parms to kernel.
      Anyway I think that is a good idea to keep this shell, so can customize boot parms,
      or for doing other tasks on systems without an EFI-shell.
      
      RFCv1: Initial efiboot.img build with vmlinuz.efi (Linux with EFI_STUB enabled)
             and archiso.img (initramfs).
      RFCv2: Use an startup.nsh with EFI-Shell 2.0 (generated from build.sh) for automatic boot.
      RFCv3: Use and older EFI-Shell 1.0 instead of 2.0, since not all UEFI-systems
             are compatible with 2.3+ specs.
      RFCv4: The script "startup.nsh" improved by Keshav P R, using a for-loop
             (see notes below from original commit), now that has more than 1-line,
             I moved it to an independent file and is parsed by build.sh.
      
      ----
      About startup.nsh:
      Author: Keshav P R <the.ridikulus.rat@gmail.com>
      Date:   Thu Apr 5 10:33:20 2012 +0530
          [configs/releng] Search in all existing UEFI FS mountpoints for archiso efistub kernel file
      
          There is no guarantee that the efistub kernel will always be in fs0:
          (similar to the case inside linux OS where the sda, sdb confusion exists,
          hence the need for UUIDs), especially when USB (instead os CD/ISO) is
          used for booting.
      
          Hence loop through all possible fs mountpoints (in UEFI) in startup.nsh
          and try to launch the first mountpoint that contains the archiso files.
      
          Cd's into the fs%m:\EFI\archiso directory also may remove future issues
          with efistub's linux.conf where the efistub might have problems
          identifying the directory from which the kernel was launched.
      
          Also add an helpful echo message showing the user the UEFI PATH to the
          archiso kernel file being launched by startup.nsh .
      
          Hopefully this should work in both CD and USB. Tested in Tianocore
          UDK/EDK2 DuetPkg X64 UEFI 2.3.1 firmware with EdkShellBinPkg's Shell.
      ----
      
      Signed-off-by: default avatarGerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
      6caa5bcb
  20. Apr 10, 2012
  21. Apr 09, 2012
  22. Apr 05, 2012
  23. Apr 01, 2012
Loading