Hi David, > It seems logical to me that what the chip does is align up the total > sub-packet length to a multiple of 4 or larger, and then add those two > prefix padding bytes. Otherwise the prefix padding won't necessarily > and reliably align the IP header after the link level header. Yep, that makes sense, and is what the driver is currently doing; between clustered packets, the header is aligned (up) to 8 bytes, then the 2-byte padding is added to that. For this change, I have assumed that the packet length behaviour (ie, describing the un-padded length) is consistent between clustered packets. [If you have any hints for forcing clustered packets, I'll see if I can probe the behaviour a little better to confirm] Cheers, Jeremy
