public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jos Hulzink <josh@stack.nl>
To: James Simmons <jsimmons@infradead.org>
Cc: Rick Warner <rick@sapphire.no-ip.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: support for dual independent keyboards in devel kernel?
Date: Thu, 13 Feb 2003 08:36:20 +0100 (CET)	[thread overview]
Message-ID: <20030213082212.L32807-100000@toad.stack.nl> (raw)
In-Reply-To: <Pine.LNX.4.44.0302121833480.31435-100000@phoenix.infradead.org>

On Wed, 12 Feb 2003, James Simmons wrote:

> > I have been doing some research on running 2 independent displays off of 1
> > machine (ie 2 keyboards, 2 mice, 2 vid cards, 2 monitors).. there are some
> > hacks out there now that "sort of" work.... but nothing stable and official..
> > it's all hacks....   I have read that support for this is planned for
> > 2.5/2.6, and would like to know what progress has been done.  I am willing to
> > help where I can.  I am a good C/C++ programmer, but have not done any kernel
> > work so far.
>
>    You are talking about the linuxconsole project. Yes with alot of work
> we got a multi-desktop system working. We even got several X servers with
> several patches running on different desktops even tho they where working
> out of one box. The main problem with this research was the console system
> level of code was intertwine in each input and display driver. In 2.5.X
> you see the moving of the console keyboards etc to the input api which can
> function indepenedent of the console layer. You also had the same effect
> with the new framebuffer layer. This was done to make driver writing easy
> and to help the embedded space as well as prepare for the future
> multi-desktop of linux.
>    What has not been done is true multi-desktop support. I like to work on
> this in the future but due to recent events in my life I have to abandon
> such research :-(
>

There is another project dealing with this: KGI. This project not
only deals with Linux, but also with NetBSD and Freew:BSD. Together with
the
Linux input layer KGI should support as many keyboards / mice as you can
buy.... Multiple desktop consoles runs fluently, support for full 3D
accellerated desktops (with help from an user space lib: GGI) is almost
there.

I'm still looking at how to connect multiple keyboards, for now I use a
microcontroller on a serial port which gives me 4 keyboards extra.

Unfortunately we're still missing a programmer willing to take a look at
the multiple keyboard / mice issue. The code is almost there, though not
functional yet. For info about KGI please drop by on
http://kgi-wip.sourceforge.net or irc.freenode.net #kgi

Jos

P.S. For those thinking KGI is still that crazy project doing graphics
accelleration in the kernel trough ioctls, please look again !


      parent reply	other threads:[~2003-02-13  7:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-25 22:14 support for dual independent keyboards in devel kernel? Rick Warner
2003-02-12 18:40 ` James Simmons
2003-02-12 18:48   ` John Bradford
2003-02-12 21:14     ` James Simmons
2003-02-12 21:33       ` John Bradford
2003-02-13  7:36   ` Jos Hulzink [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030213082212.L32807-100000@toad.stack.nl \
    --to=josh@stack.nl \
    --cc=jsimmons@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rick@sapphire.no-ip.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox