From: Bharat Bhusan Panda <bharat.panda@samsung.com>
To: 'Luiz Augusto von Dentz' <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, cpgs@samsung.com
Subject: RE: [PATCH v2] monitor: Add AVDTP support to btmon
Date: Mon, 23 Mar 2015 20:26:33 +0530 [thread overview]
Message-ID: <022f01d06579$955ccec0$c0166c40$@samsung.com> (raw)
In-Reply-To: <CABBYNZLzrFhgq7K6DdFCMUg0AaQpj5RmGWDCZcZS_K3-HN8q7A@mail.gmail.com>
Hi Luiz,
> >> +
> >> +void avdtp_packet(const struct l2cap_frame *frame) {
> >> + struct l2cap_frame *l2cap_frame;
> >> + struct avdtp_frame avdtp_frame;
> >> + const char *pdu_color;
> >> +
> >> + l2cap_frame_pull(&avdtp_frame.l2cap_frame, frame, 0);
> >> +
> >> + l2cap_frame = &avdtp_frame.l2cap_frame;
> >> +
> >> + avdtp_frame.tsid = 0x00;
> >> + if (!l2cap_frame_get_u8(l2cap_frame, &avdtp_frame.hdr) ||
> >> + !l2cap_frame_get_u8(l2cap_frame,
> >> &avdtp_frame.tsid)) {
> >> + print_text(COLOR_ERROR, "frame too short");
> >> + packet_hexdump(frame->data, frame->size);
> >> + return;
> >> + }
>
> It looks like you are treating all frames as signalling but A2DP uses the same
> PSM for streaming so I wonder if you have tried this with an active stream?
Yes, I was testing it through mecApp, so couldn't test the real media streaming of the same.
I agree, it is treating all frames as signaling frames, which is how it should not be. I will submit another version for this patch handling the same.
>
Thanks
Best Regards,
Bharat
next prev parent reply other threads:[~2015-03-23 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 13:36 [PATCH v2] monitor: Add AVDTP support to btmon Bharat Panda
2015-03-23 9:34 ` Bharat Bhusan Panda
2015-03-23 10:36 ` Luiz Augusto von Dentz
2015-03-23 14:56 ` Bharat Bhusan Panda [this message]
2015-03-27 10:50 ` Bharat Bhusan Panda
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='022f01d06579$955ccec0$c0166c40$@samsung.com' \
--to=bharat.panda@samsung.com \
--cc=cpgs@samsung.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