Re: pbbuttonsd beta on new Powerbook5,8
Hello Matthias,
[writing this mail a second time, powerbook went to sleep and crashed on
wake while replying. Arghhh...]
On 22 Jan, this message from Matthias Grimm echoed through cyberspace:
> There are a couple of applications fiddle around with /dev/input/event
> so I try to bring some light into it.
Thanks a lot for that, it helped tremendously.
> Udev is responsible for creating an /dev/input/event% device for each
> HID. Udev is the most comfortable way to have up-to-date devices
> in /dev. If you don't have udev running, be sure that each HID is
> represented by an event devive in /dev/input/.
udev disabled here, and all 32 event devices exist in the statuc /dev.
> Pbbuttonsd opens all /dev/input/event% devices and uses them for input
> (at least to reset the user idle timer). If autorescan = yes
Checked, I have that.
> devices will be automatically added or
> removed as soon as they appear or vanish.
That doesn't seem to work. Input devices with mouseemu stopped:
/sys/class/input/input5/name: Apple Computer Apple Internal Keyboard / Trackpad
/sys/class/input/input5/event2
/sys/class/input/input6/name: appletouch
/sys/class/input/input6/event3
/sys/class/input/input7/name: Apple Computer Apple Internal Keyboard / Trackpad
/sys/class/input/input7/event4
/sys/class/input/input8/name: HID 05ac:1000
/sys/class/input/input8/event0
/sys/class/input/input9/name: HID 05ac:1000
/sys/class/input/input9/event1
pbbuttonsd opens event0 and event2 only. X has event3 and mice open.
With mouseemu running, I have these devices:
/sys/class/input/input26/name: Mouseemu virtual keyboard
/sys/class/input/input26/event5
/sys/class/input/input27/name: Mouseemu virtual mouse
/sys/class/input/input27/event6
/sys/class/input/input5/name: Apple Computer Apple Internal Keyboard / Trackpad
/sys/class/input/input5/event2
/sys/class/input/input6/name: appletouch
/sys/class/input/input6/event3
/sys/class/input/input7/name: Apple Computer Apple Internal Keyboard / Trackpad
/sys/class/input/input7/event4
/sys/class/input/input8/name: HID 05ac:1000
/sys/class/input/input8/event0
/sys/class/input/input9/name: HID 05ac:1000
/sys/class/input/input9/event1
mouseemu has event0, event1 and event2 open, as well as uinput (two times).
However, pbbuttonsd does _not_ seem to reopen any devices, in particular
after a few minutes it still hasn't opened the uinput event devices.
After booting the powerbook again (tomorrow) I need to check whether
stopping/starting pbbuttonsd makes it open the uinput event devices.
> Mouseemu exclusively locks all input devices related to mice for full
> control. After that it routes the mouse events through a newly created
> input device (or two of them). This way it can filter out unwanted
> mouse events or create new ones. Pbbuttonsd can't access the locked
> event devices anymore but it uses the newly created uinput devices
> instead. You won't see any difference in behaviour.
So no problem to be expected here, is there? And pbbuttonsd should be
able to detect buttons 2&3 as activity, in contrast to mouse movement
and button1 (whose event dev is locked by synaptics), since those are
created on the new uinput event device, accessible to pbbuttonsd? I
haven't noticed this, but I would need to check.
> Synaptics Trackpad driver, often used on recent PowerBooks, also locks
> all mouse input events for exclusive use but in contrast to mouseemu
> it doesn't create an uinput device to let other applications receive
> mouse events. This problem is well known and Luca Bigliardi prepared a
> patch to work around this problem. Furthermore some people including
> Luca are working on a final solution of this problem. If you used the
> unmodified synaptics driver you would deprive pbbuttonsd and mouseemu
> of mouse events.
OK, work to be done here. That explains why mouse movement isn't
detected as activity.
> I hope this will help to identify where the problems come from or at
> least give some hinte where to look at next.
It still doesn't explain why Fn'ed keys aren't detected by pbbuttonsd
anymore while mouseemu is running.
Is mouseemu also locking the keyboard exclusively? That, plus the fact
that pbbuttonsd isn't opening the uinput event dev's, would be the
explanation then.
Thanks to all so far :-)
Cheers
Michel
PS Does anybody know what all those input devices correspond to?
-------------------------------------------------------------------------
Michel Lanners | " Read Philosophy. Study Art.
23, Rue Paul Henkes | Ask Questions. Make Mistakes.
L-1710 Luxembourg |
email mlan@cpu.lu |
http://www.cpu.lu/~mlan | Learn Always. "
Reply to: