Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

investigate endpoint 1 requirement for boot keyboards #1306

Open
tlyu opened this issue Nov 8, 2022 · 0 comments
Open

investigate endpoint 1 requirement for boot keyboards #1306

tlyu opened this issue Nov 8, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@tlyu
Copy link
Collaborator

tlyu commented Nov 8, 2022

Describe the bug

There are some reports that even in 2021, PC vendors have BIOSes that require IN 1 (and possibly OUT 1) endpoint(s) in order to recognize a Boot Keyboard. (There are also reports that it's required to be Interface 0, but the evidence seems less reliable on that.)

It's not clear whether OUT 1 is required. An interrupt out endpoint isn't required by either the HID specification in general or the Boot Keyboard specification. I haven't yet seen any evidence that any KVMs or BIOSes actually require a functioning OUT 1 endpoint for LED Output Reports, as opposed to using a Set Report control request.

To Reproduce

Details are unknown. We could experiment with forcing an endpoint of IN 1 for the Boot Keyboard to see if that helps any of the reported problems with KVM or BIOS compatibility. Note that forcing endpoint numbers is likely impossible on AVR without patching the Arduino core, which I'm guessing we've been avoiding.

Additional information

espressif/arduino-esp32#6964

@tlyu tlyu added the bug Something isn't working label Nov 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant