From: krishnaLee <sssky307@163.com>
To: edk2-devel@lists.01.org
Subject: question about uefi shell pipe.
Date: Wed, 4 Jul 2018 17:15:44 +0800 (CST) [thread overview]
Message-ID: <3009b28c.9942.16464937ab3.Coremail.sssky307@163.com> (raw)
Hi,
I wrote this shell application(smalltest.efi),did some pipe function test,find some strange result.
boot into shell:
# test-1,the follow two command should has the same output ,but infact not the same in QEMU,and the second command failed WriteFile in real machine(AMI bios uefi 2.6):
ls | smalltest.efi
ls | smalltest.efi | smalltest.efi # the ls command directory only has one file(this tool),so the tool's buffer 80x25*4 won't overflow.
#test-2
run smalltest.efi,
just key in some chars and Enter,nothing output,why?
my test environment:
UDK2018 + vs2015
QEMU emulator version 2.10.95
OVMF_X64.fd( x64,release build)
the tool's build command:
D:\edk2-vUDK2018>build -p ShellPkg\ShellPkg.dsc -m ShellPkg\Application2\smalltest\smalltest.inf -a X64 -b RELEASE
//--------code---smalltest.c-------------
#include <Uefi.h>
#include <Library/UefiApplicationEntryPoint.h>
#include <Library/UefiLib.h>
#include <Library/UefiBootServicesTableLib.h>//global gST gBS gImageHandle
#include <Library/BaseMemoryLib.h>
#include <Library/MemoryAllocationLib.h>
#include <Protocol/Shell.h>
#include <Protocol/ShellParameters.h>
EFI_STATUS
EFIAPI
UefiMain (
IN EFI_HANDLE ImageHandle,
IN EFI_SYSTEM_TABLE *SystemTable
)
{
EFI_STATUS status;
EFI_SHELL_PROTOCOL* gShell;
EFI_SHELL_PARAMETERS_PROTOCOL*gParameters;
UINT16 Buffer[80*25*4]; //tool's buffer;
UINTN BufferSize=sizeof(Buffer);
UINTN BufferByteSize=BufferSize*sizeof(UINT16);
status=gBS->HandleProtocol(gImageHandle,&gEfiShellParametersProtocolGuid,&gParameters);
if(status!=EFI_SUCCESS)
{
Print(L"locate gEfiShellParametersProtocolGuid failed.\n");
return status;
}
status=gBS->LocateProtocol(&gEfiShellProtocolGuid,NULL,&gShell);
if(status!=EFI_SUCCESS)
{
Print(L"locate gEfiShellProtocolGuid failed.\n");
return status;
}
status=gShell->ReadFile(gParameters->StdIn,&BufferByteSize,(VOID*)Buffer);
if(status!=EFI_SUCCESS)
{
Print(L"read from gParameters->StdIn failed.\n");
return status;
}
status=gShell->WriteFile(gParameters->StdOut,&BufferByteSize,(VOID*)Buffer);
if(status!=EFI_SUCCESS)
{
Print(L"wirte gParameters->StdOut failed\n");
return status;
}
gShell->FlushFile(gParameters->StdOut);
return EFI_SUCCESS;
}
//--------code---smalltest.inf-------------
[Defines]
INF_VERSION = 0x00010005
BASE_NAME = smalltest
FILE_GUID = 8F7D7B1D-0E1C-4c98-B12E-4EC99C400704
MODULE_TYPE = UEFI_APPLICATION
VERSION_STRING = 1.0
ENTRY_POINT = UefiMain
[Sources]
smalltest.c
[Packages]
MdePkg/MdePkg.dec
[Protocols]
gEfiShellProtocolGuid
gEfiShellParametersProtocolGuid
[LibraryClasses]
UefiApplicationEntryPoint
UefiLib
//--------code---end----------------------------------------------------------
thank you,
by krishna.
next reply other threads:[~2018-07-04 9:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 9:15 krishnaLee [this message]
2018-07-04 14:55 ` question about uefi shell pipe Andrew Fish
2018-07-05 0:34 ` krishnaLee
[not found] ` <a0121e33a4124122b955158310cafa98@ausx13mps335.AMER.DELL.COM>
[not found] ` <34bf3bdd.43b7.1646d5dd393.Coremail.sssky307@163.com>
[not found] ` <2c4c067c.593d.1646d8eb20d.Coremail.sssky307@163.com>
2018-07-06 3:34 ` krishnaLee
2018-07-09 7:17 ` Gao, Liming
2018-07-10 8:49 ` krishnaLee
2018-07-06 3:50 ` krishnaLee
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=3009b28c.9942.16464937ab3.Coremail.sssky307@163.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