Thank you very much Bjorn. On Tue, 2 Dec 2014, Bjørn Mork wrote: ==Date: Tue, 2 Dec 2014 14:37:03 ==From: Bjørn Mork <bjorn@xxxxxxx> ==To: Enrico Mioso <mrkiko.rs@xxxxxxxxx> ==Cc: Kevin Zhu <Mingying.Zhu@xxxxxxxxxxxxxx>, == Eli Britstein <Eli.Britstein@xxxxxxxxxxxxxx>, == Alex Strizhevsky <alexxst@xxxxxxxxx>, == Midge Shaojun Tan <ShaojunMidge.Tan@xxxxxxxxxxxxxx>, == "youtux@xxxxxxxxx" <youtux@xxxxxxxxx>, == "linux-usb@xxxxxxxxxxxxxxx" <linux-usb@xxxxxxxxxxxxxxx>, == "netdev@xxxxxxxxxxxxxxx" <netdev@xxxxxxxxxxxxxxx> ==Subject: Re: Is this 32-bit NCM? == ==Enrico Mioso <mrkiko.rs@xxxxxxxxx> writes: == ==> ... but out of curiosity: are NCM specs allowing to change order of things in ==> the package or not? ==> This is not to start philosofical falames or something, but to understand ==> better how things work. And, if they do: how much arbitrarily? == ==Only the NTB header has a fixed location. The rest can be anywhere and ==in any order. Quoting from section 3 Data Transport: == == "Within any given NTB, the NTH always must be first; but the other == items may occur in arbitrary order." == == ==Bjørn ==
