From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] SCO syncronization taking down USB dongle
Date: Wed, 15 Feb 2006 09:35:09 +0100 [thread overview]
Message-ID: <1139992509.26072.16.camel@localhost> (raw)
In-Reply-To: <bd72c4b0602141948w3bacbf30q49f933551f56b40a@mail.gmail.com>
Hi Gareth,
> Hello. I am currently writing code for voice connections using a
> Motorla HS850 headset and the BlueZ stack on a Intrinsyc Cerf 255PXA
> board (a small form mobile PC). I can currently make successful SCO
> connections to the headset, but they sometimes crash, and take the
> whole USB dongle with it. (Running 'hciconfig hci0 up' fixes it).
>
> Here is the crash printout:
> usb.c: USB disconnect on device 2
> Receive failed: Broken pipe
> hub.c: USB new device connect on bus1/2, assigned device number 3
the dongle gets disconnected from the USB bus. What kind of dongle is
this? Maybe you need to get yourself a better one, because a disconnect
from the USB is nothing we can really work around.
> I notice that flow (and error) control appear on the Todo list, but is
> there some way to guard against the whole dongle being taken down?
It only protects the host stack and not the dongle. The flow control
towards the HCI of the dongle is always used.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-02-15 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 3:48 [Bluez-users] SCO syncronization taking down USB dongle Gareth Bradley
2006-02-15 8:35 ` Marcel Holtmann [this message]
2006-02-15 23:40 ` Gareth Bradley
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=1139992509.26072.16.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-users@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.