<div dir="ltr">Éric, I never got around to figuring out how to do this in a safe way, and I don’t see me having time for that in the near future. I’d like to get the issue solved for other users of this touchpad, but I don’t currently have the time nor the knowledge to attempt any kernel-hacking. Could you point me towards the right bug-tracking system when I can report the issue so it will at least be documented and available for others to see and possibly to fix? Thank you for your help, David. <div class="gmail_quote">On Fri, Jul 23, 2010 at 02:33, Éric Piel <<a href="mailto:E.A.B.Piel@tudelft.nl" target="_blank">E.A.B.Piel@tudelft.nl</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div></div> Nope, not yet! You have to compile and install the kernel and make sure it works as well as your default kernel (at least for the mouse side). Check in google, and "make help", but basically, you have to do: make localmodconfig # only the very first time make # each time you modify the source code sudo make modules_install firmware_install install # to install it and then you reboot and select your new kernel in grub. Precisely, the kernel doesn't have to work as well as your distro kernel, but at least you should be able to boot into the graphical interface, modify files, and move the mouse. It's nicer to have it fully working in order to stay using this kernel all the time while your are developing. In case there are some functionality missing, you might want to check if some modules were not compiled in, and add them with "make menuconfig" Finally, when this is done, create a new branch in git: git checkout -b sentelic Then you can start modifying the driver :-) Eric</blockquote></div></div>