31.3.1 Testing Specific Protocols

The following table lists Shell commands that might be useful in testing specific protocols.

Table 40-UEFI Shell commands

Command

Protocol tested

Service tested

Load -nc

Driver entry point.

Driver Binding

Supported()

Load

Driver entry point.

Driver Binding

Supported()

Driver Binding

Start()

Unload

Loaded Image

Unload()

Connect

Driver Binding

Supported()

Driver Binding

Start()

Disconnect

Driver Binding

Stop(). Note: The UEFI driver must specifically disconnect (destroy) all child handles and device paths associated with the handle for the driver being stopped.

Reconnect

Driver Binding

Supported()

Driver Binding

Start()

Driver Binding

Stop()

Drivers

Component Name and Component Name2

GetDriverName()

Devices

Component Name and Component Name2

GetDriverName()

GetControllerName()

DevTree

Component Name and Component Name2

GetControllerName()

Dh -d

Component Name and Component Name2

GetDriverName()

GetControllerName()

DrvCfg -s

Driver Configuration and Driver Configuration 2

This command used to test the SetOptions() service. These protocols are supported by EFI 1.10 and UEFI 2.0.

DrvCfg -f

Driver Configuration and Driver Configuration 2

This command used to test the

ForceDefaults() service. These protocols are supported by EFI 1.10 and UEFI 2.0.

DrvCfg -v

Driver Configuration and Driver Configuration 2

This command used to test the OptionsValid() service. These protocols are supported by EFI 1.10 and UEFI 2.0.

DrvDiag

Driver Diagnostics and Driver Diagnostics2

RunDiagnostics()