linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alessio Sangalli <alesan@manoweb.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input@vger.kernel.org
Subject: Re: "soft" USB keyboard and mouse driver
Date: Wed, 22 Apr 2009 09:01:38 -0700	[thread overview]
Message-ID: <49EF3F62.6020300@manoweb.com> (raw)
In-Reply-To: <alpine.LRH.2.00.0904221319520.18261@twin.jikos.cz>

Jiri Kosina wrote:

> I am not really sure I understand very well. So you have the device the 
> provides some "crippled" implementation of USB and provides some HID 
> devices on top of it, and you would like to have this compliant with the 
> kernel Input/HID infrastructure?

Yeah we can define it that way. It basically provides a low-speed USB
port to chips that do not have a USB controller and PHY. Yes, it sounds
disgusting, but sometimes it's the only way to use USB input devices to
embedded systems that do not have USB connectivity.

> If the devices are really HID (i.e. the protocol on the wire is proper HID 
> as defined by HID specification), you'd only need to implement a 
> specialized "transport" HID code for this transport protocol, and let the 
> HID core do the rest.

Well those are standard USB keyboard and mice, so what goes on the wire
is what is expected by those devices.


> Currently there are implementations for USB and Bluetooth which you can 
> look at.

Could you point me to a more specific example?

Thank you
Alessio



  reply	other threads:[~2009-04-22 16:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-21  8:48 "soft" USB keyboard and mouse driver Alessio Sangalli
2009-04-22 11:22 ` Jiri Kosina
2009-04-22 16:01   ` Alessio Sangalli [this message]
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=49EF3F62.6020300@manoweb.com \
    --to=alesan@manoweb.com \
    --cc=jkosina@suse.cz \
    --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).