From: Ramesh R. <rameshr@ami.com>
To: GN Keshava <keshava.gn@gmail.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: UEFI shell vs UEFI BIOS version compatibility
Date: Tue, 23 May 2017 12:25:36 +0000 [thread overview]
Message-ID: <FCB618580B279147A99F061E09CFF06DE6AA3EB1@Venus2.in.megatrends.com> (raw)
In-Reply-To: <CABKwMdv5TvyBKbaDQOKkX_ML-fWPyLpQ2z28KVBZD5pcvQi_CQ@mail.gmail.com>
Hi,
Old Shell was installing EFI_SHELL_INTERFACE and new shell is installing the EFI_SHELL_PARAMETERS_PROTOCOL on the shell application.
Thanks,
Ramesh
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of GN Keshava
Sent: 23 May 2017 17:01
To: edk2-devel@lists.01.org
Subject: [edk2] UEFI shell vs UEFI BIOS version compatibility
Hi all,
I was using older version of UEFI shell (older EFI shell inside EdkShellBinPkg). It was working fine with my testing PCs (Intel core i5 (Dell Optiplex 7020) (UEFI ver 2.31) as well as Intel Gigabit motherboard (UEFI ver 2.4)). I'm able to load any driver efi and use it.
Now I'm trying newer UEFI shell (UEFI Interactive shell v 2.2, the newer one in ShellBinPkg).
I'm trying to load my driver (and default Fat.efi driver downloaded from github as well) It is working fine with Intel Gigabit motherboard (UEFI ver 2.4). I'm able to load the driver and use it.
But if I try to load the same efi driver on newer UEFI shell v2.2 on Intel core i5 (Dell Optiplex 7020) (UEFI ver 2.31), display is just turning black, and I'm not able to use the shell any further. (But I'm able to load my custom shell application!)
What could be the issue? Any help is much appreciated.
Thanks.
With regards,
Keshava
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2017-05-23 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 11:31 UEFI shell vs UEFI BIOS version compatibility GN Keshava
2017-05-23 12:25 ` Ramesh R. [this message]
2017-05-23 12:34 ` GN Keshava
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=FCB618580B279147A99F061E09CFF06DE6AA3EB1@Venus2.in.megatrends.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