All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alessio Sangalli <alesan@manoweb.com>
To: linux-input@vger.kernel.org
Subject: Equivalent of /dev/input/mice for keyboards
Date: Fri, 02 Jan 2009 15:29:53 -0800	[thread overview]
Message-ID: <495EA371.8050304@manoweb.com> (raw)

Hi, I have developed a PS/2 driver for a new ARM-based hardware.

I have used the serio subsystem and I can test with input-event or
similar programs that the keyboard and mouse I have connected work well.

Now, this platform, being an embedded ARM board, does not have a
"console" that can be attached to the keyboard. I only connect with
serial port or telnet. And here I am getting confused: I can read one
device at a time by opening /dev/input/event*.

I would like to write my userspace application so that it gets all the
input from the various keyboards (can be up to two PS/2 keyboards + USB
ones) and process it. The struct input_event is very convenient but what
I am doing now is to open all the event* devices and select() them. This
wouldn't probably work if I connect/disconnect a device on the fly. It
would be much easier if I had a device similar to input/mice that
automatically does the muxing for me...

Thank you
Alessio



             reply	other threads:[~2009-01-02 23:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-02 23:29 Alessio Sangalli [this message]
2009-01-12  7:32 ` Equivalent of /dev/input/mice for keyboards Dmitry Torokhov
2009-01-12 21:14   ` Alessio Sangalli
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=495EA371.8050304@manoweb.com \
    --to=alesan@manoweb.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.