From: Marcel Holtmann <marcel@holtmann.org>
To: Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCHv3 2/4] add fixed channel definitions
Date: Mon, 17 Oct 2011 08:29:26 -0700 [thread overview]
Message-ID: <1318865368.15441.94.camel@aeonflux> (raw)
In-Reply-To: <1318839662-13609-3-git-send-email-Andrei.Emeltchenko.news@gmail.com>
Hi Andrei,
> lib/l2cap.h | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/lib/l2cap.h b/lib/l2cap.h
> index 47b3dc3..3880551 100644
> --- a/lib/l2cap.h
> +++ b/lib/l2cap.h
> @@ -139,6 +139,11 @@ struct l2cap_conninfo {
>
> #define L2CAP_SDULEN_SIZE 2
>
> +/* L2CAP fixed channels */
> +#define L2CAP_FC_L2CAP 0x02
> +#define L2CAP_FC_CONNLESS 0x04
> +#define L2CAP_FC_A2MP 0x08
> +
please get these added to bluez.git first and then send exactly the same
patch to add them here (once accepted).
Also please add also LE, LE signaling, AMP test manager as well. Just
make sure the list is complete according to 4.0 specification and
assigned numbers list.
Regards
Marcel
next prev parent reply other threads:[~2011-10-17 15:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 8:20 [PATCHv3 0/4] decode fixed channels Emeltchenko Andrei
2011-10-17 8:20 ` [PATCHv3 1/4] add btohll macro Emeltchenko Andrei
2011-10-17 15:32 ` Marcel Holtmann
2011-10-17 8:21 ` [PATCHv3 2/4] add fixed channel definitions Emeltchenko Andrei
2011-10-17 15:29 ` Marcel Holtmann [this message]
2011-10-17 8:21 ` [PATCHv3 3/4] add 64 bit get_val support Emeltchenko Andrei
2011-10-17 15:31 ` Marcel Holtmann
2011-10-18 6:33 ` Emeltchenko Andrei
2011-10-18 15:53 ` Marcel Holtmann
2011-10-19 7:59 ` Emeltchenko Andrei
2011-10-19 15:59 ` Marcel Holtmann
2011-10-17 8:21 ` [PATCHv3 4/4] decode fixed channel list info rsp 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=1318865368.15441.94.camel@aeonflux \
--to=marcel@holtmann.org \
--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).