From mboxrd@z Thu Jan 1 00:00:00 1970 From: Enrico Mioso Subject: Re: Is this 32-bit NCM? Date: Mon, 1 Dec 2014 22:11:39 +0100 (CET) Message-ID: References: <87ppc957h1.fsf@nemi.mork.no> <874mtl55ar.fsf@nemi.mork.no> <87ppc71xne.fsf@nemi.mork.no> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: =?ISO-8859-15?Q?Bj=F8rn_Mork?= , Alex Strizhevsky , ShaojunMidge.Tan@audiocodes.com, youtux@gmail.com, linux-usb@vger.kernel.org, netdev@vger.kernel.org, Eli.Britstein@audiocodes.com To: Mingying.Zhu@audiocodes.com Return-path: Received: from mail-wi0-f180.google.com ([209.85.212.180]:34088 "EHLO mail-wi0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932112AbaLAVLK (ORCPT ); Mon, 1 Dec 2014 16:11:10 -0500 In-Reply-To: <87ppc71xne.fsf@nemi.mork.no> Sender: netdev-owner@vger.kernel.org List-ID: So ... I have two ideas left for now. We know for sure the problem is in the way we TX frames, not the way we RX them (the way we send, generate them, not the way we receive them). Si I have two ideas, and I ask for help from the Linux-usb mailing list for this first one. 1 - Does a wayexist to "replay" traffic crom a usb capture? We might try to take the usb frames generated by Windows, and send them to the device to see if there is any reaction. It should not be science fiction, I saw them do that in the eciadsl old project. 2 - The huawei ndis driver: does it work with these devices? It should be a little bit out-dated now (at least in terms of dates, it might work as well): the code is A LOT but, just in case, to see if there is any chances it'll work. It remains to be seen in which kernels it can actually compile again. If this works we might analyse what's happening and try to debug this out. But I really would like this to work in the cdc_ncm driver + huawei_cdc_ncm. Thank you.