On 06/10/15 13:55, Marcel Apfelbaum wrote:
> On 06/10/2015 02:04 PM, Laszlo Ersek wrote:
>> On 06/10/15 11:09, Marcel Apfelbaum wrote:
>>> On 06/06/2015 02:45 AM, Laszlo Ersek wrote:
>>
(7) At least one issue remains to be solved (designed) in QEMU, for
both
SeaBIOS's and OVMF'
On 06/10/2015 02:04 PM, Laszlo Ersek wrote:
On 06/10/15 11:09, Marcel Apfelbaum wrote:
On 06/06/2015 02:45 AM, Laszlo Ersek wrote:
(7) At least one issue remains to be solved (designed) in QEMU, for both
SeaBIOS's and OVMF's sake: booting off devices that are located on
the PXB. T
On 06/10/15 11:09, Marcel Apfelbaum wrote:
> On 06/06/2015 02:45 AM, Laszlo Ersek wrote:
>> (7) At least one issue remains to be solved (designed) in QEMU, for both
>> SeaBIOS's and OVMF's sake: booting off devices that are located on
>> the PXB. The problem is with the "bootorder" fw_cf
On 06/06/2015 02:45 AM, Laszlo Ersek wrote:
Following up on this cross-posted message, I will send two patch sets,
one for QEMU (to qemu-devel) and another for OVMF (to edk2-devel). With
both in place, OVMF supports multiple PCI root buses.
Hi Laszlo,
Thank you for the patches.
Below I'm writ
Following up on this cross-posted message, I will send two patch sets,
one for QEMU (to qemu-devel) and another for OVMF (to edk2-devel). With
both in place, OVMF supports multiple PCI root buses.
Below I'm writing up the way I tested the feature, plus a few random
notes.
(1) Interrupt line assig
