From mboxrd@z Thu Jan 1 00:00:00 1970 From: Enrico Mioso Subject: Re: [cdc_ncm] guidance and help refactoring cdc_ncm Date: Mon, 1 Jun 2015 14:08:26 +0200 (CEST) Message-ID: References: <20150601005917.GB5320@kroah.com> <1433144906.1557.2.camel@suse.com> <1433155778.1884.12.camel@suse.de> <1433160022.1884.18.camel@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: youtux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, Greg KH , linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Oliver Neukum Return-path: In-Reply-To: <1433160022.1884.18.camel-IBi9RG/b67k@public.gmane.org> Sender: linux-usb-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: netdev.vger.kernel.org On Mon, 1 Jun 2015, Oliver Neukum wrote: ==Date: Mon, 1 Jun 2015 14:00:22 ==From: Oliver Neukum ==To: Enrico Mioso ==Cc: youtux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, Greg KH , linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, == netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org ==Subject: Re: [cdc_ncm] guidance and help refactoring cdc_ncm == ==On Mon, 2015-06-01 at 13:41 +0200, Enrico Mioso wrote: ==> Thank you Oliver, thank you all for reading this thread and the attention. ==> For a more detailed discussion and how we got here, you might google for the ==> thread: ==> "Is this 32-bit NCM?" ==> and ==> "Is this 32-bit NCM?y" (follow up). ==> Where the "y" letter comes from a mistake of mine. == ==Having read them it looks like the issues of padding and ==sequence numbers are open. == ==> The specification does only mandate the position of the NTH (header). The rest ==> can be in any order and position in general. This will work with most devices: ==> except, of course, those from Huawei. == ==Indeed. And a redesign for crap devices looks like ==a bad idea. == ==> Our aggregate looks something like this from my perspective (anyone correct me ==> in case): ==> NTH: header ==> NDP: contains indexing informations ==> ethernet packet 1 ==> ethernet packet 2 ==> ... ==> ethernet packet n; ==> ==> While it should look like: ==> NTH: header ==> ethernet packet 1 ==> ethernet packet 2 ==> ... ==> ethernet packet n; ==> NDP: contains indexing informations ==> ==> but, when introducing such a change: you might break other devices now working. ==> Infact, clearly there are multiple vendors producing NCM device, as you might ==> also see by looking at the dirver's comments. ==> So in general, we should be able to dynamically change the way in which the ==> driver order things in the package. ==> and that's why I initially proposed the "redesign". == ==OK, so the NDP needs to be at the end. However in the old thread ==you state that this requires the NDP to be built between the ==final aggregate and physically transmitting. I think this is a false ==choice. You could just as well copy the NDP around provided you reserve ==enough space at the end of the skb. Yes, probably you can do so. I am not against anything at this moment. == == Regards == Oliver == == == == -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html