Support boot-protocol keyboard for UEFI/BitLocker pre-boot - #356
Open
mglushko wants to merge 1 commit into
Open
Conversation
Present the keyboard interface as a boot keyboard (subclass=Boot, protocol=Keyboard) so UEFI/BIOS pre-boot environments (e.g. BitLocker PIN entry) recognize it. When the host selects boot protocol, send the plain 8-byte boot keyboard report with no report ID, and drop absolute-mouse and consumer/system report-ID reports on that interface so they are not misread as keystrokes. Normal OS operation (report protocol) is unchanged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Present the keyboard interface as a boot keyboard (subclass=Boot, protocol=Keyboard) so UEFI/BIOS pre-boot environments (e.g. BitLocker PIN entry) recognize it. When the host selects boot protocol, send the plain 8-byte boot keyboard report with no report ID, and drop absolute-mouse and consumer/system report-ID reports on that interface so they are not misread as keystrokes. Normal OS operation (report protocol) is unchanged.
I was having this same issue on my work laptop, and this seems to work for me. Hopefully resolves #122.