Hi,
thank you for info. I am still finding something
wrong in running th test cases. I have pasted the
output after each activity.
any fix for this error 22?
~ #
~ # 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 # tftp -g -r usbtest.ko 132.186.127.38
/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
/dev/console /dev/led0 /dev/port
/dev/root /dev/vc/
/dev/fb/ /dev/mem /dev/ptmx
/dev/scsi/ /dev/vcc/
/dev/full /dev/mtd/ /dev/pts/
/dev/tts/ /dev/zero
/dev/input/ /dev/mtdblock/ /dev/pty/
/dev/tty
/dev/kmem /dev/net/ /dev/random
/dev/urandom
/dev/kmsg /dev/null /dev/rd/
/dev/usb/
/etc/usb-test # ./testusb -D /dev/usb/
/dev/usb/hid/ /dev/usb/tts/
/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)
/dev/usb/tts/0 test 1 --> 22 (error 22)
/dev/usb/tts/0 test 2 --> 22 (error 22)
/dev/usb/tts/0 test 3 --> 22 (error 22)
/dev/usb/tts/0 test 4 --> 22 (error 22)
/dev/usb/tts/0 test 5 --> 22 (error 22)
/dev/usb/tts/0 test 6 --> 22 (error 22)
/dev/usb/tts/0 test 7 --> 22 (error 22)
/dev/usb/tts/0 test 8 --> 22 (error 22)
/dev/usb/tts/0 test 9 --> 22 (error 22)
/dev/usb/tts/0 test 10 --> 22 (error 22)
/dev/usb/tts/0 test 11 --> 22 (error 22)
/dev/usb/tts/0 test 12 --> 22 (error 22)
/dev/usb/tts/0 test 13 --> 22 (error 22)
/dev/usb/tts/0 test 14 --> 22 (error 22)
/dev/usb/tts/0 test 15 --> 22 (error 22)
/dev/usb/tts/0 test 16 --> 22 (error 22)
/dev/usb/tts/0 test 17 --> 22 (error 22)
/dev/usb/tts/0 test 18 --> 22 (error 22)
/dev/usb/tts/0 test 19 --> 22 (error 22)
/dev/usb/tts/0 test 20 --> 22 (error 22)
/dev/usb/tts/0 test 21 --> 22 (error 22)
/dev/usb/tts/0 test 22 --> 22 (error 22)
/dev/usb/tts/0 test 23 --> 22 (error 22)
/dev/usb/tts/0 test 24 --> 22 (error 22)
/dev/usb/tts/0 test 25 --> 22 (error 22)
/dev/usb/tts/0 test 26 --> 22 (error 22)
/dev/usb/tts/0 test 27 --> 22 (error 22)
/dev/usb/tts/0 test 28 --> 22 (error 22)
/dev/usb/tts/0 test 29 --> 22 (error 22)
/etc/usb-test # ./testusb -t 9 -D /dev/usb/tts/0
./testusb: /dev/usb/tts/0 may see only control tests
/dev/usb/tts/0 test 9 --> 22 (error 22)
/etc/usb-test # ./testusb -t 10 -D /dev/usb/tts/0
./testusb: /dev/usb/tts/0 may see only control tests
/dev/usb/tts/0 test 10 --> 22 (error 22)
Any inputs on how to continue testing ?
Regards
:-)
--- [EMAIL PROTECTED] wrote:
> > From [EMAIL PROTECTED] Tue Aug 2 02:34:36 2005
> > Date: Tue, 2 Aug 2005 02:30:01 -0700 (PDT)
> > From: driversbin driversbin <[EMAIL PROTECTED]>
> > Subject: Re: [linux-usb-devel] core driver testing
> > To: [EMAIL PROTECTED],
> [email protected]
> >
> > hi,
> >
> > thanks for the info.
> >
> > I am using usb-serial convertor having ftdi chip (
> > vendor id 0x067b and product id 0x2303).
> > How do i carry out these tests with that hardware.
> >
> > I tried to insmod the usbtest.ko using this vendor
> and
> > product id and by undefing generic in the
> usbtest.c
> > code.
> >
> > What chnages have to be done, for the testcases to
> > work for the usb-serial convertor?
>
> You'll only be able to do it for the "test9" and
> "test10"
> cases, but once you modified the kernel "usbtest" to
> grab
> that device, then just run userspace "testusb -D ...
> " to
> make it use that particular device.
>
> For tests specific to the serial functionality, I
> don't
> know what you'd use. Surely with all the serial
> lines
> in use on Linux, there are already programs written
> to
> kick the drivers in ways that maximize code
> coverage.
>
> - Dave
>
>
>
> > Regards
> > :-)
> >
> >
> > --- [EMAIL PROTECTED] wrote:
> >
> > > > I am testing my host controller driver using
> the
> > > > scripts in the Linux Usb test Page
> > > >
> (http://www.linux-usb.org/usbtest/index.html#hosts
> > > > )and the usbtest driver available in the
> kernel.
> > >
> > > Good.
> > >
> > > > Can i know to test host controller and core
> driver
> > > > exhaustively??
> > > >
> > > > I need to know to what extent it wil test the
> core
> > > > driver and are there any test cases that wil
> test
> > > > the USB core driver in specific,,?
> > >
> > > I'd like to see test coverage statistics. Why
> don't
> > > you run kernel profiling tools over the
> different
> > > tests and send us the results?
> > >
> > > - 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
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
