Hi,

I'm attempting to develop some support for SMSC USB controllers.   
I'm using the kernel version 2.4.20 and the usb-skeleton driver to attempt 
code some new USB drivers.  I have attached the USB and I see it
on the bus however, when I try to attach a device driver to the device,
I don't see the device I expect. 

usb.c: USB device 3 (vend/prod 0x424/0xdad) is not claimed by any active 
driver.

The device vendor/product id is 0x424/0xdad.  However, when I insert my
module using insmod, I don't see this device.  I only see the device 
0x1000/0x201 (which doesn't exist!).  This device doesn't appear in the 
/proc/bus/usb/devices.

usb-skeleton.c: USBSkeleton USB device 3 (vend/prod 0x1000/0x201)

/proc/bus/usb/devices looks like:
...

P:  Vendor=0424 ProdID=0dad Rev=10.00
S:  Manufacturer=SMSC
S:  Product=USB DataPump
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E:  Ad=81(I) Atr=03(Int.) MxPS=  64 Ivl=127ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms

Any ideas as to what I'm doing wrong?   If it matters, I'm using Red Hat 
linux.  I've verified the device is there with lsusb and I can extract 
detail information about it.  

Thanks in advance,
jeff




_____________________________________________________
Jeffrey McDonald, University of Pittsburgh [EMAIL PROTECTED]
100 Allen Hall                             office: 412-624-9056 
3941 O'Hara St.                            lab:    412-624-9160
Dept. of Physics and Astronomy             fax:    412-624-9163
University of Pittsburgh   
Pittsburgh, PA 15260



-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to