"Stojsavljevic, Zoran" <zoran.stojsavljevic@xxxxxxxxx> writes: > Hello to everyone, > > Basically, my problem addresses this site: > http://www.linux-usb.org/usbtest/ > > Network Tests (Linux 2.6 and MS-Windows USB Hosts) > __________________________________________ > When Gadget Zero is basically working, you should start > using Ethernet style testing also, the g_ether gadget driver. > That normally uses CDC Ethernet to talk to hosts, and will > cover important code paths that won't be addressed using > "usbtest". Specifically, transfers go in both directions > concurrently; they use queue depths greater than one; > and the rates at which requests enter and leave the > queues vary considerably more. (Races will show up a > lot more readily!) > > I am pinging from the host target, and I see ARP requests > Coming to target (properly dequeued from ep1out (all > 42 bytes correct), but I do not see any messages coming > to RNDIS, especially to f-n skb_pull(skb, ...). See below. > I have both loaded cdc_ether and cdc_subset drivers, > And I assume that this is wrong! > > So, what should I disable in menuconfig in USB gadget > framework so I do not see anymore cdc_subset driver? This I have absolutely no clue about. That is even less clue than usual :-) >> One question out of curiosity... I am trying to ping from host to >> target, and I see perfect ARP request coming to the target (all 42 >> octets as required). >> >> But I do not see any reply from the target. It seems to me, According >> what I am reading that something is very wrong configured in my >> menuconfig. >> >> I do not see any messages coming to RNDIS (as you have mentioned), >> especially to > skb_pull(skb, ...). >> >> I have in lsmod : >> Module Size Used by >> cdc_ether 9612 0 >> cdc_subset 3069 0 >> usbnet 28738 2 cdc_ether,cdc_subset >> mii 4310 1 usbnet >> >> And as outcome of cat /proc/bus/usb/devices >> >> T: Bus=02 Lev=02 Prnt=03 Port=00 Cnt=01 Dev#= 18 Spd=12 MxCh= 0 >> D: Ver= 2.00 Cls=02(comm.) Sub=00 Prot=00 MxPS=64 #Cfgs= 2 >> P: Vendor=0525 ProdID=a4a2 Rev= 3.27 >> S: Manufacturer=Linux 2.6.34.10-WR4.3.0.0_standard with max_udc >> S: Product=RNDIS/Ethernet Gadget >> C: #Ifs= 2 Cfg#= 2 Atr=c0 MxPwr= 2mA >> A: FirstIf#= 0 IfCount= 2 Cls=02(comm.) Sub=06 Prot=00 >> I: If#= 0 Alt= 0 #EPs= 0 Cls=02(comm.) Sub=02 Prot=ff Driver= >> I: If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver= >> E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms >> E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms Well, this is your RNDIS configuration (class 02, subclass 02, protocol ff), but it isn't currently active. >> C:* #Ifs= 2 Cfg#= 1 Atr=c0 MxPwr= 2mA >> I:* If#= 0 Alt= 0 #EPs= 0 Cls=02(comm.) Sub=06 Prot=00 Driver=(none) >> I: If#= 1 Alt= 0 #EPs= 0 Cls=0a(data ) Sub=00 Prot=00 >> Driver=cdc_subset >> I:* If#= 1 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 >> Driver=cdc_subset The active configuration uses the cdc_subset. I don't know this driver, but finding out what it expects from the target should be easy since the source is available. Bjørn -- 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
