Thank you, Jaben.
I have added my comments inline
*From:* Carsey, Jaben [mailto:jaben.car...@intel.com]
*Sent:* Monday, August 17, 2015 11:12 AM
*To:* Daniel Samuelraj; uswg
*Cc:* edk2-devel@lists.01.org; Carsey, Jaben
*Subject:* RE: [uswg] Shell 2.0 and 2.1
(note: I changed the edk2 mailing list)
Daniel,
A UEFI Shell 2.0 application will work fine in UEFI Shell 2.1 with no
changes.
To create/build a UEFI Shell 2.1 application would need to have a version
of the UDK that has the updated protocol to get easy access to the new
API’s that were added to the protocol.
*[Samuelraj, Daniel] I assume that this UDK is not available yet?*
If you create a UEFI Shell 2.1 application AND you use a API in the
protocol that is not in the 2.0 version of the protocol, you should check
the version information in the protocol itself to make sure that the
application will function on a UEFI Shell 2.0 system (even if that just
generates an error). If you call the API that does not exist, you will
certainly have undefined behavior.
-Jaben
*From:* u...@uefi.org [mailto:u...@uefi.org ] *On
Behalf Of *Daniel
Samuelraj
*Sent:* Friday, August 14, 2015 9:40 AM
*To:* uswg ; edk2-de...@lists.sourceforge.net
*Subject:* [uswg] Shell 2.0 and 2.1
*Importance:* High
Hi,
I assume that Shell 2.0 apps are expected to run fine in Shell 2.1. Can you
please confirm?
Should shell 2.1 app be using new toolkit (e.g., UDK2014 or newer?) when
app want to make use of the content added in Shell 2.1?
Will there be any backward or forward compatibility issue? That is end user
running Shell 2.0 app in shell 2.1; similarly running Shell 2.1 app in
Shell 2.0?
Appreciate the response!
Thanks,
Daniel
___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
