From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Early failures with Treo 650
Date: Sat, 28 May 2005 15:41:47 +0200 [thread overview]
Message-ID: <1117287707.12036.138.camel@pegasus> (raw)
In-Reply-To: <42980599.9040801@gmail.com>
Hi David,
> > So loading with "modprobe hci_usb reset=1" and without the patch doesn't
> > make it work? Don't using "reset=1" and applying the patch does also not
> > work? Only when you do both things the dongle is working. This is odd,
> > because one of my previous Broadcom based dongles like this only needed
> > the BCM92035 quirk to switch from HID into HCI mode. Please test all
> > possibilities so I can add the correct quirk to the kernel.
>
> OK -- here are the results:
>
> 1) Stock 2.6.11 hci_usb module:
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> a) modprobe hci_usb
> => FAIL timeout on the scan (original behavior)
> b) modprobe hci_usb reset=1
> => PASS This works, can scan, and info my device
>
>
> 2) hci_usb module with given patch applied:
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> a) modprobe hci_usb
> => FAIL timeout on the scan (seems to be the same as 1a)
> b) modprobe hci_usb reset=1
> => PASS This works, can scan, and info my device. Also, there is a
> significant increase in response when I do more "hcitool scan" commands
> after the first one, I have no idea why this is or if it is important?
>
>
> 3) hci_usb module with attached patch applied:
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> a) modprobe hci_usb
> => PASS since we do the bitwise or of HCI_RESET added to BCM92035 quirk
> in the module, no need to specify reset at the command line of modprobe,
> so this works just as 2b worked (just as you said it would). Speed
> increase on multiple "hcitool scan" commands is also present as in 2b.
explain the speed increase to me. I don't understand it. The RESET quirk
should be enough, because the BCM92035 quirk is only for a very specific
dongle from Broadcom.
Check the dmesg output for added and removed USB while you are attaching
the dongle. You should see a mouse and a keyboard that will disappear
minutes later.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-05-28 13:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-21 7:14 [Bluez-users] Early failures with Treo 650 David Britton
2005-05-23 10:06 ` Marcel Holtmann
2005-05-24 2:38 ` David Britton
2005-05-24 8:48 ` Marcel Holtmann
2005-05-26 4:43 ` David Britton
2005-05-26 8:16 ` Marcel Holtmann
2005-05-27 2:15 ` David Britton
2005-05-27 7:05 ` Marcel Holtmann
2005-05-28 5:46 ` David Britton
2005-05-28 13:41 ` Marcel Holtmann [this message]
2005-06-02 4:46 ` David Britton
2005-07-28 18:02 ` [Bluez-users] " Ken M
2005-07-30 0:10 ` [Bluez-users] Treo 650 Oddities bc90021
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=1117287707.12036.138.camel@pegasus \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox