Tim,
I'm sure that it the requirement were added to the UEFI Shell specification it
would soon appear in the code.
I don't work on the UEFI Shell so I can't say what may or may not happen in the
future.
Technically, your suggestion is feasible. This is similar to what is planned
for StdLib.
Daryl - If the shell is launched from a device that has a mapping, could we set
CWD to something other than nothing? For example, the location where
startup.nsh is located?
Tim
From: Mcdaniel, Daryl [mailto:daryl.mcdan...@intel.com]
Sent: Tuesday, July 02, 2013 10:48 AM
To: ritul guru (riguru);
This error is produced by the OLD EFI toolkit.
It results because the current working directory is not set. The ASSERT is
triggered specifically because CWD does not contain a ':'.
Within either the EFI or UEFI shells, CWD is not set until after the first time
one explicitly sets it. For examp
Thank you for the answers :)
2013/6/30 Tian, Feng
> DataHub has been deprecated. PI spec has removed it.
>
> ** **
>
> ReportStatusCode() could have many different implementations or be
> outputted to different “channels”, such as serial port, port80, datahub and
> so on.
>
> ** **
>
>
There are sample implements under edk2\IntelFrameworkModulePkg\Csm\BiosThunk
you can refer to that use legacy int calls for providing UEFI standard protocol
interfaces.
-Mars
From: ritul guru (riguru) [mailto:rig...@cisco.com]
Sent: Tuesday, July 02, 2013 7:18 PM
To: edk2-devel@lists.sourceforge
Hi,
As legacy devices can't be served by uefi drivers. So BIOS may end up providing
2 different versions of drivers
1. On for legacy devices
2. Other for uefi supported devices
Is there any way to make uefi driver work for legacy devices? By writing some
kind of wrapper around uefi dri
