linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Lucas De Marchi <lucas.demarchi@profusion.mobi>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: Re: [PATCH] Fix parser of AVRCP continuing messages
Date: Tue, 27 Sep 2011 12:58:57 +0300	[thread overview]
Message-ID: <20110927095857.GC6190@dell> (raw)
In-Reply-To: <1315923685-30574-1-git-send-email-lucas.demarchi@profusion.mobi>

Hi Lucas,

On Tue, Sep 13, 2011, Lucas De Marchi wrote:
> If packet_type is not START or SINGLE, we have to continue where we
> stopped from previous packet. Therefore we must store where we left on
> previous packet due to packet size limit. We store both the number of
> attributes missing and the lenght of the last attribute that is missing.
> 
> An example interaction for this implementation, obtained with PTS test
> TC_TG_MDI_BV_04_C (I reduced the MTU in order to reproduce it here and
> values between brackets I added now):
> 
> > AVCTP: Command : pt 0x00 transaction 2 pid 0x110e
>     AV/C: Status: address 0x48 opcode 0x00
>       Subunit: Panel
>       Opcode: Vendor Dependent
>       Company ID: 0x001958
>       AVRCP: GetElementAttributes: pt Single len 0x0009
>         Identifier: 0x0 (PLAYING)
>         AttributeCount: 0x00
> < AVCTP: Response : pt 0x00 transaction 2 pid 0x110e
>     AV/C: Stable: address 0x48 opcode 0x00
>       Subunit: Panel
>       Opcode: Vendor Dependent
>       Company ID: 0x001958
>       AVRCP: GetElementAttributes: pt Start len 0x0118
>         AttributeCount: 0x04
>         Attribute: 0x00000001 (Title)
>         CharsetID: 0x006a (UTF-8)
>         AttributeValueLength: 0x001b
>         AttributeValue: isso eh um titulo mei longo
>         Attribute: 0x00000003 (Album)
>         CharsetID: 0x006a (UTF-8)
>         AttributeValueLength: 0x00fe
> 	AttributeValue: super-long-album-name super-long-album-name
> 	super-long-album-name super-long-album-name super-long-album
> 	super-long-album-name [... snip... ] super-long-album-name-1234
> > AVCTP: Command : pt 0x00 transaction 2 pid 0x110e
>     AV/C: Control: address 0x48 opcode 0x00
>       Subunit: Panel
>       Opcode: Vendor Dependent
>       Company ID: 0x001958
>       AVRCP: RequestContinuingResponse: pt Single len 0x0001
> < AVCTP: Response : pt 0x00 transaction 2 pid 0x110e
>     AV/C: Stable: address 0x48 opcode 0x00
>       Subunit: Panel
>       Opcode: Vendor Dependent
>       Company ID: 0x001958
>       AVRCP: GetElementAttributes: pt End len 0x002a
>         ContinuingAttributeValue: 678900000000000000
>         Attribute: 0x00000005 (Track Total)
>         CharsetID: 0x006a (UTF-8)
>         AttributeValueLength: 0x0002
>         AttributeValue: 30
>         Attribute: 0x00000006 (Genre)
>         CharsetID: 0x006a (UTF-8)
>         AttributeValueLength: 0x0006
>         AttributeValue: Gospel
> ---
>  parser/avrcp.c |   94 +++++++++++++++++++++++++++++++++++++++++++++++---------
>  1 files changed, 79 insertions(+), 15 deletions(-)

Applied. Thanks.

Johan

  parent reply	other threads:[~2011-09-27  9:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-13 14:21 [PATCH] Fix parser of AVRCP continuing messages Lucas De Marchi
2011-09-13 14:40 ` Luiz Augusto von Dentz
2011-09-13 16:33   ` Lucas De Marchi
2011-09-27  9:58 ` Johan Hedberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-09-09 17:40 Lucas De Marchi

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=20110927095857.GC6190@dell \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=lucas.demarchi@profusion.mobi \
    --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).