Linux bluetooth development
 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>,
	"Sundar, Murali" <murali.sundar@intel.com>
Subject: Re: [Bluez-devel] AADP -- Is it being worked on?
Date: Tue, 03 Feb 2004 12:35:54 +0100	[thread overview]
Message-ID: <1075808154.13285.7.camel@pegasus> (raw)
In-Reply-To: <20040203075757.42952.qmail@web10206.mail.yahoo.com>

Hi Aarti,

> I am working on the implementation of A2DTP with basic
> functionality and right now the raw version is working
> with MP3 codec. But to be included on the bluez
> protocol stack I have to add SBC and refine it. I am
> not working on AADP, though I have written an
> application based on AADP with MP3 codec to test AVDTP
> functionality. 

to get A2DP working we need a clean AVDTP implementation which we can
include into BlueZ. This is the basic step and I don't care if you use a
MP3 codec or SBC. Once AVDTP is in the right shape, the rest will follow
automaticly. Do you have code we can look at?

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2004-02-03 11:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-02 18:57 [Bluez-devel] AADP -- Is it being worked on? Sundar, Murali
2004-02-02 21:12 ` Marcel Holtmann
2004-02-03  7:57 ` Aarti Kumar
2004-02-03 11:35   ` Marcel Holtmann [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=1075808154.13285.7.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=akmr2000@yahoo.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=murali.sundar@intel.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