On Sat, Apr 28, 2012 at 06:17:24PM -0700, Jordan Justen wrote:
> On Sat, Apr 28, 2012 at 00:08, Gleb Natapov 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 chan
On Sat, Apr 28, 2012 at 00:08, Gleb Natapov 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 start
On Fri, Apr 27, 2012 at 02:55:48PM -0700, Jordan Justen wrote:
> On Fri, Apr 27, 2012 at 11:47, Laszlo Ersek 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
On Fri, Apr 27, 2012 at 11:47, Laszlo Ersek 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 two charact
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 wher
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,
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 wrote:
>
> >> edk2's "OvmfPkg/AcpiTables/Platform.h" specifies GPE0_BLK at 0x40C,
> >> while qemu's "hw/acpi_piix4.c" expects the guest to access
On 04/27/12 17:12, Jordan Justen wrote:
> On Fri, Apr 27, 2012 at 07:31, Laszlo Ersek 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?
>
On Fri, Apr 27, 2012 at 07:31, Laszlo Ersek 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 PBMA to 0x4
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 P
10 matches
Mail list logo