Frans Pop wrote:
On Friday 15 December 2006 21:45, Frans Pop wrote:I've finally been able to trace the problem to a config change in the kernel: -CONFIG_INPUT_MOUSEDEV=m +CONFIG_INPUT_MOUSEDEV=yIt's still a bit unclear how/why that option was changed.It may have been on request of the maintainer of udev as udev has no sane way to load mousedev.From the Kconfig this parameter is responsible for creating /dev/input/mouseX and /dev/input/mice. For g-i we never included that module (only evdev, psmouse and usbmouse). Can the presence of these devices influence the behavior of directfb?Attached some info from my laptop, including the output of dfbinfo (from a 2.6.18 kernel without that option set).
On my regular debian system i have $ uname -r 2.6.18-1-686 $ cat /boot/config-2.6.18-1-686 |grep CONFIG_INPUT_MOUSEDEV= CONFIG_INPUT_MOUSEDEV=y and i can handle my usb mouse via ps2mouse or linux_input indifferently.I guess your hardware is a bit different from mine (IIUC your /proc/bus/input/devices output, your alps touchpad is listed twice, while on my debian system my synaptics touchpad is listed once only) and i cannot reproduce the crash, but what if you boot textual, add
disable-module=ps2mouseto /etc/directfbrc and then switch graphical ? does the freeze still happen ? what's now the dfbinfo output ? do both touchpad and usb mice still work ?
In the case this should work, we could simply disable ps2mouse on x86 (as we did for keyboard module) so that both keyboard and mice/touchpad are always handled by linux_input.
For the future it would be nice if we could switch to an unique input driver for both x86 and PPC, but unluckily on some Mac models linux_input crashes badly right now, and we had to implement that infamous ugly [1] hack :(
Attilio[1] http://wiki.debian.org/DebianInstaller/GUIToDo#head-fa668fd9c7b4c31a91f90019b6133be37ab31fda