|
From: Petr V. <VAN...@vc...> - 2000-04-05 16:02:15
|
On 5 Apr 00 at 10:38, James Simmons wrote:
> Second issue:
> The next question is how to handle multihead? Here are some models.
> ---------------------------------------------------------------------------
> First Model:
> The current kernel doesn't really handle this very well. The kernel has
> 32 virtaul consoles. Fbdev has a function con2fb that maps a framebuffer
^^ 64
> to a VT or set of VTs. This is done because the current console system
> can't handle multihead properly. Continuing to use this model we would map
> devices around. Many problems with this model :(
I vote for this model. I do not know where problems with this model live.
Except that with correct code you can have two (or more) keyboards
attached to one VT then. But it is (useful) feature, not a bug. Even
Windows can have two mouses connected at one time, controlling one
mouse pointer together.
> Second Model:
> Create VT pools per head. In this model we have a each head behave
> indpenedently. For each head you you can VT switch around but you can
> never VT switch to another head.
I really do not want to have to buy another keyboard because of I have
dualhead G400. Or what is definition of head and how is it supposed
to work?
Best regards,
Petr Vandrovec
van...@vc...
|