All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alessio Sangalli <alesan@manoweb.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: Equivalent of /dev/input/mice for keyboards
Date: Mon, 12 Jan 2009 13:14:43 -0800	[thread overview]
Message-ID: <496BB2C3.9080307@manoweb.com> (raw)
In-Reply-To: <20090111232539.ZZRA012@mailhub.coreip.homeip.net>

Dmitry Torokhov wrote:

> I am very hesitant adding such multiplexing device to the kernel. While
> it is pretty easy to write one we had only pain from them. There are all
> kinds of quirks, grabs, and workarounds because people are using
> /dev/input/mice and console but at the same time want to use event
> devices for some of the hardware.

Yes I appreciate your comments, I get your point.

What I would personally like to experiment with is:
- enabling this driver would automatically disable the other event
devices and the console, so it is the only source of input events for
the system
- to me it's also an exercise the helps the understanding of the input
layer and the kernel in general.

In my free time, I'd like to do the implementation, having in mind you
are not interested in merging it into the kernel. Would you spare some
hints on how you would proceed?

bye
as


  reply	other threads:[~2009-01-12 21:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-02 23:29 Equivalent of /dev/input/mice for keyboards Alessio Sangalli
2009-01-12  7:32 ` Dmitry Torokhov
2009-01-12 21:14   ` Alessio Sangalli [this message]
2009-01-13  5:53     ` Dmitry Torokhov
2009-01-15  7:56       ` Alessio Sangalli
2009-01-15  8:33         ` Dmitry Torokhov

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=496BB2C3.9080307@manoweb.com \
    --to=alesan@manoweb.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@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.