From: Ruben Jenster <rjenster@web.de>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] usb-2.0 hub problem
Date: Thu, 24 Mar 2005 17:06:45 +0000 [thread overview]
Message-ID: <200503241706.45605.rjenster@web.de> (raw)
Trying to transmit some audio data to my headset fails, when the bluetooth
dongle is attached to a usb-2.0 hub. I allready commited a bug to the kernel
bugtracker but there no one is able to help me.
http://bugme.osdl.org/show_bug.cgi?id=4358
The dongle works perfectly when attached directly to the motherbord.
When attaching it to the usb-2.0 hub I get the following message:
usb 3-3.1: new full speed USB device using ehci_hcd and address 5
Bluetooth: Core ver 2.7
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: HCI USB driver ver 2.8
usbcore: registered new driver hci_usb
Bluetooth: L2CAP ver 2.7
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM ver 1.5
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
hci_cmd_task: hci0 command tx timeout
hci_usb_isoc_rx_submit: hci0 isoc rx submit failed urb cf315c14 err -12
hci_usb_isoc_rx_submit: hci0 isoc rx submit failed urb cf315c14 err -12
Maybe someone here is able to help me.
Regards
Ruben
-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register
by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
reply other threads:[~2005-03-24 17:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200503241706.45605.rjenster@web.de \
--to=rjenster@web.de \
--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