On Sat, Apr 28, 2012 at 06:17:24PM -0700, Jordan Justen wrote:
On Sat, Apr 28, 2012 at 00:08, Gleb Natapov g...@redhat.com wrote:
On Fri, Apr 27, 2012 at 02:55:48PM -0700, Jordan Justen wrote:
But, if qemu could be changed,
could it be made to match the PIIX4 datasheet?
We try not to
On Fri, Apr 27, 2012 at 02:55:48PM -0700, Jordan Justen wrote:
On Fri, Apr 27, 2012 at 11:47, Laszlo Ersek ler...@redhat.com wrote:
This was how I interpreted our discussion with Jordan:
L: Shouldn't qemu OVMF agree on GPE0?
J: Why? Anyway, OVMF should be correct, because all ACPI
On Sat, Apr 28, 2012 at 00:08, Gleb Natapov g...@redhat.com wrote:
On Fri, Apr 27, 2012 at 02:55:48PM -0700, Jordan Justen wrote:
But, if qemu could be changed,
could it be made to match the PIIX4 datasheet?
We try not to change QEMU in non backwards compatible way. We can
implement PMBA and
Hi,
I'm trying to improve understanding between OVMF and qemu-kvm.
edk2's OvmfPkg/AcpiTables/Platform.h specifies GPE0_BLK at 0x40C,
while qemu's hw/acpi_piix4.c expects the guest to access it at 0xAFE0.
Which macro should be modified to get them in sync?
(SeaBIOS's src/acpi.c #defines
On Fri, Apr 27, 2012 at 07:31, Laszlo Ersek ler...@redhat.com wrote:
edk2's OvmfPkg/AcpiTables/Platform.h specifies GPE0_BLK at 0x40C,
while qemu's hw/acpi_piix4.c expects the guest to access it at 0xAFE0.
Which macro should be modified to get them in sync?
Do they need to be in sync?
We set
On 04/27/12 17:12, Jordan Justen wrote:
On Fri, Apr 27, 2012 at 07:31, Laszlo Ersek ler...@redhat.com wrote:
edk2's OvmfPkg/AcpiTables/Platform.h specifies GPE0_BLK at 0x40C,
while qemu's hw/acpi_piix4.c expects the guest to access it at 0xAFE0.
Which macro should be modified to get them in
On Fri, Apr 27, 2012 at 07:24:48PM +0200, Laszlo Ersek wrote:
On 04/27/12 17:12, Jordan Justen wrote:
On Fri, Apr 27, 2012 at 07:31, Laszlo Ersek ler...@redhat.com wrote:
edk2's OvmfPkg/AcpiTables/Platform.h specifies GPE0_BLK at 0x40C,
while qemu's hw/acpi_piix4.c expects the guest to
On 04/27/12 20:09, Gleb Natapov wrote:
On Fri, Apr 27, 2012 at 07:24:48PM +0200, Laszlo Ersek wrote:
From 5.2.9 Fixed ACPI Description Table (FADT) in the ACPI spec (v5.0)
it would appear OVMF can freely choose where to put GPE0_BLK, in both
senses (ie. port address considered alone, and also
On Fri, Apr 27, 2012 at 08:47:00PM +0200, Laszlo Ersek wrote:
On 04/27/12 20:09, Gleb Natapov wrote:
On Fri, Apr 27, 2012 at 07:24:48PM +0200, Laszlo Ersek wrote:
From 5.2.9 Fixed ACPI Description Table (FADT) in the ACPI spec (v5.0)
it would appear OVMF can freely choose where to put
On Fri, Apr 27, 2012 at 11:47, Laszlo Ersek ler...@redhat.com wrote:
This was how I interpreted our discussion with Jordan:
L: Shouldn't qemu OVMF agree on GPE0?
J: Why? Anyway, OVMF should be correct, because all ACPI registers are
in one tight bunch, starting from 0x400.
L: None of those
10 matches
Mail list logo
