Re: No patches any more - fake tty driver

[Aivils S. <ai...@un...>]

On Tre=C5=A1diena, 24. Augusts 2005 12:13, Helge Hafting wrote:
> >Hi , All!
> >
> >Don't like patched kernel. Ok try out vanilla!
> >
> >=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0Main goal of this fake TTY dri=
ver is multi seat Linux box creation
> >without any patch under Debian stable or Mandriva 2005 LE , which distros
> >contains -isolateDevice patch of X.
> >
> >=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0Recent Linux kernel does not f=
orce us use evdev or tty layer. Even
> > sytem operator can load new input handler. Actualy i write faketty kern=
el
> > module, which create device file for each keyboard. That device file
> > emulate TTY layer.
> > =C2=A0
>
> Interesting. =C2=A0Do this have an advantage compared to using
> evdev, which is supported in ubuntu's x.org? (this x.org
> also works on debian testing, making multiseat X possible
> with a standard kernel. =C2=A0

No advantage. I need _running_ system with minimum costs.
Linux-ruby dummy console is very close to be "fake" tty. Most of
dummy console device ioctl's is meaningless. 99% of linux-ruby
users start multiple X neither multiple text mode consoles.

Why i should create huge patch under these conditions ?

> But of course only one user=20
> gets a vga console.

A small bug of keyboard_tasklet allow "normal" keyboard
steer all LED's of all keyboards.

> >Keypress events are translated to standard TTY layer keycodes. These
> > keycodes can use X for input.
> > =C2=A0
>
> Is it possible to run a getty taking input from such a faketty, and
> also redirecting the output of that getty to some process who
> renders it on a framebuffer device?

No. K_XLATE keyboard mode erased during code optimisation.

Aivils Stoss