Salastil/ckb-next
1
0
Fork 0
mirror of https://github.com/ckb-next/ckb-next.git synced 2026-10-10 12:27:21 -04:00
Code Issues Packages Projects Releases Wiki Activity

Correct some typos in DAEMON.md

Browse Source
This commit is contained in:
Lutz Eichler
2017-06-17 13:35:18 +02:00
parent 793fe1221f
commit 8296895c9d
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
DAEMON.md
+4 -2
View File
@@ -9,11 +9,13 @@ The daemon provides devices at `/dev/input/ckb*`, where * is the device number,
Other `ckb*` devices contain the following:
- `cmd`: Keyboard controller.
- `notify0`: Keyboard notifications.
- `notify0`: Keyboard- or mouse notifications.
- `notify1`: Keyboard- or mouse notifications, useed for macro recording.
- `features`: Device features.
- `fwversion`: Device firmware version (not present on all devices).
- `model`: Device description/model.
- `pollrate`: Poll rate in milliseconds (not present on all devices).
- `productid`: Contains the USB productID of the hardware
- `serial`: Device serial number. `model` and `serial` will match the info found in `ckb0/connected`
Commands
@@ -238,7 +240,7 @@ Restart
-------
Because sometimes the communication between the daemon and the keyboard is corrupted after resuming from standby or suspend, a restart function is implemented.
It first calls the quit() funtion, then it calls main() again with the original parameter list.
It first calls the quit() function, then it calls main() again with the original parameter list.
There are two ways to restart the daemon:
- send the string "restart some-description-as-one-word" to the cmd-pipe (normally /dev/input/ckb1/cmd or /dev/input/ckb2/cmd, depending on what device gets which ID.