From: Marcel Holtmann <marcel@holtmann.org>
To: Till Harbaum <till@harbaum.org>
Cc: Till Harbaum <harbaum@beecon.de>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Fighting with SCO
Date: Thu, 26 Aug 2004 21:23:05 +0200 [thread overview]
Message-ID: <1093548184.2581.48.camel@pegasus> (raw)
In-Reply-To: <200408262000.07077.till@harbaum.org>
Hi Till,
> guess what ... my Acer Dongle at home just works fine. I'll try to figure out,
> what the reason is.
do you played with the PS key settings, because the default for the Acer
was sending SCO traffic over the PCM interface. Use the revision command
to check where the SCO traffic is routed through.
> So you may add the BlueTrek G2 to the list of supported devices.
Send me the output of "hcitool info ...".
> At least my broadcom dongle says it has 0 sco slots of 16 bytes each. I think
> this is a clear indication, that the dongle does not support sco.
It is Broadcom. Their support to the community is very bad.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-08-26 19:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 16:52 [Bluez-devel] Fighting with SCO Till Harbaum
2004-08-26 17:27 ` Marcel Holtmann
2004-08-26 18:00 ` Till Harbaum
2004-08-26 19:23 ` Marcel Holtmann [this message]
2004-08-26 20:29 ` Till Harbaum
2004-08-26 20:36 ` Marcel Holtmann
2004-08-27 10:21 ` Till Harbaum
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=1093548184.2581.48.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=harbaum@beecon.de \
--cc=till@harbaum.org \
/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