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.
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. 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". thank you guys, for the patience and time. Enrico -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
