Re: faketty + vt7

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

On Ceturtdiena, 1. Septembris 2005 21:11, Hugo Vanwoerkom wrote:
> Hi,
>
> I'll start a new thread to make searching a little
> easier.
>
> Everything with faketty works and more.
>
> My setup again: AGP=TNT2 PCI=MX-440.
>
> If I start gdm with:
>
> name=Standard server
> command=/usr/X11R6/bin/X0 :0 -layout X0 -deferglyphs
> 16 -isolateDevice \"PCI:1:0:0\" vt50
> flexible=true
>
> # Definition of the second X server.
> [server-2nd]
> name=2nd server
> command=/usr/X11R6/bin/X1 :1 -layout X1 -deferglyphs
> 16 -isolateDevice \"PCI:0:10:0\" vt51
>
> I get garbage on the AGP, little speckles that follow
> the mouse in 3 different places on the screen. PCI
> screen is fine.
>
> And I cannot use Alt+Ctrl+Fx to switch to a text vc.
>
> If I change this to (I found this by mistake):
>
> name=Standard server
> command=/usr/X11R6/bin/X0 :0 -layout X0 -deferglyphs
> 16 -isolateDevice \"PCI:1:0:0\" vt7
>
> The garbage disappears and I can switch to a text
> console and back.
>
> Why does this work? So faketty got me Ruby free and
> everything works as before. My power typist for the
> PCI monitor hasn't shown up to see if I get those
> keyboard overflows on my textconsole.

Here is quite different layers. TTY and faketty. Both
are completely independ, exluding LED handling.
faketty do not knows nothing about VT-handlig. faketty
send necessary characters to device file fttyXX. When
userspace program opens fttyXX, then faketty grab that
device and input events goes to faketty only.

This trick became possible besause of new input layer.
Under new input layer every body can register unlimited
count of event handlers of each input device. Current
exist kbd mouse event. These 3 generates events via
assigned device files with proper protocol.

Charaters, which runs via TTY in "RAW" mode, looks
very simple for me. I face up to new handler. Code
is as simple as possible. for that reason some ioctl's
like bell are cleaned up but wholly possible.
VT-handling is totally impossible. From view point of
angry kernel developer that all is duplicate code.

Keyboard soft IRQ handler does not take care for grabed
devices, so LED handling is exlusive and hijacked for the
sake of text mode console.

You are wellcome to rewrite that damn readme :-)

Aivils