On Wed, 20 Jan 2010, KIYOHARA Takashi wrote: > > also - should this value reflect the real length (including the pad)? eg > > data stream: > > I know, DTL operates following packet format. > In acldata case: > > { > { > uint8 type; > uint8 rsvd; > uint16 len; > } NOKIA DTL header; > > { > uint16_t con_handle; > uint16_t length; > }; > > { > data ... > }; > > [uint8_t pad;] /* need, if len is odd. */ > } > > NOKIA DTL parses little-endian. And operates each 2bytes/word. When > the length of data is an odd byte because headers are four bytes always, > padding is necessary.
Ok - my question is, for a 5 byte ACL packet: 82 00 09 00 01 00 05 00 aa bb cc dd ee 00 ^^^^^ [........................] or 82 00 0a 00 01 00 05 00 aa bb cc dd ee 00 ^^^^^ [...........................] ? I think the second (but I did not design the NOKIA DTL-1 device :) iain