Timeline for Usb keyboard use separately in X
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 11:33 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Mar 2, 2017 at 11:19 | vote | accept | johnfound | ||
| Feb 8, 2017 at 7:57 | history | edited | dirkt | CC BY-SA 3.0 |
Fix typo.
|
| Feb 7, 2017 at 10:58 | comment | added | dirkt |
See edit for permissions. /dev/stdin is just a symlink to the first file descriptor of the process (have a look with ls -l). I'm not sure about the details how the kernel keymapping works, but I assume it's tied to the current virtual console, and it wouldn't be possible to use another one without using a fresh virtual console. That means a lot of overhead, and also your display would switch. I don't think you can just attach it to a pseudo tty somehow, though that would be a cool thing to do.
|
|
| Feb 7, 2017 at 10:55 | history | edited | dirkt | CC BY-SA 3.0 |
Setting permissions
|
| Feb 7, 2017 at 9:44 | comment | added | johnfound | "such devices don't exist in the Linux kernel" Maybe I am wording wrong. I mean, the kernel can decode scan codes into ascii chars - this way are created /dev/stdin and /dev/console when there is no X running. Isn't it possible to configure such ascii device instead of manually reading the event devices? Also, how to configure the access? Now all these devices need root access. | |
| Feb 7, 2017 at 9:22 | history | answered | dirkt | CC BY-SA 3.0 |