Comment 60 for bug 296610

Of course I am. Personally, I'm a Debian user - for about 10 yrs, but I wanted to try its younger brother on my new laptop. It was an opportunity. :) At the moment I've been hacking on the alps.c source and testing stuff by rmmod/insmod-ing a patched psmouse module. Same results so far.

I'll have a look at your patch and try it out. Right now I don't even know what it does, I didn't see it yet. When I'm done, I'll let you know.

BTW, you might be able to tell me how module versioning works "under the hood". Even though I've written a kernel module myself and contributed to v4l-dvb, I never looked into this deep enough. I know how to work with it the traditional way, but I'd like to be able to just compile the psmouse module and insmod it. I cannot do it unless I go through all that "CONCURRENCY_LEVEL=3 AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules binary-generic-pae" stuff, somehow making a compatible deb package of my flavour from the distribution release. Then, my .ko's from the build tree work with my current kernel.

Is there a way I could hack Module.symvers or something to compile the kernel the old-fashioned way (make menuconfig; make) and then be able to use the .ko? It would save me a lot of time waiting for the "Debian-way" recompilations...