1. 24 Jul, 2018 1 commit
  2. 13 Sep, 2017 1 commit
  3. 29 Aug, 2017 1 commit
  4. 07 Aug, 2017 1 commit
  5. 22 Sep, 2016 1 commit
  6. 26 Jul, 2016 1 commit
  7. 30 Jun, 2015 1 commit
  8. 29 Jun, 2015 1 commit
  9. 13 Apr, 2015 2 commits
    • Laszlo Ersek's avatar
      Fix length of allocated buffer for boot option comparison. · 0ea5b3e3
      Laszlo Ersek authored
      The following commit:
        commit 4aac8a11
        Author: Gary Ching-Pang Lin <glin@suse.com>
        Date:   Thu Mar 6 10:57:02 2014 +0800
          [fallback] Fix the data size for boot option comparison
      corrected the data size used for comparison, but also reduced the
      allocation so it doesn't include the trailing UTF16LE '\0\0' at the
      end of the string, with the result that the trailer of the buffer
      containing the string is overwritten, which OVMF detects as memory
      Increase the size of the storage buffer in a few places to correct
      this problem.
      Signed-off-by: 's avatarRichard W.M. Jones <rjones@redhat.com>
      Cc: Laszlo Ersek <lersek@redhat.com>
      Cc: Gary Ching-Pang Lin <glin@suse.com>
    • Richard W.M. Jones's avatar
      fallback: Fix comparison between signed and unsigned in debugging code. · cb7dec11
      Richard W.M. Jones authored
      fallback.c: In function ‘update_boot_order’:
      fallback.c:334:17: error: comparison between signed and unsigned integer expressions [-Werror=sign-compare]
        for (j = 0 ; j < size / sizeof (CHAR16); j++)
      fallback.c: In function ‘add_to_boot_list’:
      fallback.c:402:16: error: comparison between signed and unsigned integer expressions [-Werror=sign-compare]
        for (i = 0; i < s; i++) {
      Signed-off-by: 's avatarRichard W.M. Jones <rjones@redhat.com>
  10. 13 May, 2014 3 commits
  11. 11 Apr, 2014 1 commit
  12. 31 Jan, 2014 2 commits
    • Peter Jones's avatar
      [fallback] Attempt to re-use existing entries when possible. · 9fcd221e
      Peter Jones authored
      Some firmwares seem to ignore our boot entries and put their fallback
      entries back on top.  Right now that results in a lot of boot entries
      for our stuff, a la https://bugzilla.redhat.com/show_bug.cgi?id=995834 .
      Instead of that happening, if we simply find existing entries that match
      the entry we would create and move them to the top of the boot order,
      the machine will continue to operate in failure mode (which we can't
      avoid), but at least we won't create thousands of extra entries.
      Signed-off-by: 's avatarPeter Jones <pjones@redhat.com>
    • Peter Jones's avatar
      [fallback] For HD() device paths, use just the media node and later. · 6edc6ec0
      Peter Jones authored
      UEFI 2.x section 3.1.2 provides for "short-form device path", where the
      first element specified is a "hard drive media device path", so that you
      can move a disk around on different buses without invalidating your
      device path.  Fallback has not been using this option, though in most
      cases efibootmgr has.
      Note that we still keep the full device path, because LoadImage()
      isn't necessarily the layer where HD() works - one some systems BDS is
      responsible for resolving the full path and passes that to LoadImage()
      instead.  So we have to do LoadImage() with the full path.
  13. 21 Nov, 2013 1 commit
  14. 12 Nov, 2013 1 commit
  15. 15 May, 2013 1 commit
  16. 14 May, 2013 1 commit
  17. 02 May, 2013 1 commit
  18. 30 Apr, 2013 7 commits