Re: [Qemu-devel] [PATCH v3 6/6] hw/pci-bridge: set explicit OFW unit address for TYPE_PXB_HOST

2015-06-11 Thread Laszlo Ersek
On 06/11/15 12:29, Marcel Apfelbaum wrote: On 06/11/2015 01:26 PM, Laszlo Ersek wrote: On 06/11/15 12:21, Marcel Apfelbaum wrote: On 06/11/2015 03:38 AM, Laszlo Ersek wrote: The PXB implementation doesn't allow firmware (SeaBIOS or OVMF) to boot off devices behind the PXB. This happens

Re: [Qemu-devel] [PATCH v3 6/6] hw/pci-bridge: set explicit OFW unit address for TYPE_PXB_HOST

2015-06-11 Thread Marcel Apfelbaum
On 06/11/2015 03:38 AM, Laszlo Ersek wrote: The PXB implementation doesn't allow firmware (SeaBIOS or OVMF) to boot off devices behind the PXB. This happens because the sysbus_get_fw_dev_path() function in hw/core/sysbus.c doesn't have enough information to format a unique identifier for the PXB

Re: [Qemu-devel] [PATCH v3 6/6] hw/pci-bridge: set explicit OFW unit address for TYPE_PXB_HOST

2015-06-11 Thread Marcel Apfelbaum
On 06/11/2015 03:38 AM, Laszlo Ersek wrote: The PXB implementation doesn't allow firmware (SeaBIOS or OVMF) to boot off devices behind the PXB. This happens because the sysbus_get_fw_dev_path() function in hw/core/sysbus.c doesn't have enough information to format a unique identifier for the PXB

Re: [Qemu-devel] [PATCH v3 6/6] hw/pci-bridge: set explicit OFW unit address for TYPE_PXB_HOST

2015-06-11 Thread Marcel Apfelbaum
On 06/11/2015 01:26 PM, Laszlo Ersek wrote: On 06/11/15 12:21, Marcel Apfelbaum wrote: On 06/11/2015 03:38 AM, Laszlo Ersek wrote: The PXB implementation doesn't allow firmware (SeaBIOS or OVMF) to boot off devices behind the PXB. This happens because the sysbus_get_fw_dev_path() function in

Re: [Qemu-devel] [PATCH v3 6/6] hw/pci-bridge: set explicit OFW unit address for TYPE_PXB_HOST

2015-06-11 Thread Marcel Apfelbaum
On 06/11/2015 01:45 PM, Laszlo Ersek wrote: On 06/11/15 12:29, Marcel Apfelbaum wrote: On 06/11/2015 01:26 PM, Laszlo Ersek wrote: On 06/11/15 12:21, Marcel Apfelbaum wrote: On 06/11/2015 03:38 AM, Laszlo Ersek wrote: The PXB implementation doesn't allow firmware (SeaBIOS or OVMF) to boot

Re: [Qemu-devel] [PATCH v3 6/6] hw/pci-bridge: set explicit OFW unit address for TYPE_PXB_HOST

2015-06-11 Thread Laszlo Ersek
On 06/11/15 11:15, Marcel Apfelbaum wrote: On 06/11/2015 03:38 AM, Laszlo Ersek wrote: The PXB implementation doesn't allow firmware (SeaBIOS or OVMF) to boot off devices behind the PXB. This happens because the sysbus_get_fw_dev_path() function in hw/core/sysbus.c doesn't have enough

Re: [Qemu-devel] [PATCH v3 6/6] hw/pci-bridge: set explicit OFW unit address for TYPE_PXB_HOST

2015-06-11 Thread Laszlo Ersek
On 06/11/15 12:21, Marcel Apfelbaum wrote: On 06/11/2015 03:38 AM, Laszlo Ersek wrote: The PXB implementation doesn't allow firmware (SeaBIOS or OVMF) to boot off devices behind the PXB. This happens because the sysbus_get_fw_dev_path() function in hw/core/sysbus.c doesn't have enough

[Qemu-devel] [PATCH v3 6/6] hw/pci-bridge: set explicit OFW unit address for TYPE_PXB_HOST

2015-06-10 Thread Laszlo Ersek
The PXB implementation doesn't allow firmware (SeaBIOS or OVMF) to boot off devices behind the PXB. This happens because the sysbus_get_fw_dev_path() function in hw/core/sysbus.c doesn't have enough information to format a unique identifier for the PXB in question, and consequently the