public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Aarti Kumar <akmr2000@yahoo.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Thoughts about AVDTP support
Date: Sat, 05 Jun 2004 12:08:06 +0200	[thread overview]
Message-ID: <1086430086.16316.49.camel@pegasus> (raw)
In-Reply-To: <20040605042247.96059.qmail@web52307.mail.yahoo.com>

Hi Aarti,

> I agree that we have to keep the provision of recovery
> and reporting functionality from the start.

and there are some more, like multiplexing etc.

> The PSM value for AVDTP is 17 and the order of
> creation will determine the channel type -signal or
> media transfer. 

The PSM for AVDTP is 0x19 and this is 25 decimal ;)

> For the socket type I think it should be
> SOCK_SEQPACKET.

Any other comments about the socket type?

> Yes I do have initial part of the code that I can
> share but have nothing with SBC codec.

Please send it over, so I can see if I can integrate it or not.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

       reply	other threads:[~2004-06-05 10:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040605042247.96059.qmail@web52307.mail.yahoo.com>
2004-06-05 10:08 ` Marcel Holtmann [this message]
2004-05-30  7:05 [Bluez-devel] Thoughts about AVDTP support Marcel Holtmann
2004-06-04 21:57 ` Aarti Kumar
2004-06-04 23:58   ` Marcel Holtmann

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=1086430086.16316.49.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=akmr2000@yahoo.com \
    --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