public inbox for
 help / color / mirror / Atom feed
From: Chris Holgate <>
To: GaurangT <>
Subject: Re: Where is GET Descriptor in usb-stm32 code
Date: Sat, 13 Jun 2009 11:32:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

GaurangT wrote:

>          I am new for I want to develop hid driver using usb-stm32
> code and I cann't get anywhere code in GET Descriptor.

If you're writing a USB class driver you don't need to worry about
implementing descriptor handling since this is all taken care of by the
eCos USB framework and the low level driver.  All you need to do is
provide a suitable set of descriptors as described in the documentation

The STM32 driver also uses this information to automatically set up its
endpoint configuration so even that is taken care of for you.

> Anyone know about hid driver plz help me.

I've not really looked at the HID specs.  It sounds like you'll need to
spend a bit of time looking at the official specs and working out what
endpoint configuration is required for your application before starting
to fill in the descriptor tables for your class driver.  While debugging
my descriptor setup I found it useful to use a Linux box and check the
kernel logs (type 'dmesg') since the Linux kernel driver helpfully
reports the descriptor information.


      reply	other threads:[~2009-06-13 11:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-13  9:22 GaurangT
2009-06-13 11:32 ` Chris Holgate [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).