Pass through all the devices#41
Conversation
If you mess up the config on the first run you're left with a broken gadget and future runs fail
Should avoid getting into the situation fixed by the previous commit
The duplication was annoying me, also reduce to one line
Should probably check if it's executable too, but this gets rid of the file not found errors
No idea how correct this is, but it seems to find the right thing
There seems to be a limit of 4 in the kernel
|
This is beautifully awesome. Thank you! Time to dig up a Pi 400 👀 I have a suspicion the keyboard's dual devices are the keyboard itself - probably regular boot protocol - plus a separate media keys device. I guess the keyboard controller is pretty turnkey, so it made no sense for the Pi 400 to diverge away from it. (Though I suspect just because I can't imagine why a Pi 400 would ever need a boot compatible keyboard, doesn't mean there isn't a reason.) |
|
Fired up a Pi 400, remembered to follow my own instructions, got it up and running, and it just goes BOOP BEEP BOOP and grabs all the things and just works. Slightly less success with my 8bitdo ultimate controller (2.4GHz/USB HID), but it's the K(v)M that matters. Very, very nice. |
|
Merge? |
|
This is wonderful. Would love a merge! |
|
Thanks @Daft-Freak for making this, I merged the main branch and compiled it, and it works great with a wired mouse and a Linux host. Unfortunately, the mouse driver does not work on Windows, it shows up in Device Manager, but the driver fails to start with code 10. The keyboard works fine on Windows. |
... well, up to four because of kernel limit on HID functions.
Ended up looking at this more than I intended to, so there are a bunch of changes here.
Currently this introduces a few new issues: