[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [bluetooth-dev] doubt on rfcomm



Hi,

It is for removing the RFCOMM header (maximum 4 bytes) plus the RFCOMM checksum (1 byte).

By the way, the L2CAP header is just 4 bytes ;-)

Best Regards

Mats Fridén

Axis Communications

>-----Original Message-----
>From: sarita [mailto:sarita@xxxxxxx.com]
>Sent: Tuesday, January 16, 2001 8:11 PM
>To: bluetooth-dev@xxxxxxx.com
>Subject: [bluetooth-dev] doubt on rfcomm
>
>
>hello,
>
>In rfcomm_receive_data()  ...case SABM ...during negotiation of MTU why
>is it l2cap->remote_mtu-5.. is it to remove the l2cap header?? if so it
>why is it 5 instead of l2cap header size of 6.
>
>sarita
>
>-
>To unsubscribe from this list: send the line "unsubscribe 
>bluetooth-dev" in
>the body of a message to majordomo@xxxxxxx.com
>
-
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com