Re: [edk2] [PATCH v4 00/11] OvmfPkg: Introduce and use the new VIRTIO_DEVICE_PROTOCOL protocol

2013-10-28 Thread Olivier Martin
Unfortunately, the caller (the VirtIo Block driver) does not know if the access is unaligned. The VirtIo Block driver does not necessary know if the transport layer is PCI and has not got PCI-X capability (case when the access is unaligned). One other solution would be to handle the 64bit unalig

Re: [edk2] UEFI SCT few queries

2013-10-28 Thread Li, Ruth
Hi Prabhakar, Recommend you bring your question to UTWG group. Email: u...@uefi.org Thanks, Ruth From: Prabhakar Kushwaha [mailto:prabha...@freescale.com] Sent: Tuesday, October 29, 2013 12:17 PM To: boot-architect...@lists.linaro.org; edk2-devel@lists.sourceforge.net; b45

[edk2] UEFI SCT few queries

2013-10-28 Thread Prabhakar Kushwaha
Hi List, I am new to UEFI and exploring about SCT. I have very basic question regarding SCT. 1) In order to use SCT in an organization, do we require any special license? 2) Looks like SCT compliance testing is only internal to an organization. We don't require to publish its details outs

[edk2] [PATCH 3/8] OvmfPkg: Add NV Variable storage within FD

2013-10-28 Thread Jordan Justen
Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Jordan Justen --- OvmfPkg/OvmfPkgIa32.fdf| 93 ++-- OvmfPkg/OvmfPkgIa32X64.fdf | 93 ++-- OvmfPkg/OvmfPkgX64.fdf | 93 ++

[edk2] [PATCH 7/8] OvmfPkg: Add QemuFlashFvbServicesRuntimeDxe to firmware image

2013-10-28 Thread Jordan Justen
This driver will support a flash FVB implementation if QEMU flash is detected. The driver is added to the apriori list to make sure it runs before the EmuVariableFvbRuntimeDxe driver. If this driver detects flash support, then it will disable the EmuVariableFvbRuntimeDxe driver by setting PcdFlash

[edk2] [PATCH 1/8] OvmfPkg: Increase DEBUG build size to 2MB by default

2013-10-28 Thread Jordan Justen
The 1MB image with full debug and the shell included is too large to implement flash based non-volatile variable. After this change, building with -D FD_SIZE_1MB will force the smaller flash size. The default size for RELEASE build remains at 1MB, so using -b RELEASE on the build command line wil

[edk2] [PATCH 2/8] OvmfPkg: Add flash PCD items

2013-10-28 Thread Jordan Justen
Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Jordan Justen --- OvmfPkg/OvmfPkg.dec | 12 +++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/OvmfPkg/OvmfPkg.dec b/OvmfPkg/OvmfPkg.dec index d874f0c..01fe469 100644 --- a/OvmfPkg/OvmfPkg.dec +++ b/O

[edk2] [PATCH 5/8] OvmfPkg/EmuVariableFvbRuntimeDxe: Disable if flash variables are supported

2013-10-28 Thread Jordan Justen
If QEMU flash is supported, then the PcdFlashNvStorageVariableBase64 will be set by the flash FVB driver. If it is set to a non-zero value, then we disable memory based variables. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Jordan Justen --- OvmfPkg/EmuVariableFvbRunti

[edk2] [PATCH 4/8] OvmfPkg/AcpiPlatformDxe/Qemu: Allow high runtime memory regions

2013-10-28 Thread Jordan Justen
Previously we would only search for MMIO regions that were also above every EfiGcdMemoryTypeReserved and EfiGcdMemoryTypeSystemMemory region. Now we just search for the largest EfiGcdMemoryTypeMemoryMappedIo region. This will allow us to mark the flash memory as a runtime memory region in order t

[edk2] [PATCH 0/8] OVMF support for QEMU's PC System Flash

2013-10-28 Thread Jordan Justen
https://github.com/jljusten/edk2.git ovmf-nvvars-v1 This series implements support for QEMU's emulated system flash. This allows for persistent UEFI non-volatile variables. Previously we attemptedto emulate non-volatile variables in a few ways, but each of them would fail in particular situation

[edk2] [PATCH 8/8] OvmfPkg/build.sh: Support --enable-flash switch

2013-10-28 Thread Jordan Justen
Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Jordan Justen --- OvmfPkg/build.sh | 40 +--- 1 file changed, 29 insertions(+), 11 deletions(-) diff --git a/OvmfPkg/build.sh b/OvmfPkg/build.sh index f64ea91..e491eff 100755 --- a/OvmfPk

Re: [edk2] How to append to DB?

2013-10-28 Thread Michael
On 29.10.2013 00:58, Jarlstrom, Laurie wrote: Hi Michael, A good place to start is with the Security Package on Edk II. http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=SecurityPkg There are also a couple PDFs for "HOW TO" enable security and sign UEFI Applications. thank

Re: [edk2] How to append to DB?

2013-10-28 Thread Jarlstrom, Laurie
Hi Michael, A good place to start is with the Security Package on Edk II. http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=SecurityPkg There are also a couple PDFs for "HOW TO" enable security and sign UEFI Applications. thanks, Laurie laurie.jarlst...@intel.com

Re: [edk2] How to append to DB?

2013-10-28 Thread Michael
On 28.10.2013 23:27, Carsey, Jaben wrote: What DB? I am not sure what you want... -Jaben From: Michael [mailto:jollh...@riseup.net] Sent: Monday, October 28, 2013 10:59 AM To: edk2-devel@lists.sourceforge.net Subject: [edk2] How to append to DB? Hi, I need to add an entry in the DB from uefi

Re: [edk2] How to append to DB?

2013-10-28 Thread Andrew Fish
On Oct 28, 2013, at 12:27 PM, Carsey, Jaben wrote: > What DB? I assume he means the key database, as defined in Chapter 27 Secure Boot and Driver Signing. Thanks, Andrew Fish > I am not sure what you want... > > -Jaben > > From: Michael [mailto:jollh...@riseup.net] > Sent: Monday, Octo

Re: [edk2] How to append to DB?

2013-10-28 Thread Carsey, Jaben
What DB? I am not sure what you want... -Jaben From: Michael [mailto:jollh...@riseup.net] Sent: Monday, October 28, 2013 10:59 AM To: edk2-devel@lists.sourceforge.net Subject: [edk2] How to append to DB? Hi, I need to add an entry in the DB from uefi app. How can I do that with the UEFI appli

Re: [edk2] [PATCH] OvmfPkg/PlatformPei: emulated NV storage must be EfiRuntimeServicesData

2013-10-28 Thread Jordan Justen
Reviewed-by: Jordan Justen On Mon, Oct 28, 2013 at 5:04 AM, Laszlo Ersek wrote: > SVN r14770 ("OvmfPkg/PlatformPei: correctly align emulated NV storage") > made sure the emulated NV storage was allocated with correct alignment. > > However, the AllocateRuntimePool() -> AllocateAlignedPages() cha

[edk2] How to append to DB?

2013-10-28 Thread Michael
Hi, I need to add an entry in the DB from uefi app. How can I do that with the UEFI application? I tried to do it in custom mode, but an error occurs security violation. Am I doing something wrong? -- October Webinars: Co

Re: [edk2] [PATCH v3 00/10] OvmfPkg: Introduce and use the new VIRTIO_DEVICE_PROTOCOL protocol

2013-10-28 Thread Laszlo Ersek
On 09/28/13 20:51, Mark Salter wrote: > On Fri, 2013-09-27 at 02:31 +0200, Laszlo Ersek wrote: >> Hi Mark, >> >> just my 2 cents: >> >> On 09/26/13 21:33, Mark Salter wrote: >>> I've been trying out this patch series on AArch64 foundation model. >>> I have UEFI booting a linux kernel image in an EF

Re: [edk2] efibootmgr throws error

2013-10-28 Thread Andrew Fish
On Oct 28, 2013, at 4:54 AM, b_b_si...@dell.com wrote: > Hi All, > > When I try to delete the entry “efibootmgr -b –B” I get the below > message. > requested operation failed: status=8002 > efivars: set_variable() failed: status=8009 in dmesg > > May I please kno

Re: [edk2] [PATCH v4 05/11] OvmfPkg/VirtioPciDeviceDxe: Implement VIRTIO_DEVICE_PROTOCOL for VirtIo Devices over PCI

2013-10-28 Thread Laszlo Ersek
On 10/16/13 19:29, Olivier Martin wrote: > This change implements the VIRTIO_DEVICE_PROTOCOL for the PCI transport > layer. > The VirtIo device drivers will interact with the PCI-based VirtIo devices > through this protocol implementation. > > Contributed-under: TianoCore Contribution Agreement 1.

Re: [edk2] [PATCH v4 04/11] OvmfPkg/VirtioDevice.h: Introduced VIRTIO_DEVICE_PROTOCOL protocol

2013-10-28 Thread Laszlo Ersek
On 10/16/13 19:29, Olivier Martin wrote: > This protocol introduces an abstraction to access the VirtIo > Configuration and Device spaces. > The registers in these spaces are located at a different offset and have > a different width whether the transport layer is either PCI or MMIO. This > protoco

Re: [edk2] efibootmgr error message

2013-10-28 Thread Laszlo Ersek
On 10/28/13 13:59, parmeshwr_pra...@dell.com wrote: > > When I try to delete the entry “efibootmgr -b –B” I get the below > message. > > requested operation failed: status=8002 > > efivars: set_variable() failed: status=8009 in dmesg > > > > May I please know w

[edk2] efibootmgr error message

2013-10-28 Thread Parmeshwr_Prasad
Hi All, When I try to delete the entry "efibootmgr -b -B" I get the below message. requested operation failed: status=8002 efivars: set_variable() failed: status=8009 in dmesg May I please know what is this error & status 8002 mean? Why I'm gettin

[edk2] [PATCH] OvmfPkg/PlatformPei: emulated NV storage must be EfiRuntimeServicesData

2013-10-28 Thread Laszlo Ersek
SVN r14770 ("OvmfPkg/PlatformPei: correctly align emulated NV storage") made sure the emulated NV storage was allocated with correct alignment. However, the AllocateRuntimePool() -> AllocateAlignedPages() change flipped the memory type from EfiRuntimeServicesData to EfiBootServicesData. This cause

Re: [edk2] [PATCH] OvmfPkg/PlatformPei: emulated NV storage must be EfiRuntimeServicesData

2013-10-28 Thread Wei Liu
On Mon, Oct 28, 2013 at 01:04:33PM +0100, Laszlo Ersek wrote: > SVN r14770 ("OvmfPkg/PlatformPei: correctly align emulated NV storage") > made sure the emulated NV storage was allocated with correct alignment. > > However, the AllocateRuntimePool() -> AllocateAlignedPages() change > flipped the me

[edk2] [PATCH] OvmfPkg/PlatformPei: emulated NV storage must be EfiRuntimeServicesData

2013-10-28 Thread Laszlo Ersek
SVN r14770 ("OvmfPkg/PlatformPei: correctly align emulated NV storage") made sure the emulated NV storage was allocated with correct alignment. However, the AllocateRuntimePool() -> AllocateAlignedPages() change flipped the memory type from EfiRuntimeServicesData to EfiBootServicesData. This cause

Re: [edk2] [PATCH v4 03/11] OvmfPkg/Virtio.h: Added the Virtio Vendor and MMIO IDs

2013-10-28 Thread Laszlo Ersek
On 10/16/13 19:29, Olivier Martin wrote: > Contributed-under: TianoCore Contribution Agreement 1.0 > Signed-off-by: Olivier Martin > --- > OvmfPkg/Include/IndustryStandard/Virtio.h |7 +++ > 1 files changed, 7 insertions(+), 0 deletions(-) > > diff --git a/OvmfPkg/Include/IndustryStandar

Re: [edk2] [PATCH v4 02/11] OvmfPkg/Virtio.h: Added PCI/MMIO Virtio Headers Offsets

2013-10-28 Thread Laszlo Ersek
On 10/16/13 19:29, Olivier Martin wrote: > Offsets are different between the PCI and MMIO transport layer. > > Contributed-under: TianoCore Contribution Agreement 1.0 > Signed-off-by: Olivier Martin > --- > OvmfPkg/Include/IndustryStandard/Virtio.h | 35 > + > 1 fi

Re: [edk2] [PATCH v4 01/11] OvmfPkg/Virtio.h: Added the macros that define the Device Specific Configuration Offset

2013-10-28 Thread Laszlo Ersek
On 10/16/13 19:29, Olivier Martin wrote: > The Device Specific Configuration region is located at different locations > for the VirtIo devices over PCI, PCI with MSI-X capability, MMIO. > > Contributed-under: TianoCore Contribution Agreement 1.0 > Signed-off-by: Olivier Martin > --- > OvmfPkg/In

Re: [edk2] [PATCH v4 00/11] OvmfPkg: Introduce and use the new VIRTIO_DEVICE_PROTOCOL protocol

2013-10-28 Thread Laszlo Ersek
On 10/16/13 19:29, Olivier Martin wrote: > Changelog from v3: > -- > - Fixed 'write size' in VIRTIO_DEVICE_WRITE comment > - Made all the functions of the protocol return EFI_STATUS > - Removed 'VIRTIO_GET_GUEST_FEATURES GetGuestFeatures' > - Added a note about the fact VIRTIO_SET