Keyboard input support from Bitlocker login

[tomjohnstone]

It would be nice to be able to use my keyboard from the Bitlocker login screen, just after the bios screen. I can plug a keyboard in and it will work on this screen, but I can't switch over from my other machine. I wonder if this is due to caps lock being re-mapped to F24 in the new RC and not being able to switch via the keyboard, since there is no mouse support on the Bitlocker login screen edit: I confirmed that caps lock does not work either. That said when I try to move the mouse from my other machine (A), the light for machine (B) on the Deskhop does illuminate.

Setup:
Machine A is primary machine with mouse & keyboard connected via USB hub to keyboard USB port on Deskhop
Machine B has BitLocker

[tomjohnstone]

I also tried disabling fast boot mode, but that didn't work either:

https://answers.microsoft.com/en-us/windows/forum/all/keyboard-not-working-in-bitlocker/fda262a6-ed41-403e-a423-7a19305b22ef

[hrvach]

I think I know what might work - a dedicated endpoint for the keyboard without using report ID. Maybe try that? Or build it without the mouse support and don't send report ID just for test and tell me if it works...

I'm sure there is some way we could make a workaround for such small / embedded environments.

[tomjohnstone]

Sure thing, I'm unfamiliar with HID so if you can point me in the right direction I can take a look at coding up either of those options to experiment with. Thanks!

[tomjohnstone]

This is my attempt so far at option 1. It is not registering any input from neither the keyboard or mouse however:

https://github.com/tomjohnstone/deskhop/pull/2/files

[hrvach]

I think adding a tud_hid_set_protocol_cb callback and detecting if protocol is HID_PROTOCOL_BOOT, and then stripping the ID in this case for keyboard reports and disabling other reports would be a quick'n'dirty workaround.

[tomjohnstone]

tud_hid_set_protocol_cb only receives an instance and protocol. Where do I get at the ID to strip it, from this callback?

[hrvach]

@tomjohnstone you don't need to know the ID to strip it, I think just setting it to 0 would suffice for tinyusb. I'm working on this, we definitely need proper boot protocol support as a client and I hope to have something ready soon. Just have to find something to test on...

[tomjohnstone]

Would your bios be a good testing ground? When you get something working I'm happy to test on my Bitlocker login too. Cheers!