> > Alan you are thinking to PC here. On embedded devices that run X it is
> > just extra over head to use the VT interface. It would be much lighter
> > weigth to use the /dev/input/event interface. Personally I like to see
> > KBDRATE and alot of other junk go away in the console code. Intead we
> > just use the input api and /dev/fb with DRI. I have talked to Jim Getty
> > about this and likes to see things head in this direction.
>
> DRI ? What good is DRI to me on an embedded box.
You be surprised what is coming out soon into the embedded market :-) 3D
will soon be coming to small hand held devices!!
> What good is an fb driver when my hardware does text mode ?
Text mode is the expection not the norm.
> Why do I want the whole input layer loaded for a single fixed keyboard
> controller, or a serial interface driven by user mode ?
One is portablity. The input layer handles more than just keyboards.
All input devices look the same. Most embedded devices with input
interfaces have more than one type of input device (touchscreen,
attachable keyboards, buttons etc). Plus the input layer is modular and it
is small.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu May 23 2002 - 22:00:26 EST