From: Marcel Holtmann <marcel@holtmann.org>
To: jbarnett@pobox.com,
BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Problems with Dell BCM2045 USB device
Date: Wed, 03 Jan 2007 10:28:53 +0100 [thread overview]
Message-ID: <1167816533.20568.12.camel@violet> (raw)
In-Reply-To: <1167793130.3356.17.camel@localhost>
Hi Jon,
> I have a Dell Inspiron 9400 that has a USB bluetooth local device based
> on the BCM2045 chip.
please show us the content of /proc/bus/usb/devices for this dongle.
> The options I use for hci_usb (in /etc/modprobe.d/hci_usb is:
> options hci_usb force_scofix=1 reset=1
>
> I've also tried with no options and with only force_scofix=1. Same results.
Does normal operation like scanning for other devices work if you don't
give the reset=1 quirk? If yes, then this one is not needed at all.
If you load the hci_usb driver without force_scofix=1, what does
hciconfig show you.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-01-03 9:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.341782.1167746753.8777.bluez-devel@lists.sourceforge.net>
2007-01-03 2:58 ` [Bluez-devel] Problems with Dell BCM2045 USB device Jon Barnett
2007-01-03 9:28 ` Marcel Holtmann [this message]
2007-01-03 17:05 ` Jon Barnett
2007-01-03 17:14 ` Marcel Holtmann
2007-01-03 20:04 ` Jon Barnett
2007-01-03 20:13 ` Marcel Holtmann
2007-01-03 21:56 ` Jon Barnett
2007-01-03 15:58 ` Brad Midgley
2007-01-08 20:14 ` Jon Barnett
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=1167816533.20568.12.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=jbarnett@pobox.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 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.