[Kbde-general] kernel module? reccomended change

[Jeff S. <jef...@gm...>]

Its been a while since I last used kbde.
Recently I wanted to simulate a kernel panic as a joke

watch -n 1 "kbde -d 0 --key=CapsLock --key=NumLock; xset led 3;sleep
1;kbde -d 0 --key=CapsLock --key=NumLock; xset -led 3"

and realized that it wasn't doing what I thought.
Then I remembered I needed to load a kernel module.
I downloaded the source code and there was no kernel module in it to build.
So I downloaded the cvs

 cvs -d:pserver:ano...@kb...:/cvsroot/kbde login
 cvs -z3 -d:pserver:ano...@kb...:/cvsroot/kbde co -P kbde

then I went into the driver section and attempted to build the module

/root/kbde/kbde-cvs/kbde/kbde-driver/driver/kbde.c: In function 'kbde_write':
/root/kbde/kbde-cvs/kbde/kbde-driver/driver/kbde.c:96: error: too many
arguments to function 'serio_interrupt'
make[4]: *** [/root/kbde/kbde-cvs/kbde/kbde-driver/driver/kbde.o] Error 1
make[3]: *** [_module_/root/kbde/kbde-cvs/kbde/kbde-driver/driver] Error 2
make[2]: *** [kbde.ko] Error 2
make[1]: *** [all-recursive] Error 2
make: *** [all-recursive] Error 2

I did a quick google on [error: too many arguments to function
'serio_interrupt']
something about the last argument being dropped so I did that in the source code

diff -Nu kbde-cvs/kbde/kbde-driver/driver/kbde.c kbde/kbde-driver/driver/kbde.c
--- kbde-cvs/kbde/kbde-driver/driver/kbde.c     2006-03-29
02:24:07.000000000 -0700
+++ kbde/kbde-driver/driver/kbde.c      2007-04-19 13:21:58.000000000 -0600
@@ -93,7 +93,8 @@
                get_user(scancode, (char*)buf++);
                //printk("SYMBOL = %x\n", (unsigned int)scancode);

-               serio_interrupt(kbde_port, scancode, 0, NULL);
+               /*serio_interrupt(kbde_port, scancode, 0, NULL);*/
+               serio_interrupt(kbde_port, scancode, 0);
        }
        return retval;
 }

I compiled the kernel model and did "depmod -a"
and realized I also had to deleted /dev/kbde and recreate it with
"mknod /dev/kbde c 11 0"

This seemed a little complicated to me. I'm glad I knew what I was
doing and had some experience with this in the past.