From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30295 invoked by alias); 13 Jun 2009 11:32:13 -0000 Received: (qmail 30285 invoked by uid 22791); 13 Jun 2009 11:32:12 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_32,SPF_PASS X-Spam-Check-By: sourceware.org Received: from alicia.2020media.com (HELO alicia.2020mail.com) (212.124.192.215) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 13 Jun 2009 11:31:59 +0000 Received: from [212.124.199.38] (helo=[192.168.0.2]) by alicia.2020mail.com with esmtp (Exim 4.30; FreeBSD) id 1MFRSS-0003FV-Jh; Sat, 13 Jun 2009 12:31:36 +0100 Message-ID: <4A338E28.2070108@zynaptic.com> Date: Sat, 13 Jun 2009 11:32:00 -0000 From: Chris Holgate User-Agent: Thunderbird 2.0.0.19 (X11/20081227) MIME-Version: 1.0 To: GaurangT CC: ecos-devel@ecos.sourceware.org Subject: Re: Where is GET Descriptor in usb-stm32 code References: <24010714.post@talk.nabble.com> In-Reply-To: <24010714.post@talk.nabble.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2009-06/txt/msg00022.txt.bz2 GaurangT wrote: > I am new for usb.so 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 here: http://ecos.sourceware.org/docs-latest/ref/usbs-enum.html 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. Chris.