Re: input patch

[Johann D. <jo...@Do...>]

On Sun, 23 Dec 2001, Vojtech Pavlik wrote:

> On Sun, Nov 25, 2001 at 02:30:46PM +0100, Johann Deneux wrote:
> > On Fri, 16 Nov 2001, Johann Deneux wrote:
> > 
> > > Hello,
> > > 
> > > About the directory hierarchy, I decided to keep linus' hierarchy. Not
> > > that this is a better choice, but it first appeared to me being easier
> > > (fewer changes to makefiles). However, I think I will try to move to the
> > > linuxconsole hierarchy in the next version.
> > 
> > I have been trying to do that, and encountered a problem. Making this
> > input patch makes sense provided the console and input stuff are
> > separable. Is that the case ? Right now, it looks to me there is a strong
> > depedency: the keyboard depends on the vt, which depends on the console,
> > which depends on the frame buffer.
> > At the end, my input patch may more or less include the whole ruby/linux
> > tree !!!
> 
> The only way the input subsystem depends on the VT is through the
> keyboard.c file. However, if you use keybdev.c instead, you can keep
> what's in the normal kernels. It's a hack, though not too a gross one.
> 

Hmm, do you mean keybdev.c replaces the standard keyboard.c ? From what I
read in the input.txt file, and from what I've seen in keybdev.c,
keybdev.c uses handle_scancode defined in keyboard.c.

The problem is, keyboard.c seems to use functions from pckbd, namely
pckbd_{set,get}keycode and others.
That means I cannot use the ps2 keyboard+mouse stuff from ruby with my
patch. This is ok for me, as the standard code works quite well, but it
makes me wonder if the usb keyboard code will work.
Can hid.o, keybdev.o (both from ruby),  keyboard.o and pc_keyb.o (from
the standard kernel) all work together ?

-- 
Johann Deneux