From: Mayank Batra <mayankbatra@yahoo.co.in>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Regarding a2recv
Date: Sun, 8 May 2005 13:50:39 +0100 (BST) [thread overview]
Message-ID: <20050508125039.1494.qmail@web8305.mail.in.yahoo.com> (raw)
In-Reply-To: <20050506060525.32b209ca.henryk@ploetzli.ch>
Henryk,
> Ah no, but luckily Brad did. However, that wasn't
> the problem. The
> problem was that a2recv didn't correctly fill out
> the transaction
> label. When responding to a request one must use the
> same transaction
> label that the other side used.
I believe that should have been a problem because
interchanding packet_type and message_type does make a
lot of difference to the avdtp packet.
Also, I agree that the init_request() function was not
much thought after while it was being written.
> I don't fully understand the logic behind what
> init_request() in
> a2recv.c does to the transaction_label, but it's
> most likely wrong.
Yes, we can simply copy the transation label given by
the source in the response.
> I therefore introduced a function init_response()
> that takes the header
> of the command that was received and creates a
> positive response header.
> init_request() is then used nowhere anymore, so I
> #if 0'd it. I also
> went through a hcidump of the (now working) stream
> setup phase and
> compared it to the AVDTP spec. Most of it looks
> correct now, except for
> Open Stream Response and Start Stream Response,
> which are too long (I'm
> not sure what to do about that as the additional
> byte(s) are reserved in
> the struct open_stream_rsp and struct
> start_stream_rsp for the case of
> an error).
> So now I made it to "Sent start stream confirm" but
> not further as the
> audio dongle doesn't seem to start streaming. The
> last three packets I
> see in an hcidump are
Why doesn't the streaming start?
> Anyways: I have committed the changed
> transaction_label handling to
> CVS, so please check that it doesn't break your
> already working
> devices.
I'll do that.
Mayank
________________________________________________________________________
Yahoo! India Matrimony: Find your life partner online
Go to: http://yahoo.shaadi.com/india-matrimony
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-05-08 12:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 12:45 [Bluez-devel] Regarding a2recv Mayank Batra
2005-05-05 13:14 ` Marcel Holtmann
2005-05-05 14:40 ` Brad Midgley
2005-05-06 4:05 ` Henryk Plötz
2005-05-08 12:50 ` Mayank Batra [this message]
2005-05-08 22:54 ` Henryk Plötz
2005-05-09 0:01 ` Marcel Holtmann
2005-05-09 0:58 ` Henryk Plötz
2005-05-09 1:03 ` Marcel Holtmann
2005-05-09 1:35 ` Henryk Plötz
2005-05-09 1:44 ` Marcel Holtmann
2005-05-09 4:29 ` Brad Midgley
2005-05-09 12:48 ` Henryk Plötz
2005-05-09 12:58 ` Marcel Holtmann
2005-05-09 16:25 ` Brad Midgley
2005-05-09 4:29 ` Brad Midgley
2005-05-09 12:38 ` Henryk Plötz
2005-05-09 21:31 ` Brad Midgley
2005-05-10 7:20 ` Mayank Batra
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=20050508125039.1494.qmail@web8305.mail.in.yahoo.com \
--to=mayankbatra@yahoo.co.in \
--cc=bluez-devel@lists.sourceforge.net \
/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