Re: [libvirt] [PATCH 0/5] qemu: Use FW descriptors to report FW image paths

2019-09-13 Thread Michal Privoznik
On 9/13/19 12:25 PM, Kashyap Chamarthy wrote: On Mon, Aug 05, 2019 at 06:14:20PM +0200, Michal Privoznik wrote: [...] Michal Prívozník (5): virfirmware: Expose and define autoptr for virFirmwareFree qemu_firmware: Document qemuFirmwareGetSupported qemu_firmware: Extend

Re: [libvirt] [PATCH 0/5] qemu: Use FW descriptors to report FW image paths

2019-09-13 Thread Kashyap Chamarthy
On Mon, Aug 05, 2019 at 06:14:20PM +0200, Michal Privoznik wrote: [...] > Michal Prívozník (5): > virfirmware: Expose and define autoptr for virFirmwareFree > qemu_firmware: Document qemuFirmwareGetSupported > qemu_firmware: Extend qemuFirmwareGetSupported to return FW paths >

Re: [libvirt] [PATCH 0/5] qemu: Use FW descriptors to report FW image paths

2019-09-11 Thread Cole Robinson
On 8/5/19 12:14 PM, Michal Privoznik wrote: > It feels a bit odd to report a built in list of FW images when we have > FW descriptor files. Especially, when some weird architectures are > concerned. For instance, OVMF_CODE.fd is reported even for > non-x86_64/non-i386 arches, like ppc. But if FW

Re: [libvirt] [PATCH 0/5] qemu: Use FW descriptors to report FW image paths

2019-09-10 Thread Michal Privoznik
On 8/5/19 6:14 PM, Michal Privoznik wrote: > Ping. Michal -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list

[libvirt] [PATCH 0/5] qemu: Use FW descriptors to report FW image paths

2019-08-05 Thread Michal Privoznik
It feels a bit odd to report a built in list of FW images when we have FW descriptor files. Especially, when some weird architectures are concerned. For instance, OVMF_CODE.fd is reported even for non-x86_64/non-i386 arches, like ppc. But if FW descriptor files are taken into the picture then no