aboutsummaryrefslogtreecommitdiff
path: root/src/include/ipxe/efi
diff options
context:
space:
mode:
authorMichael Brown <mcb30@ipxe.org>2020-09-29 21:13:10 +0100
committerMichael Brown <mcb30@ipxe.org>2020-09-29 21:21:04 +0100
commit8344803c934c71c7eebb6b706d73a8c00d57b713 (patch)
tree99c76a10d605635eeba536def8e9b1efd41d9682 /src/include/ipxe/efi
parent8eb19a178a5d6ca89ca2b8200dae0f7cec15ae2c (diff)
downloadipxe-8344803c934c71c7eebb6b706d73a8c00d57b713.zip
ipxe-8344803c934c71c7eebb6b706d73a8c00d57b713.tar.gz
ipxe-8344803c934c71c7eebb6b706d73a8c00d57b713.tar.bz2
[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/include/ipxe/efi')
0 files changed, 0 insertions, 0 deletions