From: Marcel Holtmann <marcel@holtmann.org>
To: Oguzhan Eris <eris3@ekls.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Problem "coldplugging"
Date: Sun, 04 Jan 2004 22:59:06 +0100 [thread overview]
Message-ID: <1073253546.25261.165.camel@pegasus> (raw)
In-Reply-To: <1073252537.4255.6.camel@localhost>
Hi,
> all bluetooth core drivers are in-kernel. hci_usb is a module and so is
> bcm203x (which I guess can never be in kernel as it needs way too many
> userland stuff)
personally I prefer to have all Bluetooth stuff as modules.
> I have tried lots and lots of different ways of going about it all. I'm
> guessing hci_usb needs to be loaded before bcm203x, please correct me if
> I'm wrong. But regardless, SOMETIMES it works perfectly, most of the
> time it just doesn't work. By doesn't work, i mean I can see the hci0
> device but bringing it up sometimes results in ...
> Can't init device hci0. Connection timed out(110)
> and in the logs I see
> hci_usb_isoc_rx_submit: hci0 isoc rx submit failed urb dd071214 err -90
Compile the hci_usb driver without the SCO audio support. Maybe the
Broadcom devices don't really like the ISOC transfers.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-01-04 21:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-04 18:00 [Bluez-users] Problem "coldplugging" Oguzhan Eris
2004-01-04 19:19 ` Marcel Holtmann
2004-01-04 21:42 ` Oguzhan Eris
2004-01-04 21:59 ` Marcel Holtmann [this message]
2004-01-04 19:23 ` [Bluez-users] " Michael Mauch
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=1073253546.25261.165.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=eris3@ekls.com \
/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