From: <dongzai007@sohu.com>
To: <linux-kernel@vger.kernel.org>
Subject: Re: vid&pid problems in usb_probe()
Date: Sat, 8 May 2004 17:05:24 +0800 (CST) [thread overview]
Message-ID: <2512736.1084007124337.JavaMail.postfix@mx0.mail.sohu.com> (raw)
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.
----- 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) <dongzai007@sohu.com> 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.
>
> --
> ~Randy
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2004-05-08 9:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-08 9:05 dongzai007 [this message]
2004-05-08 17:25 ` vid&pid problems in usb_probe() Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2004-05-09 2:03 dongzai007
2004-05-09 2:16 ` Greg KH
2004-05-08 3:48 dongzai007
2004-05-08 4:45 ` Randy.Dunlap
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=2512736.1084007124337.JavaMail.postfix@mx0.mail.sohu.com \
--to=dongzai007@sohu.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.