On Tue, Aug 19, 2014 at 09:36:19AM -0500, Felipe Balbi wrote: > On Tue, Aug 19, 2014 at 10:27:39PM +0800, Peter Chen wrote: > > On Tue, Aug 19, 2014 at 06:05:27PM +0800, Xuebing Wang wrote: > > > > > > On 08/19/2014 12:58 PM, Peter Chen wrote: > > > >>My environment is Freescale i.MX6SL EVK board (as USB peripheral device), > > > >>which is based on kernel 3.10.17. i.MX6SL uses ChipIdea dual-role > > > >>controller. > > > >> > > > >>My problem is that gadget drivers g_ether and g_audio (UAC1 enabled) can > > > >>NOT be detected by Windows 7 natively, while g_mass_storage, g_serial, > > > >>g_hid can be detected by Windows 7 natively. > > > >> > > > >>1) I found that both Ether and USB Audio uses .bAlternateSetting, while > > > >>Mass Storage, Serial and HID do NOT. I am wondering if this is related to > > > >>how Gadget framework handles USB_REQ_SET_INTERFACE request? > > > >> > > > >If possible, would you use Linux PC or Mac OS (macbook pro+) to test? > > > >>From my previous experiences, g_audio works not well with windows. > > > > > > Thanks Peter. g_audio is now working with Ubuntu and MacOS host, but > > > can NOT get detected by Windows 7. > > > > > > I am not sure if this Windows 7 detection issue is not specific to > > > g_audio (UAC1), because Windows can NOT natively detect g_ether > > > (even with RNDIS CONFIG_USB_ETH_RNDIS=y enabled). > > > > > > Also, in file f_rndis.c, it says "/* Some controllers can't support > > > RNDIS ... */", I am not sure what does this mean. Does it mean > > > possibly controller like ChipIdea does NOT support RNDIS? > > > > > > > RNDIS is software stuff, isn't it? > > it probably means that some HW configuration doesn't have enough > endpoints, or doesn't support a certain transfer type ;-) > Thanks, so Xunbing, the imx6 hardware (chipidea core) have 8 endpoints, and support all four transfer type, it should be no problem to support RNDIS. -- Best Regards, Peter Chen -- 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
