You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 18, 2021. It is now read-only.
So,
Somehow I inserted the module and registered it,
But the statement where I believe the keycode of the key pressed should be printed
it's always printed as "key press is 164". What does it mean?
And also is the file in usb-part the complete driver or the files outside are required too?
Also can you explain this structure.
By what I understand it's supposed to be a mapping but I don't understand it.
Please reply as fast as you can.
And also thank you for uploading this project.
The text was updated successfully, but these errors were encountered:
I'm so sorry for this delay which at this point should be considered as an act of terrorism. I've shifted away from GitHub as my Job just doesn't allow us to use GitHub.
So I was thinking If you want to take the ownership of this I wouldn't mind.
At this point I forget what 164 was but i think I also faced this problem and this was maybe escape key.
Yes this was the mapping but this is not the ASCII mapping but some other Unicode.
To run this I just copied the file from linux kernel source code from https://www.kernel.org/
And that did the work for me.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
So,
Somehow I inserted the module and registered it,
But the statement where I believe the keycode of the key pressed should be printed
it's always printed as "key press is 164". What does it mean?
And also is the file in usb-part the complete driver or the files outside are required too?
Also can you explain this structure.
By what I understand it's supposed to be a mapping but I don't understand it.
Please reply as fast as you can.
And also thank you for uploading this project.
The text was updated successfully, but these errors were encountered: