On Sun, Sep 11, 2005 at 09:16:42PM -0300, Diego Essaya wrote: > I may be wrong, but I think that the 'psmouse' module is unnecessary. > In fact, I don't have a PS/2 mouse (I have a USB one). > > The 'evdev' and 'mousedev' modules may be unnecessary as well...
In the meantime 0.0.11 is published, which makes it easier to play with what modules are used. Look at /usr/lib/yaird/conf/Default.cfg, but beware that this is not yet marked as a configuration file, so any changes made there will be overwritten by a new release. You can specify an alternative config file on the command line. The cause: yaird looks for keyboard devices in /proc/bus/input/devices, finds /sys/class/input/event0, with a link to the underlying hardware: /sys/devices/platform/i8042/serio1. Then we load required modules for the hardware. Platform? Nothing special. i8042? Just the i8042 module. Serio1? Hmmm, could be a psmouse, could be atkbd; lets load both. This is ugly: the fact that serio does not have the nicely coordinated vendor/product codes you find in USB or PCI devices makes it difficult to do good detection. Could we use 'driver' link in .../serio1 to find the appropriate device driver? Only if (a) the driver has same name in running and new kernel, and (b) driver is modular in running kernel. Not reliable enough. Note that older kernels (< 2.6.10?) don't have the device link in /sys/class/input/event0, in which case some fallback logic in yaird becomes active: if /proc/bus/input/devices talks about keyboard, it's probably atkbd. The psmouse stuff doesn't happen in this case. For 0.0.12, I plan to look at 'softrepeat' and 'resolution' files in serioX sysfs directory; this distinguishes nicely between atkbd and psmouse device, and it should break *visibly* for exotic stuff like newton kbd, which is an improvement over the current approach of load atkbd and hope for the best. Regarding evdev and mousedev: you don't need these to boot the system, but if mouse or keyboard is loaded from initramfs rather than /etc/init.d, you no longer can assume evdev and mousedev get sucked in as a side-effect, and they are probably needed: evdev is what allows yaird to find the keyboard, mousedev is expected by X-Windows. It would probably be more straightforward to load them from /etc/modules, but that would require manual intervention by the sysadm: the system no longer works out of the box for common configurations. Lets not do that. Erik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
