Re: mouseemu 0.15 not working at all?
> > No, that's not what I said. Usually mouseemu 'steals' the events. mouseemu
> > not getting any events at all does point to the kernel as likely culprit,
> > IMHO.
>
> so what should be activated in the kernel in addition to
> CONFIG_INPUT_UINPUT=[y|m] (the only option i found that was necessary).
CONFIG_INPUT_EVDEV, obviously.
> > Regarding other apps receiving events, see my suggestion to search /proc
> > for any occurrences of 'event' files. Any process opening some event
> > device will have a file /proc/<pid>/fd/event%d showing in /proc.
>
> ls /proc/*/fd does not show any event%d files only symlinks
Just great. If you stop for a moment and examine any arbitrary process's
fd directory you'll notice it's always symlinks. s/file/entry/ above if
you like. Now which are the processes that have symlinks containing
'event' in their fd set?
> in earlier postings in debian-powerpc, i have found something like
> /proc/input/devices. the input directory does not exist on my mac.
>
> > To see which events are processed by the kernel, load the evbug module and
> > watch /var/log/debug
>
> ok, moving the mouse produces something like ...
>
> event. dev: adb3:3.01/input, type: 2, code: 1, value -1
So far so good. In theory, the output should change somewhat after
starting mouseemu - all the adb3:3.01/input stuff should be replaced by
<NULL>, for instance (that's mouseemu's virtual keyboard and mouse
injecting the events back into the system). (Note that you can figure out
the event codes for the emulation keys from the evbug output when mouseemu
is not running - just to double check your configuration.)
If the output does not change after starting mouseemu, something in the
device open code of mouseemu fails (I doubt it, though).
Look through the debug log to find the spot where the evbug module loads -
it reports all registered event devices with name and device name. You
should find all keyboard, mouse and button devices listed there, plus a
few odd ones.
Michael
Reply to: