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/avctp: Decode player features
Date: Mon, 12 Oct 2015 16:44:36 +0200 [thread overview]
Message-ID: <20151012144436.GA1772@t440s> (raw)
In-Reply-To: <1444659847-1725-1-git-send-email-luiz.dentz@gmail.com>
Hi Luiz,
On Mon, Oct 12, 2015, Luiz Augusto von Dentz wrote:
> This decodes the bits related to browsing channel which is useful to
> debug:
>
> > ACL Data RX: Handle 256 flags 0x02 dlen 68
> Channel: 69 len 64 ctrl 0x0100 [PSM 27 mode 3] {chan 5}
> I-frame: Unsegmented TxSeq 0 ReqSeq 1
> AVCTP Browsing: Response: type 0x00 label 0 PID 0x110e
> AVRCP: GetFolderItems: len 0x0036
> Status: 0x04 (Success)
> UIDCounter: 0x0000 (0)
> NumOfItems: 0x0001 (1)
> Item: 0x01 (Media Player)
> Length: 0x002e (46)
> PlayerID: 0x0001 (1)
> PlayerType: 0x0001 (Audio)
> PlayerSubType: 0x00000000 (None)
> PlayStatus: 0x01 (PLAYING)
> Features: 0x00000000003700050000000000000000
> Advanced Control Player: yes
> Browsing: no
> Searching: no
> AddToNowPlaying: no
> Unique UIDs: no
> OnlyBrowsableWhenAddressed: no
> OnlySearchableWhenAddressed: no
> NowPlaying: no
> UIDPersistency: no
I think we want to have this consistent with how it's represented for
other similar supported bits in btmon (e.g. HCI-level features), i.e.
only list the ones supported and print in red any unknown bits.
Johan
prev parent reply other threads:[~2015-10-12 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 14:24 [PATCH BlueZ] monitor/avctp: Decode player features Luiz Augusto von Dentz
2015-10-12 14:44 ` 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=20151012144436.GA1772@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).