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
On Mon, 18 Apr 2005, Mike Lee wrote:
> for example zero.c, it use bcdUSB 0x200 but if you do not set
> GADGET_DUALSPEED. it will not include the device_qualifier, this will
> mislead the host to ask for a descriptor which the device do not know
> and result in a protocol stall.
Like David Br
Dear Alan
> I thought you said you were debugging the controller driver. Why do you
> care what the gadget driver does?
>
> To answer your question: If a gadget driver doesn't support USB 2.0 --
> including GET_DEVICE_QUALIFIER -- then it shouldn't set bcdUSB to 0x0200.
>
for example zero
On Sunday 17 April 2005 8:10 am, Alan Stern wrote:
> On Sun, 17 Apr 2005, Mike Lee wrote:
>
> > When i debug between with my FC3 linux PC, i found that it keep
> > asking the device for the DEVICE_QUALIFIER descriptor which only
> > support in USB2.0 .I finally change all the gadget driver bcdUSB
On Sun, 17 Apr 2005, Mike Lee wrote:
> Hi all
> I am now porting controller driver to I.MX motorola ARM9 , i am a
> newbie to usb development. Please correct anything wrong.
>
> When i debug between with my FC3 linux PC, i found that it keep
> asking the device for the DEVICE_QUALIFIER descrip
