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 [off-list ref]
==To: Enrico Mioso [off-list ref]
==Cc: Kevin Zhu [off-list ref],
==    Eli Britstein [off-list ref],
==    Alex Strizhevsky [off-list ref],
==    Midge Shaojun Tan [off-list ref],
==    "youtux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" [off-list ref],
==    "linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" [off-list ref],
==    "netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" [off-list ref]
==Subject: Re: Is this 32-bit NCM?
==
==Enrico Mioso [off-list ref] 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
==