[edk2] Can OVMF run on an emulated QEMU ARM vexpress-a9?

2017-06-11 Thread Andre 
Hi,

this might be a silly question, as I am learning as I go about the topic,
but is it possible to emulate UEFI on QEMU when setting the emulated
machine to an ARM vexpress-a9?

I was able to emulate it on QEMU's virt machine, but I don't care as much
about the vexpress-a9, but as to know whether OVMF can only run against
QEMU's virt machine or if it can run against some other emulated board.

Are there too many differences between the virt machine to other boards
that make providing images for different emulated boards impractical?

I really don't know enough even to know if my question is sensible, so any
pointers on the topic are really appreciated!

Thank you,
Andre
___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

Re: [edk2] PXE boot option lacks IPv4 device path

2017-06-11 Thread Santhapur Naveen 
This behavior is seen only in Simulator

From: Santhapur Naveen
Sent: Monday, June 12, 2017 9:27 AM
To: edk2-devel@lists.01.org
Subject: PXE boot option lacks IPv4 device path

Hello all,

I've built and run the Nt32Pkg source from 
here. I've enabled PXE boot support and I 
could see only MAC device path (005056C2, 0x1) present for all PXEv4 boot 
options something like UEFI PXEv4 MAC(005056C000XX).
But for HTTPv4, the device path is "MAC (005056C2, 
0x01)/IPv4(0.0.0.0, 0x0, DHCP, 0.0.0.0, 0.0.0.0, 0.0.0.0)/Uri()"

 Why the PXE boot option doesn't have the IPv4 device path?

Your comments are highly appreciated.

Regards,
Naveen

___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

[edk2] PXE boot option lacks IPv4 device path

2017-06-11 Thread Santhapur Naveen 
Hello all,

I've built and run the Nt32Pkg source from 
here. I've enabled PXE boot support and I 
could see only MAC device path (005056C2, 0x1) present for all PXEv4 boot 
options something like UEFI PXEv4 MAC(005056C000XX).
But for HTTPv4, the device path is "MAC (005056C2, 
0x01)/IPv4(0.0.0.0, 0x0, DHCP, 0.0.0.0, 0.0.0.0, 0.0.0.0)/Uri()"

 Why the PXE boot option doesn't have the IPv4 device path?

Your comments are highly appreciated.

Regards,
Naveen

___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

[edk2] [PATCH v2] EmbeddedPkg/MmcDxe: Add non-DDR timing mode support

2017-06-11 Thread Jun Nie 
Only DDR mode is support for 8bit mode currently. Add
non-DDR case when configuring ECSD.

Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jun Nie 
---
 EmbeddedPkg/Universal/MmcDxe/MmcIdentification.c | 16 ++--
 1 file changed, 14 insertions(+), 2 deletions(-)

