The definitions are from PI spec. Seems the latest PI spec hasn't been updated
to add ACPI 5.0 definition.
Thanks,
Hot
From: Andrew Fish [mailto:af...@apple.com]
Sent: Wednesday, December 04, 2013 0:44
To: edk2-devel@lists.sourceforge.net
Subject: [edk2] Is there a reason that the AcpiSystemDesc
Hi, Oliver:
Does current ArmPlatformPackage's sec code support big.LITTLE tech?
Such as :
An ARM SOC --- with 4 Cores Cortex-A15, 4 Cores Cortex-A7
So, if sec code support big.LITTLE tech, how does it let one core as
boot strap cpu, others go into wfe(or other sleeping state)?
Best wishes,
-
On Dec 3, 2013, at 5:34 PM, Gao, Liming wrote:
> Andrew:
> You mean Build Report file. Build command has -y REPORTFILE and -Y
> REPORTTYPE option to generate build text report file. You can just generate
> PCD report, then parse report file to get PCD value. The command can be:
> build -y Pc
Andrew:
You mean Build Report file. Build command has -y REPORTFILE and -Y REPORTTYPE
option to generate build text report file. You can just generate PCD report,
then parse report file to get PCD value. The command can be: build -y
Pcd_Log.txt -Y PCD
Thanks
Liming
-Original Message-
On 12/04/13 01:57, Yao, Jiewen wrote:
> Hi Laszlo
> Your analysis below is exactly what the code implemented.
> Now I believe you and me have different understanding on PI specification,
> not the UDK implementation. :-)
>
>
> "Normally this would be a violation of the protocol, because the poin
Hi Laszlo
"I'm asking because I'm now reaching the assembly code in
"MdeModulePkg/Universal/Acpi/BootScriptExecutorDxe/X64/S3Asm.S" that would jump
to the (real mode) OSPM waking vector, and it reboots the machine. I think that
maybe the wrong routine is invoked, due to confusion around
PcdDxeI
Hi Laszlo
Your analysis below is exactly what the code implemented.
Now I believe you and me have different understanding on PI specification, not
the UDK implementation. :-)
"Normally this would be a violation of the protocol, because the pointer I'm
passing to BootScript->Write() doesn't poin
On Tue, Dec 3, 2013 at 1:56 PM, Laszlo Ersek wrote:
> it's as if different parts of the code thought differently about
> PcdDxeIplSwitchToLongMode.
>
> Interpretation #1:
> - PcdDxeIplSwitchToLongMode means that we have to *switch* from 32-bit
> PEI to 64-bit DXE. Emphasis on "switch", that is, "P
I'm trying to use select() in a non-blocking connection with O_NONBLOCK
applied before connect(), but, connect() returns -1 and errno == "Device
not configured". If I don't set the O_NONBLOCK flags the connection works
fine, but with blocking behaviour using the default timeout. Someone has
any ide
Hi,
it's as if different parts of the code thought differently about
PcdDxeIplSwitchToLongMode.
Interpretation #1:
- PcdDxeIplSwitchToLongMode means that we have to *switch* from 32-bit
PEI to 64-bit DXE. Emphasis on "switch", that is, "PEI and DXE have
different bitness".
Interpretation #2:
- P
Andrew --
That's how we do it :-)
Tim
-Original Message-
From: Andrew Fish [mailto:af...@apple.com]
Sent: Tuesday, December 03, 2013 11:19 AM
To: edk2-devel@lists.sourceforge.net
Subject: [edk2] Getting PCD values for tools that post process the build.
Is there a recommended solution
Hi!
On 12/03/13 16:03, Yao, Jiewen wrote:
> Hi Laszlo
> "According to the PI spec, Information is a pointer pointing to
> runtime memory or ACPI NVS, and the BootScript record will store the
> pointer (ie. not the data pointed-to)."
> I agree with you on first part - According to the PI spec, In
On Tue, Dec 3, 2013 at 1:30 AM, Ni, Ruiyu wrote:
> For your information, I tried to replace the DUET PciBus driver using
> MdeModulePkg one.
> It works well after a small fix to the DUET PciRootBridgeNoEnumerationDxe
> driver.
Nice. :)
I wonder if there is a chance of moving DUET to use
PcAtCh
Try removing "gBS = SystemTable->BootServices;"
Your SystemTable global variable is not initialized, so that
assignment is invalid. You should remove the SystemTable variable.
Since your .inf must already include UefiBootServicesTableLib, gBS
should already be initialized for you.
-Jordan
On Tu
Is there a recommended solution to get PCD values for consumption in a post
build step?
The only thing I could think of is to post process the build log?
Thanks,
Andrew Fish
--
Rapidly troubleshoot problems before they
Is there a reason that the AcpiSystemDescriptionTable protocol does not have a
value for ACPI 5.0?
>From
>https://svn.code.sf.net/p/edk2/code/trunk/edk2/MdePkg/Include/Protocol/AcpiSystemDescriptionTable.h
#define EFI_ACPI_TABLE_VERSION_NONE (1 << 0)
#define EFI_ACPI_TABLE_VERSION_1_0B (1 << 1)
On Mon, 2013-12-02 at 13:42 -0800, Jordan Justen wrote:
>
> SMM for OVMF would be interesting from a sample code perspective for
> EDK II, but probably not bring any other benefits.
Surely if it's sample code in EDK II we are thinking about, would be far
better off showing how things could be don
On 12/02/13 18:04, Laszlo Ersek wrote:
> The big problem is that nothing ever installs
> EFI_DXE_SMM_READY_TO_LOCK_PROTOCOL. As a consequence, the boot script is
> never saved (not even an empty one), *and* BootScriptExecutorDxe never
> copies itself to reserved memory (in order to survive the sus
Hi Laszlo
"According to the PI spec, Information is a pointer pointing to runtime memory
or ACPI NVS, and the BootScript record will store the pointer (ie. not the data
pointed-to)."
I agree with you on first part - According to the PI spec, Information is a
pointer pointing to runtime memory or
Because you are using SerialDxe (see
'VenHw(D3987D4B-971A-435F-8CAF-4967EB627241)'), ensure you have the
following drivers in your DSC and FDF files:
- MdeModulePkg/Universal/Console/ConPlatformDxe/ConPlatformDxe.inf
- MdeModulePkg/Universal/Console/ConSplitterDxe/ConSplitterDxe.inf
- MdeModulePkg/
Probably a known bug that cannot be fixed for compatibility reasons:
EFI_BOOT_SCRIPT_INFORMATION_OPCODE takes two arguments, "InformationLength" and
"Information". According to the PI spec, Information is a pointer pointing to
runtime memory or ACPI NVS, and the BootScript record will store the po
For your information, I tried to replace the DUET PciBus driver using
MdeModulePkg one.
It works well after a small fix to the DUET PciRootBridgeNoEnumerationDxe
driver.
Thanks,
Ray
-Original Message-
From: Kinney, Michael D [mailto:michael.d.kin...@intel.com]
Sent: Tuesday, December 0
On 12/03/13 04:48, Yao, Jiewen wrote:
> Hi Laszlo
> Thanks! This update seems good.
> And we need more test to see if there is any impact on real platforms,
> because of dependency change.
>
> Reviewed-by: Jiewen Yao
Thanks! :)
Laszlo
---
Hi Ramesh,
PFA the source code.
On Tue, Dec 3, 2013 at 11:39 AM, Ramesh R. wrote:
> Nishit,
>
>
>
> Could you please attach your draft source where the locate protocol
> works and doesn’t work. That might give us some idea where are going wrong.
>
>
>
> Thanks,
>
> Ramesh
>
>
>
> *From:* Ni
On 12/02/13 22:42, Jordan Justen wrote:
> On Mon, Dec 2, 2013 at 9:04 AM, Laszlo Ersek wrote:
>> Please refer to the last patch in the series to appreciate the
>> complexity here. I'd like to ask interested people in the community to
>> read through the commit messages (*) and point out if I'm mis
25 matches
Mail list logo
