aboutsummaryrefslogtreecommitdiff
path: root/marsond.rst
diff options
context:
space:
mode:
Diffstat (limited to 'marsond.rst')
-rw-r--r--marsond.rst37
1 files changed, 31 insertions, 6 deletions
diff --git a/marsond.rst b/marsond.rst
index ce0e102..e094d44 100644
--- a/marsond.rst
+++ b/marsond.rst
@@ -102,6 +102,9 @@ MARSOND_GROUP
NOTES
=====
+Hardware
+--------
+
The problem happens with any SDL application (SDL1 or SDL2), as well
as other graphics libraries. It happens regardless of what PS/2
keyboard you have plugged in, what computer you have the adaptor
@@ -116,9 +119,22 @@ the back, the model number is "MT606-1". It looks like:
https://slackware.uk/~urchlay/sdl-usblink-hack/marson-back.jpg
-I'm not sure if any other USB keyboard adaptors are affected. If you
-have the problem on some other adaptor, and **marsond** fixes it,
-please contact me so I can add support for it in the future.
+Confusingly enough, in **lsusb**\(8) output, it shows up as::
+
+ $ lsusb | grep 04b4:0101
+ Bus 003 Device 006: ID 04b4:0101 Cypress Semiconductor Corp. Keyboard/Hub
+
+The Bus and Device numbers may be different for you, it's the ID and
+name that are important.
+
+I'm not sure if any other USB keyboard adaptors are affected. If
+you have the problem on some other adaptor, try it with **marsond**.
+Use the **-k** option to set the */dev/input/by-id* name of the device,
+and run the daemon manually. If this fixes it please contact me so I
+can add support for your adaptor in the future.
+
+Implementation
+--------------
**marsond** uses the Linux kernel's **uinput** layer to "grab" the
keyboard, create a new virtual keyboard device, and pass events from
@@ -128,8 +144,12 @@ before delivering it.
This should work with everything that uses the keyboard. It definitely
does, with SDL 1 and 2 running under X (and SDL 1 on the console,
-too). I don't use Wayland, so I haven't tested it there. If you do,
-please contact me and let me know if it works for you.
+too). It should also work with Wayland, though I don't use Wayland,
+so I haven't tested it there. If you do, please contact me and let me
+know whether or not it works for you.
+
+Startup
+-------
**marsond** must be run as root. At startup, it does these
things as root:
@@ -147,8 +167,13 @@ After doing the above, root access is no longer needed, so it will
drop privileges and run as the *nobody* user by default (but see
**ENVIRONMENT** if you need a different user).
+Misc
+----
+
While **marsond** is running, "xinput --list" will show an input
-device called "marson virtual keyboard".
+device called "marson virtual keyboard". Confusingly enough, it will
+show up as both a pointer and a keyboard. This doesn't seem to hurt
+anything, but it looks weird, doesn't it?
LIMITATIONS
===========