Re: splitting ruby

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

At 18:10 2001-01-10, James Simmons wrote:

> > Now 2.4.0 is out, whats next?
>
>A lot more work :-)
>
> > I think it might be a good idea to split ruby into 2 parts: the input side
> > (mostly working) and the console parts (still under dev), and try to get
> > the input side stuff into 2.4.1.
>
>I agree except you will not see the rest of the input stuff go into
>2.4.X. We will have to wait until 2.5.0. I have talked to Geert about this
>as well. I think the best attack plan is:
>
>1) Dump all the input drivers into the console system.
>2) Change all the fbdev drivers too.
>3) Change the console system.
>
>I don't know if linus would be willing to dump all our work in at one
>time. If he would be willing to do so then I would dump it all in. This of
>course would require that we have partily working functionality on ALL
>platforms. I can test the stuff on PPC, sparcs and alpha as well but
>haven't yet. Plus I need to get into contact with the other platform
>developers for this.

Well, I don't expect problems for PPC, as the adbhid.c driver is already 
part of 2.4.0, (sigh, reminds me to merge PPC code between ruby and 2.4.0) 
including the rest of the input code in 2.5.0 will just simplify the code 
and clarify configuration (especially on HW supporting both ADB and PS2 
keyboards) for us.

My TODO list for the full input code merge on PPC is quite short:
  - drop the emulate_raw() support for ADB keycodes, present in 2.4
  - drop the emulation code for 2nd and 3rd mouse button (maybe not?)
  - eventually write a handler kmmdev.c, that mixes keyboard and mouse 
events onto a single device (similar to /dev/input/mice) running the event 
protocol

Franz.