linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <me@felipebalbi.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Figuring out devnodes from a usb device
Date: Wed, 04 Aug 2010 05:09:42 +0000	[thread overview]
Message-ID: <4C58F616.1090201@felipebalbi.com> (raw)
In-Reply-To: <4C55D1CF.5090206@felipebalbi.com>

Hi,

On 08/03/2010 11:32 PM, Greg KH wrote:
> How do you know what a vendor-specific device is doing?  Are you going
> to be able to parse the HID descriptors to know what type of input
> device(s) are present?

we can start simple. USBCV only runs the chapter 9 tests (which are
pretty much verifying if the device responds to standard requests
accordingly) which any device, and runs a set of MSC tests on MSC devices.

We can start with only that and improve later on.

-- 
balbi

      parent reply	other threads:[~2010-08-04  5:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-01 19:58 Figuring out devnodes from a usb device Felipe Balbi
2010-08-02 22:29 ` Greg KH
2010-08-03  7:28 ` Felipe Balbi
2010-08-03  9:13 ` Kay Sievers
2010-08-03 19:53 ` Greg KH
2010-08-03 20:20 ` Felipe Balbi
2010-08-03 20:32 ` Greg KH
2010-08-04  5:09 ` Felipe Balbi [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=4C58F616.1090201@felipebalbi.com \
    --to=me@felipebalbi.com \
    --cc=linux-hotplug@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).