On Tuesday 19 April 2005 7:12 pm, mike lee wrote: > Hi all > I am now writing a gadget controller driver, but face some problem > when the driver still in enumeration. > Here is what i get from the host, it is very strange that my hardware > only support 2 configuration, so don't know why can't set config #3.
Is it insisting on particular numbers for those configurations? Hardware shouldn't really stick its nose into driver policy issues, but not all hardware designers have gotten the message. > Also, my hardware auto reply set configuration request to the host > without software control, this confuses some gadget driver(at least > file_storage) that it does not config completely. Could i just add a > self-made set configuration request when gadget driver register. Yes, some drivers do that already. Though it may be best to wait until the host resets the peripheral. (And how are you going to know _which_ configuration to report?) > It is difficult to debug before bus enumeration, Is there any method > to debug more efficient? Getting enumeration to work is the first major milestone of getting a new controller driver up -- and the most frustrating one. There are no good shortcuts there, sorry. Make sure you can produce packet-level tracing from your driver (or at least something very close to it), and either use a USB sniffer (CATC or equivalent) or be familiar with what the host side software is putting out a bit more directly. :) - Dave ------------------------------------------------------- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
