From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263842AbUEHR1m (ORCPT ); Sat, 8 May 2004 13:27:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263893AbUEHR1m (ORCPT ); Sat, 8 May 2004 13:27:42 -0400 Received: from fw.osdl.org ([65.172.181.6]:59548 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S263842AbUEHR1i (ORCPT ); Sat, 8 May 2004 13:27:38 -0400 Date: Sat, 8 May 2004 10:25:34 -0700 From: "Randy.Dunlap" To: Cc: linux-kernel@vger.kernel.org Subject: Re: vid&pid problems in usb_probe() Message-Id: <20040508102534.11951d7d.rddunlap@osdl.org> In-Reply-To: <2512736.1084007124337.JavaMail.postfix@mx0.mail.sohu.com> References: <2512736.1084007124337.JavaMail.postfix@mx0.mail.sohu.com> Organization: OSDL X-Mailer: Sylpheed version 0.9.8a (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 8 May 2004 17:05:24 +0800 (CST) wrote: | Thank you for replying,but I don't know what you mean, | USB descriptor data structure is defined in | "/usr/include/linux/usb.h" | | my kernel version is 2.4.18. Are you saying that your driver uses /usr/include/linux/usb.h ? If so, that's wrong. It should use linux-2.4.18/include/linux/usb.h instead, and it will if you build/make the driver correctly. So, how do you build this driver? Show the Makefile or command line that you use. Regarding the data structure, I don't know what /usr/include/linux/usb.h on your system contains since that is not a kernel header file (and drivers shouldn't use those). I do recall, however, that many moons ago, there were some usb structs in usb.h that were not defined with __attribute__((packed)), and that could cause field offsets to be off a bit, er, byte (or more). And what processor arch. are you doing this on? Driver source code? ~Randy | ----- Original Message ----- | From: Randy.Dunlap | To: dongzai007@sohu.com | Cc: linux-kernel@vger.kernel.org | Subject: Re: vid&pid problems in usb_probe() | Sent: Sat May 08 12:45:54 CST 2004 | | > On Sat, 8 May 2004 11:48:44 +0800 (CST) wrote: | > | > | | > | | > | I am writting an usb driver.You know function usb_probe(...) is used to determine whether the usbdevices just pluged in is what the driver is for. | > | > a. Please learn to use the Enter/Return key around character position | > 70 (or before) on each line. | > | > b. what kernel version? (*always*) | > | > c. You should ask this on the linux-usb-development mailing list: | > linux-usb-devel@lists.sf.net | > | > | > | The Vid and Pid of my usb device are 0x1111 and 0x0000 respectively. | > | | > | the program is : | > | | > | static void* usb_probe(struct usb_device *udev, unsigned int ifnum, const struct usb_device_id *id) | > | { | > | .............. | > | .............. | > | | > | printk("<1>Vid:%x | Pid:%x | ",udev->descriptor.idVendor,udev->descriptor.idProduct); | > | | > | if ((udev->descriptor.idVendor!=0x1111) | > | ||(udev->descriptor.idProduct!=0x0000)) return NULL; | > | | > | .............. | > | } | > | | > | when I plug the device whose vid & pid is 0x1111 & 0x0000 respectively. | > | this Module displayed | > | | > | | > | Vid:0 | > | Pid:201 | > | | > | usb.c ........ no active driver for this device; | > | | > | and when I plug another device , I also got wrong vid & pid. | > | | > | But when I wrote program as below: | > | | > | __u16 tmp=0x1111; | > | printk("<1>%x",tmp); | > | | > | it can print "1111" on the screen. That means my syntax is correct. | > | I mean, the problem may be at the data transfered into function usb_probe() | > | Maybe data transfered into function usb_probe() is wrong. | > | | > | I wonder where is the problem, how can i solve. | > | > Seeing more (or all) of your source code could help. | > I'm especially curious (suspicious) about your USB descriptor data | > structures.