o:ler...@redhat.com]
> Sent: Thursday, December 10, 2015 7:04 PM
> To: Ni, Ruiyu ; Kinney, Michael D
> ; Paolo Bonzini ; Zeng, Star
> ; Scott Duplichan
> Cc: edk2-devel@lists.01.org
> Subject: Re: [edk2] [Patch] PcAtChipsetPkg/Rtc: Fix a UEFI Win7 boot hang
> issue
>
ted to new machine types.
Thanks
Laszlo
>
>
> -Original Message-
> From: Kinney, Michael D
> Sent: Thursday, December 10, 2015 9:33 AM
> To: Ni, Ruiyu ; Laszlo Ersek ; Kinney,
> Michael D
> Cc: Paolo Bonzini ; Scott Duplichan ;
> edk2-devel@lists.01.org
aszlo
>
>
> -Original Message-
> From: Kinney, Michael D
> Sent: Thursday, December 10, 2015 9:33 AM
> To: Ni, Ruiyu ; Laszlo Ersek ; Kinney,
> Michael D
> Cc: Paolo Bonzini ; Scott Duplichan ;
> edk2-devel@lists.01.org ; Zeng, Star
>
> Subject: RE: [edk
10, 2015 9:36 AM
To: Kinney, Michael D; Laszlo Ersek
Cc: Paolo Bonzini; Scott Duplichan; edk2-devel@lists.01.org; Zeng, Star
Subject: RE: [edk2] [Patch] PcAtChipsetPkg/Rtc: Fix a UEFI Win7 boot hang issue
Yes.
Regards,
Ray
-Original Message-
From: Kinney, Michael D
Sent: Thursday
eng, Star
> Subject: RE: [edk2] [Patch] PcAtChipsetPkg/Rtc: Fix a UEFI Win7 boot hang
> issue
>
> Mike,
> The UEFI Spec doesn't require implementation to call
> InstallConfigurationTable() every time the ACPI table is updated through
> EFI_ACPI_PROTOCOL.InstallAcpiTable()
gt; > > the memory allocation services, of course).
> > >
> > > I think that the PCD is more robust, and in case a platform's ACPI
> > > driver is *not* updated to consider it, then the situation is still no
> > > worse than with Ray's curre
ecember 10, 2015 3:49 AM
To: Ni, Ruiyu ; Laszlo Ersek ; Kinney,
Michael D
Cc: Paolo Bonzini ; Scott Duplichan ;
edk2-devel@lists.01.org ; Zeng, Star
Subject: RE: [edk2] [Patch] PcAtChipsetPkg/Rtc: Fix a UEFI Win7 boot hang issue
Ray,
The UEFI Specification 2.5 p. 136 - CreateEventEx() require
> -Original Message-
> From: Ni, Ruiyu
> Sent: Wednesday, December 9, 2015 10:48 AM
> To: Laszlo Ersek
> Cc: Kinney, Michael D ; Paolo Bonzini
> ; Scott Duplichan ;
> edk2-devel@lists.01.org ; Zeng, Star
>
> Subject: Re: [edk2] [Patch] PcAtChipsetPkg/Rtc: Fix a U
---
>>> From: Paolo Bonzini [mailto:pbonz...@redhat.com]
>>> Sent: Wednesday, December 9, 2015 9:40 AM
>>> To: Laszlo Ersek ; Kinney, Michael D
>>> ; Ni, Ruiyu ; Scott
>>> Duplichan
>>> Cc: 'edk2-devel@lists.01.org' ; Zeng, Star
>>
atch.
Thanks
Laszlo
>
> Mike
>
>
>> -Original Message-
>> From: Paolo Bonzini [mailto:pbonz...@redhat.com]
>> Sent: Wednesday, December 9, 2015 9:40 AM
>> To: Laszlo Ersek ; Kinney, Michael D
>> ; Ni, Ruiyu ; Scott
>> Duplichan
>>
On 09/12/2015 18:55, Kinney, Michael D wrote:
> 1) RTC driver use info from FADT in SetTime() when FADT is available.
> Add event notification to RTC driver to capture FADT info before
> ExitBootServices().
> 2) Use PCD in RTC driver and in ACPI FADT table.
>
> Advantage of (1) is that it is com
devel@lists.01.org' ; Zeng, Star
>
> Subject: Re: [edk2] [Patch] PcAtChipsetPkg/Rtc: Fix a UEFI Win7 boot hang
> issue
>
>
>
> On 09/12/2015 18:37, Laszlo Ersek wrote:
> > - A DXE driver that runs before *both* the ACPI platform DXE driver, and
> > this ru
On 09/12/2015 18:37, Laszlo Ersek wrote:
> - A DXE driver that runs before *both* the ACPI platform DXE driver, and
> this runtime DXE driver -- to be ordered by any means necessary --, *or*
> a PEIM, sets a dynamic PCD that keys off *both* the ACPI platform DXE
> driver and this runtime DXE driv
ntimeDxe so that it match the FADT generated
by QEMU.
Thanks
Laszlo
>
> Paolo
>
>> Mike
>>
>>> -Original Message-
>>> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
>>> Paolo Bonzini
>>> Sent: Wednesday, Decemb
On 09/12/2015 18:11, Kinney, Michael D wrote:
> Paolo,
>
> I agree SetTime() is not called in very many places. But since the
> SetTime() service is added to Runtime Services Table when the RTC
> driver runs, the logic in SetTime() must be implemented to handle
> case where SetTime() is called
nal Message-
> From: Paolo Bonzini [mailto:pbonz...@redhat.com]
> Sent: Wednesday, December 9, 2015 8:42 AM
> To: Kinney, Michael D ; Ni, Ruiyu
> ; Scott Duplichan
> Cc: 'edk2-devel@lists.01.org' ; Zeng, Star
>
> Subject: Re: [edk2] [Patch] PcAtChipsetPkg/Rtc:
i
>> Sent: Wednesday, December 9, 2015 3:50 AM
>> To: Ni, Ruiyu ; Scott Duplichan
>> Cc: 'edk2-devel@lists.01.org' ; Zeng, Star
>>
>> Subject: Re: [edk2] [Patch] PcAtChipsetPkg/Rtc: Fix a UEFI Win7 boot hang
>> issue
>>
>>
>&g
ay, December 9, 2015 3:50 AM
> To: Ni, Ruiyu ; Scott Duplichan
> Cc: 'edk2-devel@lists.01.org' ; Zeng, Star
>
> Subject: Re: [edk2] [Patch] PcAtChipsetPkg/Rtc: Fix a UEFI Win7 boot hang
> issue
>
>
>
> On 09/12/2015 12:16, Ni, Ruiyu wrote:
> > Scott,
Ni, Ruiyu [mailto:ruiyu...@intel.com] wrote:
]Sent: Wednesday, December 09, 2015 05:16 AM
]To: Scott Duplichan
]Cc: 'Paolo Bonzini' ; 'edk2-devel@lists.01.org'
; Zeng, Star ]
]Subject: RE: [edk2] [Patch] PcAtChipsetPkg/Rtc: Fix a UEFI Win7 boot hang issue
]Scott,
]I debugg
On 09/12/2015 12:16, Ni, Ruiyu wrote:
> Scott, I debugged the issue further and had the below findings:
> According to the ACPI spec 6.0 5.2.9 Fixed ACPI Description Table
> (FADT), the FADT.Century can be set to 0 indicating the RTC doesn't
> support to store century value. But the Win7 boot lo
cAtChipsetPkg/Rtc: Fix a UEFI Win7 boot hang issue
Ni, Ruiyu [mailto:ruiyu...@intel.com] wrote:
]Sent: Friday, November 20, 2015 01:37 AM
]To: Scott Duplichan
]Cc: Paolo Bonzini ; edk2-devel@lists.01.org
; Zeng, Star ]
]Subject: Re: [edk2] [Patch] PcAtChipsetPkg/Rtc: Fix a UEFI Win7 boot hang
Ni, Ruiyu [mailto:ruiyu...@intel.com] wrote:
]Sent: Friday, November 20, 2015 01:37 AM
]To: Scott Duplichan
]Cc: Paolo Bonzini ; edk2-devel@lists.01.org
; Zeng, Star ]
]Subject: Re: [edk2] [Patch] PcAtChipsetPkg/Rtc: Fix a UEFI Win7 boot hang issue
]
]Scott,
]The UEFI Windows 7 is fresh
PM
> ]To: Paolo Bonzini ; Zeng, Star ;
> edk2-devel@lists.01.org
> ]Subject: Re: [edk2] [Patch] PcAtChipsetPkg/Rtc: Fix a UEFI Win7 boot hang
> issue
> ]
> ]If we strictly follow the spec, it's only needed to save the century value
> ]in CMOS when FADT.CenturyOffset is not
Ni, Ruiyu [mailto:ruiyu...@intel.com] wrote:
]Sent: Thursday, November 19, 2015 06:37 PM
]To: Paolo Bonzini ; Zeng, Star ;
edk2-devel@lists.01.org
]Subject: Re: [edk2] [Patch] PcAtChipsetPkg/Rtc: Fix a UEFI Win7 boot hang issue
]
]If we strictly follow the spec, it's only needed to sav
rg
Subject: Re: [edk2] [Patch] PcAtChipsetPkg/Rtc: Fix a UEFI Win7 boot hang issue
On 18/11/2015 06:08, Zeng, Star wrote:
>
> @@ -508,6 +509,7 @@ PcRtcSetTime (
> RtcWrite (RTC_ADDRESS_DAY_OF_THE_MONTH, RtcTime.Day);
> RtcWrite (RTC_ADDRESS_MONTH, RtcTime.Month);
> R
On 18/11/2015 06:08, Zeng, Star wrote:
>
> @@ -508,6 +509,7 @@ PcRtcSetTime (
> RtcWrite (RTC_ADDRESS_DAY_OF_THE_MONTH, RtcTime.Day);
> RtcWrite (RTC_ADDRESS_MONTH, RtcTime.Month);
> RtcWrite (RTC_ADDRESS_YEAR, (UINT8) RtcTime.Year);
> + RtcWrite (RTC_ADDRESS_CENTURY, Century);
Sho
On 2015/11/17 16:48, Ruiyu Ni wrote:
The patch updates the Century value in CMOS location 50 (32h)
to avoid UEFI Win7 hang during booting. (Though Win8 is good.)
Per the ACPI spec the Century storage in CMOS is optional,
but the fact is even we set the FADT.CenturyOffset to 0 indicating
the platf
The patch updates the Century value in CMOS location 50 (32h)
to avoid UEFI Win7 hang during booting. (Though Win8 is good.)
Per the ACPI spec the Century storage in CMOS is optional,
but the fact is even we set the FADT.CenturyOffset to 0 indicating
the platform doesn't store century value in CMOS
28 matches
Mail list logo
