All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Carnecky <tom@dbservice.com>
To: Helge Hafting <helge.hafting@hist.no>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com,
	dri-devel@lists.sourceforge.net
Subject: Re: Kernel thoughts of a Linux user
Date: Wed, 24 Nov 2004 12:31:05 +0100	[thread overview]
Message-ID: <41A470F9.4000407@dbservice.com> (raw)
In-Reply-To: <41A46085.5050602@hist.no>

Helge Hafting wrote:
>> From the [ruby patch] documentation:
>> The main problem up to this date (November 2004) is that linux kernel 
>> has only one behaviour regarding multiple keyboards : any key pressed 
>> catched on any keyboard is redirected to the one and only active 
>> Virtual Terminal (VT).
>>
>> Will this be changed/improved when the console code is moved into 
>> userspace, like some have proposed?
> 
> 
> I don't know about any userspace console, but the ruby patch lets
> you have several independent active VTs at the same time.  So
> the above mentioned problem is solved - they keyboards does
> not interfere with each other.
> 

I think the it would be much nicer to habe the console code in 
userspace, ruby is only a patch, not in the mainline kernel, and AFAIK 
not even in any experimental (-mm/-ac/-etc) tree.
There are many aproaches how to solve the problem of having more than 
one ative VT, and the userspace console seems to be the nicest one.

I know that Jon Smirl wrote an email some time ago, here it is: 
http://lkml.org/lkml/2004/8/2/111, look at point 15. I like the idea and 
I've written him several times, but he didn't answer :(
Anyone knows what's happened with him?
I know he's involved in the DRM development, so I CC to the dri-devel list.

I'd really like to help with this, as I like and share his ideas.

Is anyone already working on this? I mean pulling the console code out 
of the kernel into the userspace.

tom

  reply	other threads:[~2004-11-24 11:34 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18 17:59 Kernel thoughts of a Linux user Gerold J. Wucherpfennig
2004-11-18 18:50 ` Greg KH
2004-11-18 20:00 ` Tomas Carnecky
2004-11-18 20:46   ` Jan Engelhardt
2004-11-18 20:52     ` Tomas Carnecky
2004-11-18 21:05       ` Jan Engelhardt
2004-11-18 21:15     ` Chris Friesen
2004-11-18 21:17       ` Jan Engelhardt
2004-11-18 21:29         ` Chris Friesen
2004-11-19 12:02         ` Paulo Marques
2004-11-19 12:05           ` Jan Engelhardt
2004-11-20  2:14           ` Alan Cox
2004-11-22  8:07   ` Helge Hafting
2004-11-22  8:38     ` Jan Engelhardt
2004-11-24 10:23       ` Helge Hafting
2004-11-22 11:17     ` Tomas Carnecky
2004-11-24 10:20       ` Helge Hafting
2004-11-24 11:31         ` Tomas Carnecky [this message]
2004-11-28 19:10           ` Helge Hafting
2004-11-19  5:04 ` H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2004-11-20 10:31 Gerold J. Wucherpfennig
2004-11-21 18:29 ` Greg KH
2004-11-22 21:33   ` Gerold J. Wucherpfennig
2004-11-22 18:40     ` Greg KH
2004-11-22 18:52     ` Måns Rullgård
2004-11-22  9:54 Adam J. Richter
2004-11-22 14:54 Adam J. Richter
2004-11-22 20:21 ` Maneesh Soni
2004-11-22 15:32 Adam J. Richter
2004-12-14 18:02 Jan Engelhardt

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=41A470F9.4000407@dbservice.com \
    --to=tom@dbservice.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=greg@kroah.com \
    --cc=helge.hafting@hist.no \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.