Re: btuart and SOCKET Bluetooth CF

[KIYOHARA Takashi <kiyohara%kk.iij4u.or.jp@localhost>]

Hi! all,


From: Iain Hibbert <plunky%rya-online.net@localhost>
Date: Wed, 20 Jan 2010 11:11:21 +0000 (GMT)

> On Wed, 20 Jan 2010, Iain Hibbert wrote:
> 
> > 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 :)
> 
> further to this, on your input path
> 
> +     case BTUART_RECV_DTL_ACL_DATA:  /* ACL Packet Complete */
> +             if (dtlh->len & 0x0001)
> +                     m_adj(m, -1);
> 
> this seems to be incorrect logic..  in the first case, it will chop a
> valid byte and in the second it will not chop the pad byte.

The com(4) port is sequentially transferred by one byte though NOKIA DTL
treats 2byte/word.

                          COM port
   com@pcmcia <-------------------------------- NOKIA DTL
               0x82 rsvd lenL lenH ... dd ee 00

Thanks,
--
kiyohara