Re: question about ruby's keyboard.c & keybdev.c

[Franz S. <Fra...@la...>]

At 12:43 02.07.2002, Svetoslav Slavtchev wrote:
>Hi ,
>is it supposed drivers/input/keybdev.c to declare the functions and variables,
>that are allready defined in drivers/char/keyboard.c , more precisely 
>x86keycodes
>and the problematic emulate_raw,
>
>and ...
>how can one compile kebdev
>it seems to me that drivers/input/keybdev.c comes from standart 2.5 or may 
>be -dj
>but not from ruby, what i mean is in emulate_raw it uses handle_scancode,
>which doesn't exist in ruby but exist in 2.5 and -dj
>and as far i understand the code is replaced by put_queue
>so .. ? should handle_scancode in keybdev.c be replaced by put_queue
>
>and the other unresolved symbol in keybdev.c -- kbd_ledfunc
>it appears to me that in keyboard.c kbd_ledfunc is replyced by ledstate
>is this correct ?
>
>so
>how should one compile keybdev.c ?

With ruby you shouldn't compile keybdev.c at all, it's only in ruby CVS for 
maintenance reasons. keybdev.c provides bridge code between input layer and 
old-style keyboard.c. In ruby this is no longer necessary as the new-style 
keyboard.c registers itself directly to the input layer.

Maybe you should just wait some more days, Vojtech should be merging this 
to Linus any day now.

Franz.