Thank you Oliver for the reply. On Mon, 1 Jun 2015, Oliver Neukum wrote: ==Date: Mon, 1 Jun 2015 09:48:26 ==From: Oliver Neukum <oneukum@xxxxxxxx> ==To: Enrico Mioso <mrkiko.rs@xxxxxxxxx> ==Cc: Greg KH <greg@xxxxxxxxx>, linux-usb@xxxxxxxxxxxxxxx, == netdev@xxxxxxxxxxxxxxx, youtux@xxxxxxxxx ==Subject: Re: [cdc_ncm] guidance and help refactoring cdc_ncm == ==On Mon, 2015-06-01 at 08:53 +0200, Enrico Mioso wrote: == ==> A 32-bit version of the driver (talking 32-bit NCM) is here: ==> http://www.gstorm.eu/cdc_ncm.c ==> I modified the original driver with the help of a very talented friend. ==> It works: but there seem to be no real reasons to implement this properly. We ==> did this in a consistent effort to understand what was wrong, and here it is. == ==Well, you are really talking about two different things here. ==Do we ever fail because we only do 16 bit as opposed to 32 bit? ==Your 32 bit driver looks good, but it raises the question of what to do ==if this test: == == if (le16_to_cpu(ctx->ncm_parm.bmNtbFormatsSupported) & == USB_CDC_NCM_NTB32_SUPPORTED) { == ==fails. Otherwise it looks ready for merging. == == Regards == Oliver == == == == Oh - I am sorry. Infact, I am taling about two different things here. No, I've seen no device failing because of this (16 vs. 32 bit problem). I was mentioning this only as an additional thing to consider, at least from my side. We are failing on some cases only because of the position we put the NDP part of the NCM frame. Infact, this 32-bit driver will work when the 16 bit one does, and fail when the 16 bit one does. Thank you for your review and consideration. It would be nice to see this code merged - but I think we might need to merge the two drivers in a way that reduces code de-duplication. But this might be work for a second take in case. Thank you again, Enrico -- 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
