diff options
| author | Michael Brown | 2020-09-29 22:13:10 +0200 |
|---|---|---|
| committer | Michael Brown | 2020-09-29 22:21:04 +0200 |
| commit | 8344803c934c71c7eebb6b706d73a8c00d57b713 (patch) | |
| tree | 99c76a10d605635eeba536def8e9b1efd41d9682 /src/interface/linux | |
| parent | [usb] Show debug message on device removal (diff) | |
| download | ipxe-8344803c934c71c7eebb6b706d73a8c00d57b713.tar.gz ipxe-8344803c934c71c7eebb6b706d73a8c00d57b713.tar.xz ipxe-8344803c934c71c7eebb6b706d73a8c00d57b713.zip | |
[efi] Disconnect controllers before uninstalling EFI_USB_IO_PROTOCOL
The call to UninstallMultipleProtocolInterfaces() will implicitly
disconnect any relevant controllers, and there is no specified
requirement to explicitly call DisconnectController() prior to
callling UninstallMultipleProtocolInterfaces().
However, some UEFI implementations (observed with the USB keyboard
driver on a Microsoft Surface Go) will fail to implicitly disconnect
the controller and will consequently fail to uninstall the protocols.
The net effect is that unplugging and replugging a USB keyboard may
leave the keyboard in a non-functional state.
Work around these broken UEFI implementations by including an
unnecessary call to DisconnectController() before the call to
UninstallMultipleProtocolInterfaces().
Signed-off-by: Michael Brown <mcb30@ipxe.org>
Diffstat (limited to 'src/interface/linux')
0 files changed, 0 insertions, 0 deletions