Message-ID: <447C7330.9000303@xmission.com>
Date: Tue, 30 May 2006 10:30:40 -0600
From: Brad Midgley <bmidgley@xmission.com>
MIME-Version: 1.0
To: BlueZ development <bluez-devel@lists.sourceforge.net>
References: <447C6278.1040707@palmsource.com> <447C6598.6050107@xmission.com>
	<447C69D4.9020504@palmsource.com>
In-Reply-To: <447C69D4.9020504@palmsource.com>
Subject: Re: [Bluez-devel] A2DP Profile Certification
Reply-To: BlueZ development <bluez-devel@lists.sourceforge.net>
Content-Type: text/plain; charset="iso-8859-1"
Sender: bluez-devel-bounces@lists.sourceforge.net
Errors-To: bluez-devel-bounces@lists.sourceforge.net

Fr=E9d=E9ric

> We must be very careful here : The ICS says the Source must accept =

> connection establishment, this is different from the sink role because =

> the source will accept the connection and then send its audio stream!

ok. yes, we're missing a lot of stuff here that we need to handle.

we need to use "sdptool add A2SRC" to advertise the source. we need to
listen for new connections and keep listening on the control connection
during playback (maybe in another thread)

the alsa plugin can't just block audio writes when the stream is
stopped. most alsa clients do not have a separate transmission thread,
so the ui will lock up. the way to handle it is to use dbus to tell the
audio app to pause if possible.

there is a lot of overlap with avrcp here, so we should make it easy to
work that in too.

brad


_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel