From: "Carsey, Jaben" <jaben.carsey@intel.com>
To: Rafael Machado <rafaelrodrigues.machado@gmail.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Carsey, Jaben" <jaben.carsey@intel.com>
Subject: Re: Improvement at Wiki (EFI_SHELL_INTERFACE)
Date: Mon, 9 Jan 2017 15:44:02 +0000 [thread overview]
Message-ID: <CB6E33457884FA40993F35157061515C54B3DE5B@FMSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: <CACgnt7-qq+ZHK-zu1DaGUNES1NnWVpsvLzY4iGhdHLpa+CQZVw@mail.gmail.com>
Rafael,
Actually it's the opposite. EFI_SHELL_INTERFACE is the older and deprecated protocol. I do not know of any active development using that protocol.
-Jaben
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Rafael
> Machado
> Sent: Saturday, January 7, 2017 1:14 PM
> To: edk2-devel@lists.01.org
> Subject: [edk2] Improvement at Wiki (EFI_SHELL_INTERFACE)
> Importance: High
>
> Hi everyone
>
> During a a development I faced the following wiki information at tianocore's
> github:
>
> https://github.com/tianocore/tianocore.github.io/wiki/Creating-a-Shell-
> Application#Using_EFI_SHELL_PROTOCOL
>
> I remember a case when I was working with a system that didn't have a instance
> of the EFI_SHELL_PARAMETERS_PROTOCOL, and the solution was to use the
> EFI_SHELL_INTERFACE protocol, that seems to be a newer protocol to be used
> when doing something like what the wiki presents.
>
> I believe it would be nice to update this wiki adding this information.
>
> Thanks and Regards
> Rafael R. Machado
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2017-01-09 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-07 21:13 Improvement at Wiki (EFI_SHELL_INTERFACE) Rafael Machado
2017-01-09 15:44 ` Carsey, Jaben [this message]
2017-01-09 18:22 ` Jarlstrom, Laurie
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=CB6E33457884FA40993F35157061515C54B3DE5B@FMSMSX103.amr.corp.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