hi,
thanks for the info. But i get similar errors if tried
with /proc/bus/usb path also. I am sending you the
outputs. 
Can you please suggest me a method to use the test
cases using usb-serial cable?

~ #
~ # cat /proc/bus/usb/devices

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1
Spd=12  MxCh= 2
B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8
#Cfgs=  1
P:  Vendor=0000 ProdID=0000 Rev= 2.06
S:  Manufacturer=Linux 2.6.11.11 ohci_hcd
S:  Product=S3C24XX OHCI
S:  SerialNumber=s3c24xx
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00
Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  3
Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8
#Cfgs=  1
P:  Vendor=067b ProdID=2303 Rev= 2.02
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00
Driver=pl2303
E:  Ad=81(I) Atr=03(Int.) MxPS=  10 Ivl=1ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=83(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
/etc/usb-test # insmod usbtest.ko vendor=0x067b
product=0x2303
Using usbtest.ko
usbcore: registered new driver usbtest
/etc/usb-test # lsmod
Module                  Size  Used by    Not tainted
usbtest 21100 0 - Live 0xbf000000
/etc/usb-test # ./testusb -D /proc/bus/usb/001/003
./testusb: /proc/bus/usb/001/003 may see only control
tests
/proc/bus/usb/001/003 test 0 --> 25 (error 25)
/proc/bus/usb/001/003 test 1 --> 25 (error 25)
/proc/bus/usb/001/003 test 2 --> 25 (error 25)
/proc/bus/usb/001/003 test 3 --> 25 (error 25)
/proc/bus/usb/001/003 test 4 --> 25 (error 25)
/proc/bus/usb/001/003 test 5 --> 25 (error 25)
/proc/bus/usb/001/003 test 6 --> 25 (error 25)
/proc/bus/usb/001/003 test 7 --> 25 (error 25)
/proc/bus/usb/001/003 test 8 --> 25 (error 25)
/proc/bus/usb/001/003 test 9 --> 25 (error 25)
/proc/bus/usb/001/003 test 10 --> 25 (error 25)
/proc/bus/usb/001/003 test 11 --> 25 (error 25)
/proc/bus/usb/001/003 test 12 --> 25 (error 25)
/proc/bus/usb/001/003 test 13 --> 25 (error 25)
/proc/bus/usb/001/003 test 14 --> 25 (error 25)
/proc/bus/usb/001/003 test 15 --> 25 (error 25)
/proc/bus/usb/001/003 test 16 --> 25 (error 25)
/proc/bus/usb/001/003 test 17 --> 25 (error 25)
/proc/bus/usb/001/003 test 18 --> 25 (error 25)
/proc/bus/usb/001/003 test 19 --> 25 (error 25)
/proc/bus/usb/001/003 test 20 --> 25 (error 25)
/proc/bus/usb/001/003 test 21 --> 25 (error 25)
/proc/bus/usb/001/003 test 22 --> 25 (error 25)
/proc/bus/usb/001/003 test 23 --> 25 (error 25)
/proc/bus/usb/001/003 test 24 --> 25 (error 25)
/proc/bus/usb/001/003 test 25 --> 25 (error 25)
/proc/bus/usb/001/003 test 26 --> 25 (error 25)
/proc/bus/usb/001/003 test 27 --> 25 (error 25)
/proc/bus/usb/001/003 test 28 --> 25 (error 25)
/proc/bus/usb/001/003 test 29 --> 25 (error 25)

Please suggest as what shal be the fix so that
testcases 9 and 10  execute well on with this cable..?

Regards
:-)


--- [EMAIL PROTECTED] wrote:

> > /etc/usb-test # ./testusb -D /dev/usb/tts/0
> > ./testusb: /dev/usb/tts/0 may see only control
> tests
> > /dev/usb/tts/0 test 0 --> 22 (error 22)
> > ... etc
> 
> You need to pass a /proc/bus/usb/... path.
> 
> - Dave
> 
> 



                
____________________________________________________
Start your day with Yahoo! - make it your home page 
http://www.yahoo.com/r/hs 
 


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to