Jon Grosshart wrote: > /dev/input/mice is NOT a suitable device for the synaptics driver. You > need to supply the real device. > > Ortwin > > > > I'll say the same thing as Nick... As far as I'm aware, using "auto-dev" > completely overides your device option and will use a /dev/input/event* > node.... You can put:
Partly. auto-dev enumerates all /dev/input/event* files (path hardcoded) and tries to open them. If it succeeds you should see a line like: "synaptics auto-dev sets device to /dev/input/event7" There is a small glitch in the algorithm: if there is a gap of 10 (event3, event14) in the device numbers the algorithm stops. This may happen after a couple suspend/resume cycles for instance. The drivers tries every event device and figures out if it can be used as a touchpad. A "touchpad" device must have registered to report these events: - ABS_X, ABS_Y and ABS_PRESSURE of the EV_ABS class - BTN_TOOL_FINGER but not BTN_TOOL_PEN of the EV_KEY class - the EV_SYN class everything else is not treated as a touchpad. There is no guarantee that the drivers chooses the right device. I recommend setting the right device and using "event" for the protocol. Ortwin -- [web] http://www.odi.ch/ [blog] http://www.odi.ch/weblog/ [pgp] key 0x81CF3416 finger print F2B1 B21F F056 D53E 5D79 A5AF 02BE 70F5 81CF 3416 ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Mactel-linux-users mailing list Mactel-linux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mactel-linux-users
