Re: [edk2] Using CryptoPkg on my platform

Subject: Re: [edk2] Using CryptoPkg on my platform

From: Andrew Fish <>

To: "" <>

Date: 2011-09-22 16:53:28

Sent from my iPad

On Sep 22, 2011, at 7:50 AM, Daniel Moral <> wrote:

Hi all.
I have an x64 platform which a BIOS which supports EDK version 1. I want to use the CryptoPkg libraries to build shell applications that work on that board. Nevertheless I do not know how should I port it.
1- Should I try to adapt the CryptoPkg libraries to EDK1 and build my application in that environment?
2- Or should I try to create my applicaton on the EDK2 environment?
In the last case, how do I put the libraries that I do need on my BIOS? Should I compile the CryptoDxe driver and add it as a binary to my BIOS or should I try to adapt it to my BIOS built?
Each application/driver has it's own copies of the libraries. There is no dynamic linking in EFI, everything is abstracted via protocols.

I am a bit lost with this topic. I have been using EDK1 for some months but I have never tried to use EDK2 features on a EDK1 based platform so I would really appreciate your help.

In general EDK1 or edk2 should not matter. What really maters is what protocols the application consumes. Note that some library functions consume protocols. The over simple answer to the protocol changes over time is the transition from Intel's EFI/Framework to the industry standard UEFI/PI.

The edk2 can build EDK1 code using the EdkCompatabilityPkg. The edk2 shell will not run on older EFI platforms as it assumes UEFI HII and DevicePathToText are present.


All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
edk2-devel mailing list