Displaying 3 results from an estimated 3 matches for "v2v_utils_aavmf_firmwar".
Did you mean:
v2v_utils_aavmf_firmware
2016 Feb 04
0
[PATCH] aarch64: Use a common table of AAVMF paths.
...uot;,
+ "/usr/share/edk2.git/aarch64/vars-template-pflash.raw",
+
+ NULL
+};
diff --git a/v2v/utils-c.c b/v2v/utils-c.c
index 66291b2..4ec4063 100644
--- a/v2v/utils-c.c
+++ b/v2v/utils-c.c
@@ -57,3 +57,30 @@ v2v_utils_drive_index (value strv)
CAMLreturn (Val_int (r));
}
+
+value
+v2v_utils_aavmf_firmware (value unitv)
+{
+ CAMLparam1 (unitv);
+ CAMLlocal5 (rv, v, v1, v2, cons);
+ /* Initialize the list backwards. */
+ size_t i = guestfs_int_count_strings ((char **) guestfs_int_aavmf_firmware);
+
+ rv = Val_int (0);
+
+ while (i > 0) {
+ v1 = caml_copy_string (guestfs_int_aavmf_firmware...
2016 May 22
3
[PATCH 0/2] uefi: Add new locations for UEFI files on Fedora.
https://bugzilla.redhat.com/show_bug.cgi?id=1338083
Now that UEFI is fully open source the UEFI firmware can be included
in Fedora. The location will be slightly different. These patches do
a bit of code rearrangement and add the new paths.
Rich.
2016 Aug 18
3
[PATCH v2 0/2] v2v: Use OVMF secure boot file (RHBZ#1367615).
First version was posted here:
https://www.redhat.com/archives/libguestfs/2016-August/thread.html#00100
This is semantically the same as the first version. However
I've split the patch up into two parts. In the first part,
I factor out the UEFI paths so now they are created by the
generator and written in the library and v2v/ directory directly,
instead of the complex business of having a C