On Thu, 4 Aug 2005, Nitin Mahajan wrote:

> --- Alan Stern <[EMAIL PROTECTED]> wrote:
> 
> > On Wed, 3 Aug 2005, Nitin Mahajan wrote:
> > 
> > > Hello !
> > > 
> > >   I want to use the Linux USB subsystem along with
> > the
> > > OHCI, HID, and Device class printer drivers,
> > Storage
> > > drivers for memory stick into my kernel.
> > > 
> > > For this I wanted to test all these drivers which
> > are
> > > already available in the Linux kernel. Could u
> > please
> > > tell me what would be the best way to test the
> > core
> > > driver , HID driver and the Device class printer
> > > driver.
> > 
> > The best way to test them depends on what you want
> > to learn.  If all you 
> > care about is whether the drivers are free of bugs,
> > then I can save you 
> > some trouble: The drivers _do_ have bugs.
> 
> But could u please tell me how to unearth these bugs
> in the above drivers or how really one should go about
> these drivers if they are going to be a part of a
> product?

The same way you would test for bugs in any driver -- by trying to use the 
drivers in many different situations and with various stress programs.

The topic of software reliability testing is extremely broad, and you're
not going to get good answers to your questions on a mailing list.  To put
it another way, how would you test drivers written by Microsoft?  You can
use the same sorts of tests with Linux drivers.

> > > For testing the HC driver I am planning to use the
> > > test driver mentioned at
> > > http://www.linux-usb.org/usbtest/. However these
> > tests
> > > do not seem to test the core driver completely but
> > > only the host side support from the core driver.
> > 
> > That's because the core driver only supports hosts. 
> 
> U mean the core driver does not support the devices ,
> or peripherals or other USB drivers on the other side?

I'm not sure exactly what you mean by "the core driver"; that's not a
standard term.  From what you wrote above, it looks like you want "core
driver" to mean the same thing as "HC driver".  What I meant was: The
ohci-hcd HC driver does not drive peripheral controllers, it only
drives host controllers.  If you had a computer with both a USB host 
controller and a USB device controller, ohci-hcd would manage only the 
host controller.  You would need to load another driver to manage the 
device controller.

What you said about usbtest isn't correct.  Along with testing the
host-side support in the HC driver, it also tests the device-side support
in the peripheral.  The tests in usbtest will succeed only if both the
host and the peripheral are working properly.

There are other drivers in the Linux kernel that do support peripheral
controllers and that can act as USB peripheral class drivers.  However you
did not mention these other drivers in your original message, so I assumed
you weren't interested in them.

Alan Stern



-------------------------------------------------------
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

Reply via email to