Re: OVMF and PCI0 UID

Thanks, I sent the patches on the list now! On Wed, Jul 22, 2020 at 01:53:23PM +, vit9696 via wrote: > Hello, > > We can confirm that the suggested change to zero UIDs resolves the problem. It > will be great if you could handle the rest as you see fit. Thank you! > > Best regards, > Vitaly

Re: OVMF and PCI0 UID

Hello,We can confirm that the suggested change to zero UIDs resolves the problem. It will be great if you could handle the rest as you see fit. Thank you!Best regards,Vitaly В вт, июля 21, 2020 в 12:24, vit9696 пишет: Thank you, we will provide an update whether this sol

Re: OVMF and PCI0 UID

Thank you, we will provide an update whether this solves the problem. Besides, this is not the only case where UIDs are wrong for the PCI bus. In hw/arm/virt-acpi-build.c there is the following code: Aml *dev = aml_device("%s", "PCI0"); aml_append(dev, aml_name_decl("_HID", aml_string("P

Re: OVMF and PCI0 UID

On Mon, Jul 20, 2020 at 11:25:58PM +0200, Laszlo Ersek wrote: > Hi Vitaly, > > adding Igor, Michael, Marcel, and qemu-devel. > > On 07/20/20 11:06, vit9696 wrote: > > Hello, > > > > I discovered an issue with inconsistent QEMU/OVMF device paths, and > > while I am unsure whether directing this e-

Re: OVMF and PCI0 UID

Hi Vitaly, adding Igor, Michael, Marcel, and qemu-devel. On 07/20/20 11:06, vit9696 wrote: > Hello, > > I discovered an issue with inconsistent QEMU/OVMF device paths, and > while I am unsure whether directing this e-mail is appropriate to you, > I believe that you likely have the contacts you co