mirror of https://github.com/ipxe/ipxe.git
[efi] Prefer driver name to device path for debug messages
The driver name is usually more informative for debug messages than the device path from which a driver was loaded. Try using the various mechanisms for obtaining a driver name before trying the device path. Signed-off-by: Michael Brown <mcb30@ipxe.org>pull/1193/merge
parent
7cda3dbf94
commit
5d64469a9e
|
@ -623,9 +623,6 @@ struct efi_handle_name_type {
|
||||||
|
|
||||||
/** EFI handle name types */
|
/** EFI handle name types */
|
||||||
static struct efi_handle_name_type efi_handle_name_types[] = {
|
static struct efi_handle_name_type efi_handle_name_types[] = {
|
||||||
/* Device path */
|
|
||||||
EFI_HANDLE_NAME_TYPE ( &efi_device_path_protocol_guid,
|
|
||||||
efi_devpath_text ),
|
|
||||||
/* Driver name (for driver image handles) */
|
/* Driver name (for driver image handles) */
|
||||||
EFI_HANDLE_NAME_TYPE ( &efi_component_name2_protocol_guid,
|
EFI_HANDLE_NAME_TYPE ( &efi_component_name2_protocol_guid,
|
||||||
efi_driver_name2 ),
|
efi_driver_name2 ),
|
||||||
|
@ -650,6 +647,9 @@ static struct efi_handle_name_type efi_handle_name_types[] = {
|
||||||
/* Handle's loaded image file path (for image handles) */
|
/* Handle's loaded image file path (for image handles) */
|
||||||
EFI_HANDLE_NAME_TYPE ( &efi_loaded_image_protocol_guid,
|
EFI_HANDLE_NAME_TYPE ( &efi_loaded_image_protocol_guid,
|
||||||
efi_loaded_image_filepath_name ),
|
efi_loaded_image_filepath_name ),
|
||||||
|
/* Device path */
|
||||||
|
EFI_HANDLE_NAME_TYPE ( &efi_device_path_protocol_guid,
|
||||||
|
efi_devpath_text ),
|
||||||
/* Our standard input file handle */
|
/* Our standard input file handle */
|
||||||
EFI_HANDLE_NAME_TYPE ( &efi_simple_text_input_protocol_guid,
|
EFI_HANDLE_NAME_TYPE ( &efi_simple_text_input_protocol_guid,
|
||||||
efi_conin_name ),
|
efi_conin_name ),
|
||||||
|
|
Loading…
Reference in New Issue