public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Amit kumar <akamit91@hotmail.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: writing EDK compatible application.
Date: Tue, 4 Jul 2017 22:10:49 +0200	[thread overview]
Message-ID: <c0457df0-0f25-8e3b-f90f-d2d6e9260a2e@redhat.com> (raw)
In-Reply-To: <DM5PR11MB157806D4506F7109CCD8B4B2DCD70@DM5PR11MB1578.namprd11.prod.outlook.com>

On 07/04/17 19:20, Amit kumar wrote:
> 
> HI,
> 
> I have written a code (say helloworld program ) using edk2 framework, named the output efi file as BOOTx64.efi and placed it on a removable media in EFI/BOOT/ directory so that the application is listed in one time boot menu. When selected from boot menu it prints "Hello World".
> Which works as expected when tested on UEFI 2.3 and above platforms.
> But the same code fails to execute on EFI 1.10 platforms. Which i suppose is the problem with application entry point.
> Can somebody suggest me a way so that the application entry function can be compatible to both the platform. Even when written according to UEFI 2.5+ Spec ?

I don't think you can develop for EFI 1 using edk2 -- unless you use
EdkCompatibilityPkg I guess. But, I don't know how much
EdkCompatibilityPkg is maintained.

Here's some links:

https://github.com/tianocore/tianocore.github.io/wiki/EdkCompatibilityPkg

https://github.com/tianocore/tianocore.github.io/wiki/EDK

The entry point is likely the least of your problems. The library
instances pulled in from under MdePkg, MdeModulePkg etc are full of UEFI
2.* dependencies, I'm pretty sure. I would suggest ignoring EFI 1...

Thanks
Laszlo


  parent reply	other threads:[~2017-07-04 20:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-04 17:20 writing EDK compatible application Amit kumar
2017-07-04 17:35 ` Marvin H?user
2017-07-04 17:46   ` Amit kumar
2017-07-04 17:51     ` Marvin Häuser
2017-07-04 17:55       ` Amit kumar
2017-07-04 18:13         ` Amit kumar
2017-07-04 21:30           ` Andrew Fish
2017-07-04 20:10 ` Laszlo Ersek [this message]
2017-07-05 12:24   ` Amit kumar
2017-07-05 12:58   ` Rod Smith

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=c0457df0-0f25-8e3b-f90f-d2d6e9260a2e@redhat.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