From: Laszlo Ersek <lersek@redhat.com>
To: Andrew Fish <afish@apple.com>,
Michael Kinney <michael.d.kinney@intel.com>
Cc: krishnaLee <sssky307@163.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [RFC] Proposal to add edk2-apps repository
Date: Mon, 3 Dec 2018 15:11:33 +0100 [thread overview]
Message-ID: <0cecc14d-f268-6fcb-d185-e0bddecd4f1e@redhat.com> (raw)
In-Reply-To: <179708E3-F8AD-41B4-90B5-ECFD94924986@apple.com>
On 11/30/18 07:03, Andrew Fish wrote:
> Mike,
>
> As Krishna points out there are flavors of Apps. Do we want to have
> different packages for different flavor of apps, or different dirs in
> a more generic App package? Maybe we should define classes of UEFI
> Applications in the README.md and give them a place to live.
In my opinion, this is absolutely the first step that should be done.
Personally, I've just learned, from this thread, that there are *three*
(not two) UEFI application entry point types that edk2 supports.
* I've always known about main() -- libc app --, and ShellAppMain() --
shell app. I've always known these because I read about them in
"AppPkg/ReadMe.txt" and "StdLib/ReadMe.txt" years ago. In particular,
compare the description of "Hello" and "Main".
* And now MdeModulePkg/Application has been mentioned, in this thread,
where I see UefiMain() as the entry point.
I don't recall reading about UefiMain() or UefiApplicationEntryPoint on
this list. On the other hand, I remember several discussions where
people asked if they could write an application and invoke it from
SysPrep#### or similar, and the answer has always been, "oh sorry you
can't do that, because the lowest level you can go is ShellAppMain(),
and that won't work from SysPrep####".
Thanks
Laszlo
next prev parent reply other threads:[~2018-12-03 14:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 17:58 [RFC] Proposal to add edk2-apps repository Kinney, Michael D
2018-11-29 22:41 ` Leif Lindholm
2018-11-30 0:46 ` Kinney, Michael D
2018-11-30 1:44 ` krishnaLee
2018-11-30 3:40 ` Ni, Ruiyu
2018-11-30 15:49 ` Carsey, Jaben
2018-11-30 16:48 ` Kinney, Michael D
2018-12-03 2:01 ` krishnaLee
2018-11-30 6:03 ` Andrew Fish
2018-12-03 14:11 ` Laszlo Ersek [this message]
2018-12-03 15:07 ` Leif Lindholm
2018-12-03 17:10 ` Laszlo Ersek
2018-12-11 7:26 ` David F.
2018-11-30 3:32 ` Ni, Ruiyu
2018-11-30 4:57 ` Kinney, Michael D
2018-12-03 14:21 ` Laszlo Ersek
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=0cecc14d-f268-6fcb-d185-e0bddecd4f1e@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