From: Tom K <tomk@runbox.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] btsco not working with 3Com 3CREB96 and SE HBH-602
Date: Fri, 24 Mar 2006 12:43:51 +0000 [thread overview]
Message-ID: <4423E987.8010604@runbox.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0603241208510.15783@cherokee.spacecom.si>
Mitja Pufic wrote:
> Hello Tom,
>
> this really looks promissing, mine dongle says PCM, that could be because
> I am using it with a very old version of bluez. I see no problem, why
> this should not work with sco.
>
>
Thanks again, Mitja. Everything looks like it's in order, alright, but I
just can't set up a usable connection. It's a bit frustrating, because I
can send and receive audio, as described, so the hardware must be OK.
It's something in the setup, but I don't know what at the moment. Time
for some more tinkering, I think.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-03-24 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 11:23 [Bluez-devel] btsco not working with 3Com 3CREB96 and SE HBH-602 Tom K
2006-03-23 15:22 ` Mitja Pufic
2006-03-23 17:25 ` Tom K
2006-03-24 11:24 ` Mitja Pufic
2006-03-24 12:43 ` Tom K [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=4423E987.8010604@runbox.com \
--to=tomk@runbox.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;
as well as URLs for NNTP newsgroup(s).