All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zoltan Szecsei <zoltans@geograph.co.za>
To: linux-kernel@vger.kernel.org
Subject: Re: multiple independent keyboard kernel support
Date: Thu, 01 Sep 2005 15:07:20 +0200	[thread overview]
Message-ID: <4316FD08.1070505@geograph.co.za> (raw)
In-Reply-To: <20050901122253.GA11787@midnight.suse.cz>

Vojtech Pavlik wrote:

>On Thu, Sep 01, 2005 at 01:28:25PM +0200, Zoltan Szecsei wrote:
>
>  
>
>>Hi All,
>>The archives & FAQs on this subject stop at December 2003. Google not 
>>much help either (prob. due to my keyword choices)
>>
>>I gather the only way to do this is via the ruby patch.
>>
>>(When) Will there ever be native kernel (and maybe XFree) support for 
>>multiple independent keyboards?
>>    
>>
>
>The kernel console is unlikely to ever going to have that - noone is
>interested in changing the console subsystem.
>  
>
Ah, rats! :-(

>The current state of input device support in the kernel, however, allows
>any userspace program to access them independently, including keyboards.
>
>That means multi-user X and possibly a userspace console implementation
>(Jon Smirl is planning one) has no barriers in the kernel input device
>  
>
Do you have an email address so that I can keep in touch with him?

>implementation keeping it from proceeding.
>
>The problems with multiple VGA cards, etc, are much harder to solve,
>though.
>  
>
That's a surprise - barring the keyboard issue, I thought I was close to 
getting it working on my SuSE 9.3 using 2 mice, onboard 915G graphics 
and an old TSENG Labs ET6000.
Maybe I had further to go than I realised :-(

>  
>
>>The ruby patch seems to also only have discussions older than 18 months.
>>
>>Has there really been no progress in the last 18 months?
>>
>>I would prefer to see "official and permanent" support for this as then 
>>when HW & drivers & kernels develop in the future, this capability will 
>>always be (immediately) available - and not have to wait for patches.
>>    
>>
>
>Many people would like that. But not many enough to make it happen, at
>least not until now.
>  
>
Ah cool - there's hope - any pointers on how I can get a counter or 
lobby group going?  :-)

Thanks for taking time to reply.

Cheers,
Z


-- 

==================================
Geograph (Pty) Ltd
P.O. Box 31255
Tokai
7966
Tel:    +27-21-7018492
Fax:	+27-86-6115323
Mobile: +27-83-6004028
==================================



  reply	other threads:[~2005-09-01 13:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-01 11:28 multiple independent keyboard kernel support Zoltan Szecsei
2005-09-01 12:22 ` Vojtech Pavlik
2005-09-01 13:07   ` Zoltan Szecsei [this message]
2005-09-01 13:24     ` Vojtech Pavlik
2005-09-01 14:48       ` Martin Mares
2005-09-01 16:38         ` Vojtech Pavlik
2005-09-11 22:36         ` Helge Hafting
2005-09-12 16:03           ` Bjorn Helgaas
2005-09-12 20:47             ` Kyle Moffett
2005-09-13 16:20               ` Bjorn Helgaas
2005-09-11 22:34 ` Helge Hafting
2005-09-12  7:01   ` Zoltan Szecsei
2005-10-19 16:01   ` Zoltan Szecsei
2005-10-19 19:23     ` Helge Hafting
  -- strict thread matches above, loose matches on Subject: below --
2005-09-01 13:35 Svetoslav Slavtchev
2005-09-01 14:06 ` Zoltan Szecsei

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=4316FD08.1070505@geograph.co.za \
    --to=zoltans@geograph.co.za \
    --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.