> >> Actually, I'm still struggling in a bug similar with this one on Blackfin. > >> We ran following testcase 100 times, 10-20 times tastcases failed. > >> > >> --- > >> $ ./testusb -D /proc/bus/usb/005/012 -t14 -c 15000 -s 256 -v 1 > >> unknown speed /proc/bus/usb/005/012 > >> /proc/bus/usb/005/012 test 14 --> 75 (Value too large for defined data type) > >> --- > >> > >> I reported this bug to our hardware designer and the omap list. Felipe > >> said he did met this issue. > >> From the capture data of USB analyzer, the peripheral musb sent out > >> garbage data in the IN-STATUS stage. > >> In that stage, the DATA length should be zero. But the peripheral sent > >> out 1 byte or 2 bytes sometimes. > >> > >> Thanks > >> -Bryan > > > > Hi Bryan, > > > > Could you tell me if you're using Indexed Mode or Flat mode? > > > > I'll try this out on my boards and see what I get. > > > > I tried both mode, the result is same as mentioned. Typically, we use > Flat mode on Blackfin. Tried this with current linux-omap kernel. Works fine on the OMAP3430. Guess that doesn't help much. - Anand -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
