Re: [Touchd-devel] Touchd

[Scott S. <sco...@gm...>]

Florian,
Its neat you found it!  More comments inline.  I've cced this to the new 
touchd mailing list.

Florian wrote:
> Hi!
>
> I'm currenty trying to get the touchpad of my brand newMacBook Pro to
> work in Ubuntu (well, the pointer works fine, but no right click,
> scrolling etc...) so I did some research and found your program.
> I decided to give it a go. So far, I got it to compile, and when I ran
> it as root, it segfaulted because it could not find the USB device for
> the touchpad. So I dug out my "lsusb" and found that instead of having
> a productId of 0x0230, my touchpad is at 0x231... so I changed that in
> multitouch.c, recompiled, and when I ran it, it did find the device
> (obviously), started doing some stuff, but I never got the pointer to
> move again, and the keyboard became unresponsive. I had to go for hard
> reboot (long press on power button). Obviously, after a reboot, I
> tried again :) and it crashed just the same. Here is the log, if it's
> any help:
>   
It makes sense that you lost the keyboard and mouse, touchd steals it 
from the kernel.  I'd suggest using an external keyboard and mouse 
instead of a hard restart.
> touchd:main Connecting to the Session D-Bus.
> touchd:main Registering the well-known name (org.tannewt.touchd)
> touchd:main RequestName returned 1.
> touchd:main Creating one Touchd object.
> touchd:touchd_object_class_init: Called
> touchd:touchd_object_class_init: Creating signals
> touchd:touchd_object_class_init: Binding to GLib/D-Bus
> touchd:touchd_object_class_init: Done
> touchd:touchd_object_init: Called
> touchd:main Registering it on the D-Bus.
> touchd:main Ready to serve requests (daemonizing).
> touchd: Not daemonizing (built with NO_DAEMON-build define)
> touchd: Setting up uinput device.
> device run
> found on bus 3
> got vendor: 0x5AC product: 0x231
> return value 8
> There are 1 engine queues
>
>
>
> So my question is this, I see you do some voodoo a couple of lines
> below the find_device function. Is there any chance I need to change
> some of those magical values to something different, since my
> productId is different? And to what doest this productId thing
> correspond: is it just an adress, or could it mean I have a different
> revision of the touchpad?
>   
The different product id indicates it is different hardware.

The first thing I would do is uncomment the g_print lines in the voodoo 
section and send me the output.

Second, I would use usbmon, get the source so you can make it display 
all the data, to snoop the usb traffic caused by touchd startup.  You'll 
need to modprobe usbmon too.

http://people.redhat.com/zaitcev/linux/

The last resort is snooping traffic from the windows usb drivers.  I did 
this by running Vista in vmware and capturing the usb data using usbmon.
> Of course, if you need any extra info, I'll do my best to provide it :)
> Thanks!
> Florian
>   
No problem.  Could you give me all of the specs on your computer so that 
I can distinguish between the different versions with different chips?

Thanks,
Scott