From: "Ni, Ruiyu" <ruiyu.ni@Intel.com>
To: "Palmer, Thomas" <thomas.palmer@hpe.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Poll: When to use OVMF and Nt32?
Date: Fri, 9 Feb 2018 15:05:32 +0800 [thread overview]
Message-ID: <58558f4d-1d88-27ff-915c-e19a8dc825be@Intel.com> (raw)
In-Reply-To: <TU4PR8401MB1086CDFDD2D962B82B84B0E6EDF30@TU4PR8401MB1086.NAMPRD84.PROD.OUTLOOK.COM>
On 2/9/2018 2:46 AM, Palmer, Thomas wrote:
>
> EDK2 community,
>
> When developing/testing UEFI and you can easily choose between using OVMF and Nt32, which do you choose and why? When is OVMF better/easier to use than Nt32 and vice versa?
>
> I ask because I am giving an internal presentation to our newer employees. I've used one over the other for personal reasons, but I'd like to hear your thoughts and learn something new.
When developing pure UEFI application/driver that doesn't access real
HW, NT32 is the best environment because Visual Studio debugger can be used.
When developing application/driver that needs to access real HW,
OVMF or any other real HW platform should be used.
>
>
> Regards,
>
> Thomas Palmer
> Firmware Engineer
> Enterprise Group
> Industry Standard Servers
>
> thomas.palmer@hpe.com<mailto:thomas.palmer@hpe.com>
> T +1 281 518 2564
> Hewlett Packard Enterprise
> 11445 Compaq Center Drive West
> Houston, TX 77070-1433
> USA
>
> [cid:image001.jpg@01D1CF0D.54B64190]
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
>
--
Thanks,
Ray
next prev parent reply other threads:[~2018-02-09 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 18:46 Poll: When to use OVMF and Nt32? Palmer, Thomas
2018-02-09 7:05 ` Ni, Ruiyu [this message]
2018-02-12 21:20 ` Richardson, Brian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=58558f4d-1d88-27ff-915c-e19a8dc825be@Intel.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox