1. 23 Jul, 2012 2 commits
  2. 22 Jul, 2012 1 commit
  3. 20 Jul, 2012 1 commit
  4. 19 Jul, 2012 1 commit
  5. 18 Jul, 2012 1 commit
  6. 17 Jul, 2012 6 commits
  7. 25 Jun, 2012 1 commit
  8. 24 Jun, 2012 6 commits
  9. 30 May, 2012 2 commits
  10. 19 May, 2012 1 commit
  11. 03 May, 2012 1 commit
  12. 27 Apr, 2012 1 commit
  13. 25 Apr, 2012 2 commits
  14. 19 Apr, 2012 1 commit
  15. 17 Apr, 2012 1 commit
  16. 15 Apr, 2012 1 commit
  17. 11 Apr, 2012 2 commits
    • Gerardo Exequiel Pozzi's avatar
    • Gerardo Exequiel Pozzi's avatar
      [configs/releng] Add UEFI boot support via Linux >= 3.3 EFI boot stub on x86_64 · 6caa5bcb
      Gerardo Exequiel 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
  18. 10 Apr, 2012 2 commits
  19. 09 Apr, 2012 1 commit
  20. 05 Apr, 2012 1 commit
  21. 01 Apr, 2012 2 commits
  22. 17 Mar, 2012 3 commits