diff --git a/EmbeddedPkg/Universal/MmcDxe/MmcIdentification.c 
b/EmbeddedPkg/Universal/MmcDxe/MmcIdentification.c
index 574a77e..4ce0ddd 100644
--- a/EmbeddedPkg/Universal/MmcDxe/MmcIdentification.c
+++ b/EmbeddedPkg/Universal/MmcDxe/MmcIdentification.c
@@ -254,7 +254,7 @@ InitializeEmmcDevice (
   EFI_MMC_HOST_PROTOCOL *Host;
   EFI_STATUS Status = EFI_SUCCESS;
   ECSD   *ECSDData;
-  UINT32 BusClockFreq, Idx;
+  UINT32 BusClockFreq, Idx, BusMode;
   UINT32 TimingMode[4] = {EMMCHS52DDR1V2, EMMCHS52DDR1V8, EMMCHS52, 
EMMCHS26};
 
   Host  = MmcHostInstance->MmcHost;
@@ -286,7 +286,19 @@ InitializeEmmcDevice (
 }
 Status = Host->SetIos (Host, BusClockFreq, 8, TimingMode[Idx]);
 if (!EFI_ERROR (Status)) {
-  Status = EmmcSetEXTCSD (MmcHostInstance, EXTCSD_BUS_WIDTH, 
EMMC_BUS_WIDTH_DDR_8BIT);
+  switch (TimingMode[Idx]) {
+  case EMMCHS52DDR1V2:
+  case EMMCHS52DDR1V8:
+BusMode = EMMC_BUS_WIDTH_DDR_8BIT;
+break;
+  case EMMCHS52:
+  case EMMCHS26:
+BusMode = EMMC_BUS_WIDTH_8BIT;
+break;
+  default:
+return EFI_UNSUPPORTED;
+  }
+  Status = EmmcSetEXTCSD (MmcHostInstance, EXTCSD_BUS_WIDTH, BusMode);
   if (EFI_ERROR (Status)) {
 DEBUG ((DEBUG_ERROR, "InitializeEmmcDevice(): Failed to set EXTCSD bus 
width, Status:%r\n", Status));
   }
-- 
1.9.1

___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

[edk2] [PATCH] UefiCpuPkg/SmmCpuFeatureLib: Add more CPU ID for SmmFeatureControl.

2017-06-11 Thread Jiewen Yao 
Add more CPU ID which can support SmmFeatureControl,
according to IA32 SDM.

Cc: Jeff Fan 
Cc: Michael Kinney 
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jiewen Yao 
---
 UefiCpuPkg/Library/SmmCpuFeaturesLib/SmmCpuFeaturesLib.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/UefiCpuPkg/Library/SmmCpuFeaturesLib/SmmCpuFeaturesLib.c 
b/UefiCpuPkg/Library/SmmCpuFeaturesLib/SmmCpuFeaturesLib.c
index 079baa4..b0c442e 100644
--- a/UefiCpuPkg/Library/SmmCpuFeaturesLib/SmmCpuFeaturesLib.c
+++ b/UefiCpuPkg/Library/SmmCpuFeaturesLib/SmmCpuFeaturesLib.c
@@ -296,7 +296,8 @@ SmmCpuFeaturesInitializeProcessor (
   // Intel(R) Core(TM) Processor Family MSRs.
   //
   if (FamilyId == 0x06) {
-if (ModelId == 0x3C || ModelId == 0x45 || ModelId == 0x46) {
+if (ModelId == 0x3C || ModelId == 0x45 || ModelId == 0x46 ||
+ModelId == 0x3D || ModelId == 0x47 || ModelId == 0x4E || ModelId == 
0x4F) {
   //
   // Check to see if the CPU supports the SMM Code Access Check feature
   // Do not access this MSR unless the CPU supports the 
SmmRegFeatureControl
-- 
2.7.4.windows.1

___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

[edk2] [PATCH v2] EmbeddedPkg/MmcDxe: Add alignment for ECSD data

2017-06-11 Thread Jun Nie 
Add alignment for ECSD data for DMA access. Otherwise
the data is corrupted on Sanechips platform.

Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Jun Nie 
---
 EmbeddedPkg/Universal/MmcDxe/Mmc.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/EmbeddedPkg/Universal/MmcDxe/Mmc.h 
b/EmbeddedPkg/Universal/MmcDxe/Mmc.h
index 8a7d5a3..6e3ab17 100644
--- a/EmbeddedPkg/Universal/MmcDxe/Mmc.h
+++ b/EmbeddedPkg/Universal/MmcDxe/Mmc.h
@@ -319,6 +319,7 @@ typedef struct  {
   OCR   OCRData;
   CID   CIDData;
   CSD   CSDData;
+  UINT64Pad;  // For 8 bytes alignment of 
ECSDData
   ECSD  ECSDData; // MMC V4 extended card specific
 } CARD_INFO;
 
-- 
1.9.1

___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

[edk2] [patch] MdeModulePkg/BMMUiLib: Fix incorrect variable name

2017-06-11 Thread Dandan Bi 
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=592

In function UpdateConsoleContent, we compare console name
with "ErrOut" string to check whether the content in console
Error device page has been changed. But when call function
UpdateConsoleContent, we pass console name as "ConErr" by mistake.
This patch is to fix the inconsistent issue.

Cc: Eric Dong 
Cc: Liming Gao 
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Dandan Bi 
---
 MdeModulePkg/Library/BootMaintenanceManagerUiLib/BootMaintenance.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/MdeModulePkg/Library/BootMaintenanceManagerUiLib/BootMaintenance.c 
b/MdeModulePkg/Library/BootMaintenanceManagerUiLib/BootMaintenance.c
index 3ff23a5..98e14c7 100644
--- a/MdeModulePkg/Library/BootMaintenanceManagerUiLib/BootMaintenance.c
+++ b/MdeModulePkg/Library/BootMaintenanceManagerUiLib/BootMaintenance.c
@@ -1300,11 +1300,11 @@ BootMaintCallback (
 if ((QuestionId >= CON_IN_DEVICE_QUESTION_ID) && (QuestionId < 
CON_IN_DEVICE_QUESTION_ID + MAX_MENU_NUMBER)) {
   UpdateConsoleContent (L"ConIn",CurrentFakeNVMap);
 } else if ((QuestionId >= CON_OUT_DEVICE_QUESTION_ID) && (QuestionId < 
CON_OUT_DEVICE_QUESTION_ID + MAX_MENU_NUMBER)) {
   UpdateConsoleContent (L"ConOut", CurrentFakeNVMap);
 } else if ((QuestionId >= CON_ERR_DEVICE_QUESTION_ID) && (QuestionId < 
CON_ERR_DEVICE_QUESTION_ID + MAX_MENU_NUMBER)) {
-  UpdateConsoleContent (L"ConErr", CurrentFakeNVMap);
+  UpdateConsoleContent (L"ErrOut", CurrentFakeNVMap);
 }
   }
 
   //
   // Pass changed uncommitted data back to Form Browser
-- 
1.9.5.msysgit.1

___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel