#include <Library/PcdLib.h>\r
#include <Library/DevicePathLib.h>\r
#include <Library/MemoryAllocationLib.h>\r
-\r
+#include <Library/HiiLib.h>\r
#include <Library/BdsLib.h>\r
+#include <Library/ShellLib.h>\r
\r
+#include <Protocol/DevicePathToText.h>\r
#include <Protocol/DevicePathFromText.h>\r
#include <Protocol/DevicePath.h>\r
+#include <Protocol/EfiShell.h>\r
+#include <Protocol/EfiShellDynamicCommand.h>\r
\r
#include <Guid/EventGroup.h>\r
#include <Guid/Fdt.h>\r
//\r
// Internal types\r
//\r
+\r
STATIC VOID OnEndOfDxe (\r
IN EFI_EVENT Event,\r
IN VOID *Context\r
IN CONST CHAR16* TextDevicePath\r
);\r
\r
+STATIC SHELL_STATUS EFIAPI ShellDynCmdSetFdtHandler (\r
+ IN EFI_SHELL_DYNAMIC_COMMAND_PROTOCOL *This,\r
+ IN EFI_SYSTEM_TABLE *SystemTable,\r
+ IN EFI_SHELL_PARAMETERS_PROTOCOL *ShellParameters,\r
+ IN EFI_SHELL_PROTOCOL *Shell\r
+ );\r
+\r
+STATIC CHAR16* EFIAPI ShellDynCmdSetFdtGetHelp (\r
+ IN EFI_SHELL_DYNAMIC_COMMAND_PROTOCOL *This,\r
+ IN CONST CHAR8 *Language\r
+ );\r
+\r
+STATIC SHELL_STATUS UpdateFdtTextDevicePath (\r
+ IN EFI_SHELL_PROTOCOL *Shell,\r
+ IN CONST CHAR16 *FilePath\r
+ );\r
+\r
+STATIC SHELL_STATUS EfiCodeToShellCode (\r
+ IN EFI_STATUS Status\r
+ );\r
+\r
+//\r
+// Internal variables\r
+//\r
+\r
+STATIC CONST EFI_SHELL_DYNAMIC_COMMAND_PROTOCOL mShellDynCmdProtocolSetFdt = {\r
+ L"setfdt", // Name of the command\r
+ ShellDynCmdSetFdtHandler, // Handler\r
+ ShellDynCmdSetFdtGetHelp // GetHelp\r
+};\r
+\r
+STATIC CONST EFI_GUID mFdtPlatformDxeHiiGuid = {\r
+ 0x8afa7610, 0x62b1, 0x46aa,\r
+ {0xb5, 0x34, 0xc3, 0xde, 0xff, 0x39, 0x77, 0x8c}\r
+ };\r
+STATIC CONST SHELL_PARAM_ITEM ParamList[] = {\r
+ {L"-i", TypeFlag },\r
+ {NULL , TypeMax }\r
+};\r
+\r
+STATIC EFI_HANDLE mFdtPlatformDxeHiiHandle;\r
+\r
/**\r
Main entry point of the FDT platform driver.\r
\r
@param[in] *SystemTable A pointer to the EFI System table.\r
\r
@retval EFI_SUCCESS The driver was initialized.\r
- @retval EFI_OUT_OF_RESOURCES The "End of DXE" event could not be allocated.\r
+ @retval EFI_OUT_OF_RESOURCES The "End of DXE" event could not be allocated or\r
+ there was not enough memory in pool to install\r
+ the Shell Dynamic Command protocol.\r
+ @retval EFI_LOAD_ERROR Unable to add the HII package.\r
\r
**/\r
EFI_STATUS\r
&EndOfDxeEvent\r
);\r
\r
+ if (EFI_ERROR (Status)) {\r
+ return Status;\r
+ }\r
+\r
+ //\r
+ // If the development features are enabled, install the dynamic shell\r
+ // command "setfdt" to be able to define a device path for the FDT\r
+ // that has precedence over the device paths defined by\r
+ // "PcdFdtDevicePaths".\r
+ //\r
+\r
+ if (FeaturePcdGet (PcdOverridePlatformFdt)) {\r
+ //\r
+ // Register the strings for the user interface in the HII Database.\r
+ // This shows the way to the multi-language support, even if\r
+ // only the English language is actually supported. The strings to register\r
+ // are stored in the "FdtPlatformDxeStrings[]" array. This array is\r
+ // built by the building process from the "*.uni" file associated to\r
+ // the present driver (cf. FdtPlatfromDxe.inf). Examine your Build\r
+ // folder under your package's DEBUG folder and you will find the array\r
+ // defined in a xxxStrDefs.h file.\r
+ //\r
+ mFdtPlatformDxeHiiHandle = HiiAddPackages (\r
+ &mFdtPlatformDxeHiiGuid,\r
+ ImageHandle,\r
+ FdtPlatformDxeStrings,\r
+ NULL\r
+ );\r
+\r
+ if (mFdtPlatformDxeHiiHandle != NULL) {\r
+ Status = gBS->InstallMultipleProtocolInterfaces (\r
+ &ImageHandle,\r
+ &gEfiShellDynamicCommandProtocolGuid,\r
+ &mShellDynCmdProtocolSetFdt,\r
+ NULL\r
+ );\r
+ if (EFI_ERROR (Status)) {\r
+ HiiRemovePackages (mFdtPlatformDxeHiiHandle);\r
+ }\r
+ } else {\r
+ Status = EFI_LOAD_ERROR;\r
+ }\r
+ if (EFI_ERROR (Status)) {\r
+ DEBUG ((\r
+ EFI_D_WARN,\r
+ "Unable to install \"setfdt\" EFI Shell command - %r \n",\r
+ Status\r
+ ));\r
+ }\r
+ }\r
+\r
return Status;\r
}\r
\r
return Status;\r
}\r
\r
-=======\r
-\r
/**\r
This is the shell command "setfdt" handler function. This function handles\r
the command when it is invoked in the shell.\r
\r
return ShellStatus;\r
}\r
->>>>>>> 4ac4fed... EmbeddedPkg/FdtPlatformDxe: Fix typo issue\r
The purpose of the FdtPlatformDxe UEFI driver is to install the Flat Device
Tree (FDT) of the platform the UEFI frimware is running on into the UEFI
Configuration Table. The FDT is identified within the UEFI Configuration
-Table by the "gFdtTableGuid" GUID defined in EmbeddedPkg.dec.
+Table by the "gFdtTableGuid" GUID defined in "EmbeddedPkg.dec".
Once installed, an UEFI application or OS boot loader can get from the UEFI
Configuration Table the FDT of the platform from the "gFdtTableGuid" GUID.
"Fdt". If the variable does not exist or the installation using the device path
defined by the UEFI variable fails then the installation proceeds as described
above.
+
+Furthermore and again for development purposes only, if the feature PCD
+"PcdOverridePlatformFdt" is equal to TRUE, the current driver provides the EFI
+Shell command "setfdt" to define the location of the FDT by the mean of an EFI
+Shell file path (like "fs2:\boot\fdt.dtb") or a device path.
+
+If the path passed in to the command is a valid EFI Shell file path, the
+command translates it into the corresponding device path and stores that
+device path in the "Fdt" UEFI variable asking for the variable to be non
+volatile.
+
+If the path passed in to the command is not recognised as a valid EFI
+Shell device path, the command handles it as device path and stored
+in the "Fdt" UEFI variable as it is.
+
+Finally, the "-i" option of the "setfdt" command allows to trigger the FDT
+installation process. The installation process is completed when the command
+returns. The command can be invoked with the "-i" option only and in that
+case the "Fdt" UEFI variable is not updated and the command just runs the
+FDT installation process. If the command is invoked with the "-i" option and
+an EFI Shell file path then first the "Fdt" UEFI variable is updated accordingly
+and then the FDT installation process is run.
projects / mirror_edk2.git / commitdiff