From: Alessio Sangalli <alesan@manoweb.com>
To: linux-input@vger.kernel.org
Subject: "soft" USB keyboard and mouse driver
Date: Tue, 21 Apr 2009 01:48:23 -0700 [thread overview]
Message-ID: <49ED8857.9010809@manoweb.com> (raw)
Hi I would need a hint what is best to do; I have an embedded device
that can do a "soft" implementation of USB for embedded
applications. The aim is to be compatible with low-speed HID USB
devices.
The fact is, it does not implement a full USB stack but only
point-to-point communication with the aforementioned devices. I know it
sounds weird but it's more like a "PS/2" port than a USB thing.
Now, I have a generic character device driver that can read keyboard and
mouse data. Of course I get what a USB device would send when you press
keys etc.
How do you think it would be the best way to integrate it with the input
subsystem?
Any idea would be appreciated.
Thank you!
Alessio
next reply other threads:[~2009-04-21 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 8:48 Alessio Sangalli [this message]
2009-04-22 11:22 ` "soft" USB keyboard and mouse driver Jiri Kosina
2009-04-22 16:01 ` Alessio Sangalli
2009-04-23 9:33 ` Jiri Kosina
2009-04-23 15:18 ` Alessio Sangalli
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=49ED8857.9010809@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 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).