Re: [Bluez-devel] AVDTP socket?

[Brad Midgley <bmidgley@xmission.com>]

Marcel

>>>bug as far as I know. However you don't need this, because it is always
>>>PSM 25 and my sender device simply only looks if a A2DP sink is present
>>>or not.

My a2play.c (committed to cvs btw) opens the l2cap socket and exchanges 
a couple of messages with the bt420n before I have reached something I 
don't know how to interpret:

send avdtp_discover
receive avdtp_discover accept, seid=1
send avdt_get_capabilities for seid=1
receive avdt_get_capabilities accept

The accept looks like this byte-for-byte:

02 -> response accept
02 -> AVDT_GET_CAPABILITIES
01 -> category = media transport
00 -> length of service capabilities = 0
07 -> 7 'elements' follow
06 -> elements[0]
00 ->
00 ->
ff ->
ff ->
02 ->
fa -> elements[6]

The avdt spec drops off sharply around page 86 when talking about what 
comes after the service capabilities length. Any ideas of what to make 
of the elements?

Brad

btw, I did have code in there to be totally sure I had drained off all 
the avdtp_discovery accept packets. Currently the code assumes it will 
only get one seid. The code gets ugly when I try to make it more 
generic. A nonblocking read would help but I haven't figured out how to 
get that.


-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel/listinfo/bluez-devel