Re: [edk2] [PATCH 0/4] Move S3Ready() functional code from AcpiS3SaveDxe to S3SaveStateDxe

2016-04-06 Thread Zeng, Star
On 2016/4/1 1:12, Laszlo Ersek wrote: On 03/31/16 17:10, Zeng, Star wrote: On 2016/3/31 19:47, Laszlo Ersek wrote: Therefore, if this subsystem in edk2 is being reworked, my preference would be the following: (1) Please fix the DepEx bug in BootScriptExecutorDxe first, if possible. Instead,

Re: [edk2] [PATCH 0/4] Move S3Ready() functional code from AcpiS3SaveDxe to S3SaveStateDxe

2016-03-31 Thread Zeng, Star
Laszlo, Try to solve your concern below. On 2016/3/31 19:47, Laszlo Ersek wrote: Star, On 03/31/16 05:01, Star Zeng wrote: The S3Ready() functional code in AcpiS3SaveDxe of IntelFrameworkModulePkg is to do ACPI S3 Context save. In fact, that is not really related to Intel framework ACPI S3

Re: [edk2] [PATCH 0/4] Move S3Ready() functional code from AcpiS3SaveDxe to S3SaveStateDxe

2016-03-31 Thread Laszlo Ersek
Star, On 03/31/16 05:01, Star Zeng wrote: > The S3Ready() functional code in AcpiS3SaveDxe of IntelFrameworkModulePkg > is to do ACPI S3 Context save. In fact, that is not really related to > Intel framework ACPI S3 protocol. > > IntelFrameworkModulePkg will be deprecated step by step, so move

[edk2] [PATCH 0/4] Move S3Ready() functional code from AcpiS3SaveDxe to S3SaveStateDxe

2016-03-30 Thread Star Zeng
The S3Ready() functional code in AcpiS3SaveDxe of IntelFrameworkModulePkg is to do ACPI S3 Context save. In fact, that is not really related to Intel framework ACPI S3 protocol. IntelFrameworkModulePkg will be deprecated step by step, so move the functional code to MdeModulePkg and S3SaveStateDxe