From: "Carsey, Jaben" <jaben.carsey@intel.com>
To: Tim Lewis <tim.lewis@insyde.com>,
Meenakshi Aggarwal <meenakshi.aggarwal@nxp.com>,
"edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>
Cc: "Carsey, Jaben" <jaben.carsey@intel.com>
Subject: Re: Shell version 2.2
Date: Fri, 5 Aug 2016 19:09:45 +0000 [thread overview]
Message-ID: <CB6E33457884FA40993F35157061515C549E4A2A@FMSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: <7236196A5DF6C040855A6D96F556A53F3DA5B3@msmail.insydesw.com.tw>
Tim,
Yes, ver command would output that the version of the shell is different.
The #define below is specifically the version of the Protocol, not the version of the spec.
It could have been a miss on the part of the committee, but that was hoe I interpreted the non-change to the protocol version.
-Jaben
> -----Original Message-----
> From: Tim Lewis [mailto:tim.lewis@insyde.com]
> Sent: Friday, August 5, 2016 11:36 AM
> To: Carsey, Jaben <jaben.carsey@intel.com>; Meenakshi Aggarwal
> <meenakshi.aggarwal@nxp.com>; edk2-devel@lists.01.org <edk2-
> devel@ml01.01.org>
> Subject: RE: Shell version 2.2
> Importance: High
>
> Jaben --
>
> Are there no shell commands where the standard command-line parameters
> have changed?
>
> Tim
>
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Carsey, Jaben
> Sent: Friday, August 05, 2016 10:26 AM
> To: Meenakshi Aggarwal <meenakshi.aggarwal@nxp.com>; edk2-
> devel@lists.01.org <edk2-devel@ml01.01.org>
> Cc: Carsey, Jaben <jaben.carsey@intel.com>
> Subject: Re: [edk2] Shell version 2.2
>
> I think that that version (2.1) is correct for the version of the protocol. The
> protocol API was not changed for the UEFI Shell 2.2.
>
> That is the current version and should support the 2.2 spec.
>
> -Jaben
>
> > -----Original Message-----
> > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> > Meenakshi Aggarwal
> > Sent: Friday, August 5, 2016 2:20 AM
> > To: edk2-devel@lists.01.org <edk2-devel@ml01.01.org>
> > Subject: [edk2] Shell version 2.2
> > Importance: High
> >
> > Hi,
> >
> >
> > I can see UEFI shell specification 2.2
> > (http://www.uefi.org/sites/default/files/resources/UEFI_Shell_2_2.pdf)
> > is available, But on edk2 master branch current version of Shell is still showing
> 2.1.
> >
> > File:ShellPkg/Include/Protocol/EfiShell.h
> >
> > enum ShellVersion {
> > SHELL_MAJOR_VERSION = 2,
> > SHELL_MINOR_VERSION = 1
> > };
> >
> >
> >
> > Please tell if I am looking at correct file, actually I want to update
> > my shell to 2.2, but it looks like edk2 master branch doesn't support shell
> specification 2.2.
> >
> > Is my understanding correct?
> >
> >
> >
> > Thanks & Regards,
> > Meenakshi
> > _______________________________________________
> > edk2-devel mailing list
> > edk2-devel@lists.01.org
> > https://lists.01.org/mailman/listinfo/edk2-devel
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2016-08-05 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 9:20 Shell version 2.2 Meenakshi Aggarwal
2016-08-05 17:26 ` Carsey, Jaben
2016-08-05 18:36 ` Tim Lewis
2016-08-05 19:09 ` Carsey, Jaben [this message]
2016-08-05 19:16 ` Tim Lewis
2016-08-05 19:34 ` Bhupesh Sharma
2016-08-05 19:46 ` Rothman, Michael A
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=CB6E33457884FA40993F35157061515C549E4A2A@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