All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Broadcast A2DP
Date: Mon, 23 May 2005 14:22:58 +0200	[thread overview]
Message-ID: <1116850978.30044.72.camel@pegasus> (raw)
In-Reply-To: <20050523121022.83208.qmail@web8307.mail.in.yahoo.com>

Hi Mayank,

> > > Is it possible to develop an application, that
> > will
> > > broadcast a2dp stream to more than 1 sink?
> > 
> > it will be possible.
> > 
> > > What I want to know is that whether sufficient
> > > bandwidth will be there or not?
> > 
> > I think it is not and besides this you might get
> > into problems if you
> > create a scatternet. Most headphones I have seen
> > require to be a master
> > of a piconet. Thus means that the source will create
> > a scatternet and
> > the link manager must use hold mode to switch
> > between both piconets. In
> > all my tests this was not working very good.
> 
> Consider the simple case, when the headphones will not
> want to become the master of the piconet, so, there
> will be only a single piconet with the a2dp source as
> the master. Thus no scatternet.
> (IVT's BlueSoleil, for instance, does not require to
> be master)
> 
> Now, my question is, whether I can send a broadcast
> packet on the L2CAP layer. If yes, then how?
> 
> Or will I have to send packets one after the other to
> all the sinks. If this is the case then I'm afraid
> that we'll face shortage of bandwidth, cause after sbc
> encoding, bit rates are no less than 210 kbps, which
> means that no more than 3 sinks can be supported (for
> a bandwidth of 723 kbps).

I think you have to do it this way. If you get into bandwidth problems,
then use more dongles.

> Also, I read somewhere that at L2CAP level, we can
> form groups similar to IGMP. Is that true? or rather,
> is it there in Bluez?

You mean the L2CAP connection less channel. We have basic support for
it, but not really the group management part. However what you need for
real broadcast is broadcast support on the HCI level. Otherwise the
kernel have to emulate the broadcast for you and this is the same as
above.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-05-23 12:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-23 12:10 [Bluez-devel] Broadcast A2DP Mayank Batra
2005-05-23 12:22 ` Marcel Holtmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-20 15:17 Mayank Batra
2005-05-20 15:42 ` Marcel Holtmann
2005-05-20 16:30   ` Brad Midgley

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=1116850978.30044.72.camel@pegasus \
    --to=marcel@holtmann.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.