From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] first(?) bc4 module
Date: Thu, 14 Apr 2005 19:36:24 +0200 [thread overview]
Message-ID: <1113500184.8989.65.camel@pegasus> (raw)
In-Reply-To: <Pine.LNX.4.33.0504141909360.29800-100000@redbean.intranet.gw-instruments.de>
Hi Peter,
> > > Things again look very different if you use a BC04 with internal SCO
> > > routing (e.g. for a A2DP headset). But this is a diffrent story.
> >
> > The SCO stuff has nothing to do with A2DP, because this is ACL based.
>
> Of cause ! My mistake. However, even this ACL may be routed internaly on
> some future chips (maybe there will be something like a BC04MM........).
> I just wanted to point out that for special applications EDR can be
> usefull even if there is no fast Host to CHip connection. But such
> applications usually won't use BlueZ. So this is somehow unrelated here.
you will really need a BlueCore4 with DSP for it, because otherwise you
don't know what to do with all the data ;)
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-04-14 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 18:30 [Bluez-devel] first(?) bc4 module Brad Midgley
2005-04-13 9:31 ` Marcel Holtmann
2005-04-14 15:16 ` Brad Midgley
2005-04-14 16:03 ` Marcel Holtmann
2005-04-14 16:26 ` Peter Wippich
2005-04-14 17:02 ` Marcel Holtmann
2005-04-14 17:25 ` Peter Wippich
2005-04-14 17:36 ` Marcel Holtmann [this message]
2005-04-14 18:22 ` Peter Wippich
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=1113500184.8989.65.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.