On 1/19/09, David Brownell <david-b@xxxxxxxxxxx> wrote: > On Monday 19 January 2009, Mandeep Sandhu wrote: >> So where do I look now? Is something failing or is it a case of >> misconfiguration >> where the Host is not able to send packets over the link? > > Looks like it's pure host-side debugging from now on ... which we > can't much help with, since it's not a Linux host. I forgot to mention one more log message that comes after the enumeration: usb0: high speed config #1: 100 mA, Ethernet Gadget, using CDC Ethernet musb_stage2_irq 820: SUSPEND (b_peripheral) devctl 99 power f0 usb0: suspend Why does it go into suspend mode? Is it because there's no bus activity and it goes into this state for power-saving? Is this expected behavior? > > The only clue would seem to be those comments you made about the > host only supporting a single CDC Ethernet implementation, with > specific endpoint assignments. That's sloppy and stupid coding, > but you should be able to hack the Linux code so it makes the same > assignments ... purely as a workaround for the host bug, whereby > it's ignoring the descriptors provided by the peripheral. I have the Linux Host-side driver for this very chip with me (given by the vendor)...will that help in debugging the problem further?? Like, can it help explain how the host might be interpreting the EP descriptors that the ether gadget driver is sending while enumerating? Thanks again, -mandeep > > - Dave > -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
