Timeline for How does a keyboard press get processed in the Linux Kernel?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 1, 2020 at 11:47 | comment | added | dirkt | @DeclanNnadozie: Try that yourself: run evtest /dev/input/... in two terminals, with the path to your keyboard. Then try again with the --grab option. | |
| Jun 1, 2020 at 9:30 | comment | added | Declan Nnadozie | @dirkt what if multiple process made direct read system call to keyboard without use of X server logic, how does the kernel service all of them. Does it copy the bytes to all blocked processes? Or Does it return "NOT AVAILABLE" to all subsequent read system calls | |
| Apr 13, 2020 at 5:29 | history | edited | G-Man Says 'Reinstate Monica' | CC BY-SA 4.0 | Editorial changes. |
| S Apr 12, 2020 at 22:51 | history | suggested | Gab是好人 | CC BY-SA 4.0 | typo fix and improve readability |
| Apr 12, 2020 at 21:22 | review | Suggested edits | |||
| S Apr 12, 2020 at 22:51 | |||||
| Apr 12, 2020 at 10:24 | comment | added | dirkt | @tritium_3: About 25 years of using Linux, curiosity, and the ability to google and read. And I learned about X before that ... | |
| Apr 12, 2020 at 9:22 | comment | added | tritium_3 | Very interesting explanation. Where did you learn all of this? What is your background? | |
| Oct 6, 2019 at 11:46 | vote | accept | Sean | ||
| Oct 5, 2019 at 17:56 | history | answered | dirkt | CC BY-SA 4.0 |