All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kendall Bennett" <KendallB@scitechsoft.com>
To: linux-kernel@vger.kernel.org
Subject: Kernel 2.5 input layer info?
Date: Fri, 28 Feb 2003 12:07:06 -0800	[thread overview]
Message-ID: <3E5F50EA.13587.3FA4953@localhost> (raw)
In-Reply-To: <1786144585.20030228074127@wlink.com.np>

Hi Guys,

I have heard about the new 2.5 input layer work that is being done in the 
kernel, and I am interested in using this for a userland mouse/keyboard 
daemon I am looking at building. The intention of the daemon is to 
provide a common interface for event driven mouse and keyboard 
applications (ie: XFree86, Qt/E, SDL, MGL, SVGALib etc) on Linux. Since 
it appears that a lot of work is already being done on a new set of event 
driven input layers in the kernel, what I would like to do is build this 
daemon such that it will use the new 2.5 kernel interfaces when they are 
available, but fall back on the old compatible methods when not. 
Essentially I am planning on taking the existing XFree86 code and using 
it to make a common user land input daemon.

Anyway, let me know if you think this is a good idea, bad idea or if 
there is a better way to do it. The new input interfaces sound like a 
great idea, but we are looking for something that will work on as many 
versions of Linux as possible.

Finally where can I find more information on the new input interfaces in 
the 2.5 kernel? I just downloaded the latest 2.5.63 release and will take 
a look at it, but if there are any external docs on this I would like to 
peruse them first.

Thanks!

---
Kendall Bennett
Chief Executive Officer
SciTech Software, Inc.
Phone: (530) 894 8400
http://www.scitechsoft.com

~ SciTech SNAP - The future of device driver technology! ~


  reply	other threads:[~2003-02-28 19:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-28  1:56 npguy
2003-02-28 20:07 ` Kendall Bennett [this message]
2003-02-28 20:41   ` Kernel 2.5 input layer info? Randy.Dunlap

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=3E5F50EA.13587.3FA4953@localhost \
    --to=kendallb@scitechsoft.com \
    --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.