linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] monitor: Improbe decoding of ATT Read by Group Type Respose
Date: Sun, 24 May 2015 18:32:43 +0300	[thread overview]
Message-ID: <20150524153243.GA20254@t440s> (raw)
In-Reply-To: <1432473311-16657-1-git-send-email-luiz.dentz@gmail.com>

Hi Luiz,

On Sun, May 24, 2015, Luiz Augusto von Dentz wrote:
> The group data is as follow:
> 
> Attribute Handle (2 octets) End Group Handle (2 octets) Attribute Value
> (Length - 4) octets
> 
> But since only primary and secondary can be used in ATT Read by Group
> Type Request the value is garanteed to be a UUID:
> 
> < ACL Data TX: Handle 3585 flags 0x00 dlen 24
>       ATT: Read By Group Type Response (0x11) len 19
>         Attribute data length: 6
>         Attribute group list: 3 entries
>         Handle range: 0x0001-0x0005
>         UUID: Generic Access Profile (0x1800)
>         Handle range: 0x0006-0x000d
>         UUID: Heart Rate (0x180d)
>         Handle range: 0x000e-0x0011
>         UUID: Battery Service (0x180f)
> ---
>  monitor/l2cap.c | 25 ++++++++++++++++++++++++-
>  1 file changed, 24 insertions(+), 1 deletion(-)

Applied now (with s/Improbe/Improve/ to the subject). Thanks.

Johan

      parent reply	other threads:[~2015-05-24 15:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-24 13:15 [PATCH BlueZ] monitor: Improbe decoding of ATT Read by Group Type Respose Luiz Augusto von Dentz
2015-05-24 13:58 ` Johan Hedberg
2015-05-24 15:12   ` Luiz Augusto von Dentz
2015-05-24 15:29     ` Johan Hedberg
2015-05-24 15:32 ` Johan Hedberg [this message]

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=20150524153243.GA20254@t440s \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /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).