Hi all,
I am working on some project where I need to open Disk protocol.
Below is my code-
Status = gBS->OpenProtocol(ControllerHandle
,&gEfiDiskIoProtocolGuid,(VOID **) &DiskIo, gImageHandle, NULL,
EFI_OPEN_PROTOCOL_BY_DRIVER);
if (EFI_ERROR(Status)) {
Print(L"Disk IO
hi:
everybody! i'am porting edkii to a arm cortex a7 soc, everything looks well.
but when i enter shell,
there is some problem: i can use "ctrl+c" to stop app in my uart console. this
is ctrl+c do not work on my platform !
is there any guys had meet such a situation ?
zhengjiewen2005
Fro
hi:
everybody! i'am porting edkii to a arm cortex a7 soc, everything looks well.
but when i enter shell,
there is a problem: i can‘t use "ctrl+c" to stop app in my uart console. that
means ctrl+c do not work on my platform !
is there any guys had meet such a situation ?
zhengjiewen2005
F
(Let's start again the discussion with a clear title)
Hi,
Do you know if CTLR+C is supported by the shell? If no, do you know if your
EFI application support CTRL+C ?
Thanks,
Olivier
From: zhengjiewen2005 [mailto:zhengjiewen2...@163.com]
Sent: 17 October 2013 14:59
To: edk2-devel
Subject: [edk2]
Hello!
I have trouble booting DuetPkg on some configurations. I need advice
on fixing/troubleshooting. Details follow.
1. Checked out today's trunk/edk2,
2. edited Conf\target.txt to use "IA32 X64" arch and DDK3790 toolchain,
2. built DuetPkg{IA32,X64}.dsc, ran PostBuild.bat {IA32,X64},
3. eventua
Parmeshwr,
Likely because a different driver has already opened that specific Disk I/O
protocol instance. The BY_DRIVER open mode is a request to open the protocol
and then prevent other drivers from opening the same protocol. If you use the
openinfo shell command on the handle that contains
I'm linking against a third party library that already defines GUID, so
it's clashing with GUID in MdePkg/Library/Base.h. I'd prefer not to change
the third party library for licensing reasons.
My question is, why does edk2 have GUID and EFI_GUID when they are both the
same thing? Why doesn't it j
Hi All & Jaben,
Do you have any comments on the below observation?
Thanks,
Ramesh
-Original Message-
From: Ramesh R. [mailto:rame...@ami.com]
Sent: Friday, October 11, 2013 11:01 PM
To: edk2-devel@lists.sourceforge.net
Cc: Rashmi Prakash
Subject: Re: [edk2] ConsoleIn behavior with She
I do not believe that the shell's ReadKey is being called during your
application's operation. The thread from the shell is in your application at
that time. I would guess that the ReadKey gets called after your application
ends and then it handles the information from the key that was pressed
The shell will create and event to monitor for CTRL+C if the platform supports
it. There is no requirement that the platform support it.
-Jaben
From: Olivier Martin [mailto:olivier.mar...@arm.com]
Sent: Thursday, October 17, 2013 7:08 AM
To: 'zhengjiewen2005'; edk2-devel
Subject: Re: [edk2] ctr
Try doing this after getting user input, directly before your application
ends:
Status = gST->ConIn->Reset (gST->ConIn, TRUE);
Does the shell still look like it is getting the input?
On Thu, Oct 17, 2013 at 11:57 AM, Carsey, Jaben wrote:
> I do not believe that the shell's ReadKey is being ca
On 10/17/2013 11:39 AM, Sergei Antonov wrote:
> Hello!
> I have trouble booting DuetPkg on some configurations. I need advice
> on fixing/troubleshooting. Details follow.
...
> The results on two different BIOS PCs are:
>
> PC #1 (64-bit AMD CPU, 4 GB of RAM, no HDDs)
>IA32: halts on "*** INT 6
>> X64: hangs on "WELCOME TO EFI WORLD!" screen
I had the *same* error/hang about 6 weeks ago, trying to get DUET to
run, on an Intel x64 (no AMD hardware involved), built via EDK-II trunk.
I suspect DUET sees the same QA that it once did. I gave up on DUET, and
switched to OVMF, and am happy.
EDKII also has BASE type module, such as BaseLib. They don't use UEFI/PI
definition. So, GUID structure is defined for them.
Thanks
Liming
From: Thomas Rognon [mailto:tcrog...@gmail.com]
Sent: Friday, October 18, 2013 12:37 AM
To: edk2-devel
Subject: [edk2] Why does edk2 have both GUID and EFI_GU
Signed-off-by: Roy Franz
Contributed-under: TianoCore Contribution Agreement 1.0
---
ArmPlatformPkg/Drivers/NorFlashDxe/NorFlashFvbDxe.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ArmPlatformPkg/Drivers/NorFlashDxe/NorFlashFvbDxe.c
b/ArmPlatformPkg/Drivers/NorFlashDxe
Hi, carsey and Olivier:
let me describe the problem more detailly.
first, I use the the shell efi from the directory of
edk2\ShellBinPkg\UefiShell\Arm\Shell.efi
when i boot to the shell, the uart console print information like below:
Loading driver at 0x000BB914000 EntryPoint=0x000BB95A389 Shel
Dell - Internal Use - Confidential
Hi Michael,
My intention is to write some data in Disk using UEFI application.
To achieve this how I have to modify my code ?
Regards
Parmeshwr
From: Kinney, Michael D [mailto:michael.d.kin...@intel.com]
Sent: Thursday, October 17, 2013 9:48 PM
To: edk2-devel@li
Thanks Jaben. Can we send our application source and is it possible to check it
on your side? Or is there any other way that we can prove, Shell is not reading
the key when the application is active?.
Thanks,
Ramesh
-Original Message-
From: Carsey, Jaben [mailto:jaben.car...@intel.com]
Hi Parmeshwr,
Do you need to write the data into all the DISK ? If so
Use LocateHandleBuffer to get all the DiskIO handle and use the HandleProtocol
on each handle to get the DiskIO protocol.
Thanks,
Ramesh
From: parmeshwr_pra...@dell.com [mailto:parmeshwr_pra...@dell.com]
Sent: Friday, Oct
Dell - Internal Use - Confidential
Hi Ramesh,
This much I did but problem occurred when I do openprotocol with BY_DRIVER so
it gives error.
Regards
Param
From: Ramesh R. [mailto:rame...@ami.com]
Sent: Friday, October 18, 2013 10:24 AM
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] prob
Please be aware that it would be better to use SafeOpenPotocol lib if the
DiskIo is installed at the device which could be hot-plugged.
From: Ramesh R. [mailto:rame...@ami.com]
Sent: Friday, October 18, 2013 12:54
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] problem in openprotocol
H
Like Mike said: The BY_DRIVER open mode is a request to open the protocol and
then prevent other drivers from opening the same protocol.
So you met the error as other driver has opened DiskIo with BY_DRIVER.
From: parmeshwr_pra...@dell.com [mailto:parmeshwr_pra...@dell.com]
Sent: Friday, October
Please check the partition driver. It does the BY_DRIVER attribute for the
DISKIO protocol. So from application if you try BY_DRIVER again , it would
return access denied error.
Status = gBS->OpenProtocol (
ControllerHandle,
&gEfiDiskIoProtocolGuid,
Agree. It's a good point. But OpenProtocol with BY_DRIVER attribute is not
possible from application as other BIOS driver already opened the DISKIO
protocol using the BY_DRIVER attribute. The application should take care of the
handling of the Hot Pluggable devices.
Thanks,
Ramesh
From: Tian,
Right. For his case, I only could think out a way, that is raise & restore tpl
to CALLBACK level to prevent hot-plug event happen on critical region. This way
could protect BlockIo/DiskIo interface from being released and avoid hang.
Here I have an assumption that all UEFI implementations on han
Dell - Internal Use - Confidential
How to get right value for EFI_LBA ?
From: Tian, Feng [mailto:feng.t...@intel.com]
Sent: Friday, October 18, 2013 11:48 AM
To: edk2-devel@lists.sourceforge.net; Andrew Fish (af...@apple.com)
Subject: Re: [edk2] problem in openprotocol
Right. For his case, I only
Agree. We need to consider the USB devices also as they work based on SMI's.
Thanks,
Ramesh
From: Tian, Feng [mailto:feng.t...@intel.com]
Sent: Friday, October 18, 2013 11:48 AM
To: edk2-devel@lists.sourceforge.net; Andrew Fish (af...@apple.com)
Subject: Re: [edk2] problem in openprotocol
Right.
Hi,
I am writing an application in EDK II and for the given snippet of code, i
get the error
error LNK2001: unresolved external symbol _ModuleEntryPoint :-
#ifdef EFI_BOOTSHELL
EFI_APPLICATION_ENTRY_POINT(EfiFlashMain)
#endif
However, _ModuleEntryPoint is not used anywhere in the program.
Also,
What do you mean by "right value for EFI_LAB"? You should know which LAB you
are going to write the data.
Thanks,
Ramesh
From: parmeshwr_pra...@dell.com [mailto:parmeshwr_pra...@dell.com]
Sent: Friday, October 18, 2013 11:53 AM
To: edk2-devel@lists.sourceforge.net; af...@apple.com
Subject: Re:
Sorry,
the code snippet i meant to mention (which gives error) was
#ifdef EFI_BOOTSHELL
EFI_APPLICATION_ENTRY_POINT(EfiFlashMain)
#endif
FI_STATUS
EFIAPI
EfiFlashMain (
IN EFI_HANDLE ImageHandle,
IN EFI_SYSTEM_TABLE *SystemTable
)
This is the snippet which works fine,
#ifdef EF
30 matches
Mail list logo
