Reviewed-by: Ruiyu Ni
Do you have the rights to check in the patch? If not I can help to do that.
Thanks,
Ray
-Original Message-
From: Laszlo Ersek [mailto:ler...@redhat.com]
Sent: Sunday, June 09, 2013 5:47 PM
To: Ni, Ruiyu; edk2-devel@lists.sourceforge.net
Subject: [PATCH v2] Variabl
I was looking through the ArmPlatformPkg/ArmVExpressPkg/ArmVExpress-RTSM-*.fdf
files, and there looks like an FD section anomaly.
The Size variable is set to 0x0028, but the regions add up to 0x0030.
What size is really intended? Too bad the tools don't catch this kind of thing.
Size
On Jun 12, 2013, at 12:26 PM, "Pant, Alok" wrote:
> Hi all,
> May I seek suggestions or pointers as to how a UEFI BIOS can support runtime
> variable service over NAND devices (such as eMMC/UFS etc.).
>
> As I understand once BIOS handoff control to OS the OS driver takes control
> and own
Hi all,
May I seek suggestions or pointers as to how a UEFI BIOS can support runtime
variable service over NAND devices (such as eMMC/UFS etc.).
As I understand once BIOS handoff control to OS the OS driver takes control and
own the host controller to send command. If later OS call UEFI runtime
UEFI SCT is a good option for DXE drivers & Applications. SCT has test cases
for each of the UEFI driver model protocols defined in 2.3.1
You can build the SCT and you need to provide the driver handle &
controller handle
so that SCT can detect your driver
On Wed, Jun 12, 2013 at 10:20 PM, Thoma
How are you guys doing unit testing for DXE drivers and applications?
Is anyone using Visual Studio's testing features? Is anyone doing it with
VMware Workstation?
My test environment is very primitive and I'd like to improve it. Right now
I have a script to pull the latest from source control, b
