From: Gustavo Padovan <padovan@profusion.mobi>
To: Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCHv2 2/5] Bluetooth: EWS: l2cap extended control field support
Date: Thu, 6 Oct 2011 15:19:59 -0300 [thread overview]
Message-ID: <20111006181959.GG5652@joana> (raw)
In-Reply-To: <1316180379-31607-3-git-send-email-Andrei.Emeltchenko.news@gmail.com>
Hi Andrei,
* Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com> [2011-09-16 16:39:36 +0300]:
> /* L2CAP Supervisory Function */
> -#define L2CAP_SUPER_RCV_READY 0x0000
> -#define L2CAP_SUPER_REJECT 0x0004
> -#define L2CAP_SUPER_RCV_NOT_READY 0x0008
> -#define L2CAP_SUPER_SELECT_REJECT 0x000C
> +#define L2CAP_SUPER_RR 0x00
> +#define L2CAP_SUPER_REJ 0x01
> +#define L2CAP_SUPER_RNR 0x02
> +#define L2CAP_SUPER_SREJ 0x03
>
> /* L2CAP Segmentation and Reassembly */
> -#define L2CAP_SDU_UNSEGMENTED 0x0000
> -#define L2CAP_SDU_START 0x4000
> -#define L2CAP_SDU_END 0x8000
> -#define L2CAP_SDU_CONTINUE 0xC000
> +#define L2CAP_SAR_UNSEGMENTED 0x00
> +#define L2CAP_SAR_START 0x01
> +#define L2CAP_SAR_END 0x02
> +#define L2CAP_SAR_CONTINUE 0x03
I want a separate patch of these macro renames. This patch is already big.
>
> /* L2CAP Command rej. reasons */
> -#define L2CAP_REJ_NOT_UNDERSTOOD 0x0000
> -#define L2CAP_REJ_MTU_EXCEEDED 0x0001
> -#define L2CAP_REJ_INVALID_CID 0x0002
> -
> +#define L2CAP_REJ_NOT_UNDERSTOOD 0x0000
> +#define L2CAP_REJ_MTU_EXCEEDED 0x0001
> +#define L2CAP_REJ_INVALID_CID 0x0002
>
> /* L2CAP structures */
> struct l2cap_hdr {
> @@ -150,6 +168,11 @@ struct l2cap_hdr {
> __le16 cid;
> } __packed;
> #define L2CAP_HDR_SIZE 4
> +#define L2CAP_ENHANCED_HDR_SIZE 6
> +#define L2CAP_EXTENDED_HDR_SIZE 8
Use ENH and EXT instead.
> +
> +#define L2CAP_FCS_SIZE 2
> +#define L2CAP_SDULEN_SIZE 2
A separate patch for this 4 new macros as well.
Gustavo
next prev parent reply other threads:[~2011-10-06 18:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 13:39 [PATCHv2 0/5] EWS: extended window size and extended control field support Emeltchenko Andrei
2011-09-16 13:39 ` [PATCHv2 1/5] Bluetooth: EWS: extended window size option support Emeltchenko Andrei
2011-10-06 18:05 ` Gustavo Padovan
2011-10-07 10:33 ` Emeltchenko Andrei
2011-10-07 20:26 ` Gustavo Padovan
2011-10-10 8:02 ` Emeltchenko Andrei
2011-09-16 13:39 ` [PATCHv2 2/5] Bluetooth: EWS: l2cap extended control field support Emeltchenko Andrei
2011-10-06 18:19 ` Gustavo Padovan [this message]
2011-09-16 13:39 ` [PATCHv2 3/5] Bluetooth: EWS: support extended seq numbers Emeltchenko Andrei
2011-09-16 13:39 ` [PATCHv2 4/5] Bluetooth: EWS: remove magic numbers in l2cap Emeltchenko Andrei
2011-09-16 13:39 ` [PATCHv2 5/5] Bluetooth: EWS: fix max_pdu calculation Emeltchenko Andrei
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111006181959.GG5652@joana \
--to=padovan@profusion.mobi \
--cc=Andrei.Emeltchenko.news@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).