From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Alessio Sangalli <alesan@manoweb.com>
Cc: linux-input@vger.kernel.org
Subject: Re: Equivalent of /dev/input/mice for keyboards
Date: Thu, 15 Jan 2009 00:33:27 -0800 [thread overview]
Message-ID: <200901150033.27934.dmitry.torokhov@gmail.com> (raw)
In-Reply-To: <496EEC31.3080007@manoweb.com>
On Wednesday 14 January 2009 23:56:33 Alessio Sangalli wrote:
> Dmitry Torokhov wrote:
> > I would take /dev/input/evdev.c as a base but instead of creating a new
> > character device in connect() method I would route all events into a
> > single device created upon module load (also see
> > drivers/input/mousedev.c). That should be really it.
>
> Hi, I've spent a few hours trying to get it right. I am able to
> "connect" the devices correclty but when it's time to open the devices I
> get a file "No such device" error. The code is at:
>
> http://pastebin.ca/1308960
>
> and I think the problem is around evall_open (line 129). Probably just a
> look of an experienced developer can give me some small indication what
> to do to solve the issue.
>
The way character devices are created by input core is tied very much
into existing handlers and is not very easy to plug into. I would
recommend creating a character device manually via misc_register() -
see how it is done in mousedev.c for psaux_mouse.
Also, I'd recommend getting rig of ioctl, write and grab code, they
don't make sense in context of multiplexor device and clutter the
code way too much.
Hope this helps.
--
Dmitry
prev parent reply other threads:[~2009-01-15 8:34 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
2009-01-13 5:53 ` Dmitry Torokhov
2009-01-15 7:56 ` Alessio Sangalli
2009-01-15 8:33 ` Dmitry Torokhov [this message]
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=200901150033.27934.dmitry.torokhov@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).