From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] sco transfer not possible if hci_usb uses ehci_hcd?
Date: Sat, 09 Apr 2005 14:19:34 +0200 [thread overview]
Message-ID: <1113049174.9783.52.camel@pegasus> (raw)
In-Reply-To: <200504082054.21259.rjenster@web.de>
Hi Ruben,
> I've the problem that when ehci_hcd is loaded and I plug my bluetooth dongle
> to my usb hub, hci_hcd uses the ehci host and playing or recording sound
> through snd-bt-sco is not possible then. (USB_EHCI_SPLIT_ISO is enabled)
> I have to unload ehci_hcd and replug the dongle in order to make audio
> transfer possible.
> Can I tell hci_usb to use ohci_hcd even when ehci_hcd is loaded?
>
> Curiously when I plug the dongle to the usb jacks that are direcly attached to
> the mainboard hci_usb uses the ohci host, even when ehci_hcd is loaded.
>
> I've added a bug report to thet kernel bugtracker
> http://bugme.osdl.org/show_bug.cgi?id=4358
>
> I would be glad if someone could help me.
with David's and Greg's attention you got the right guys for this job,
because I am not into USB HCD stuff.
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
prev parent reply other threads:[~2005-04-09 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 20:54 [Bluez-devel] sco transfer not possible if hci_usb uses ehci_hcd? Ruben Jenster
2005-04-09 12:19 ` Marcel Holtmann [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=1113049174.9783.52.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.